Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: One archive log every minute

Re: One archive log every minute

From: MarkP28665 <markp28665_at_aol.com>
Date: 24 May 1998 16:01:13 GMT
Message-ID: <1998052416011300.MAA25203@ladder03.news.aol.com>


From: Igor Sereda <sereda_at_spb.runnet.ru> >> Can someone give me a hint on how to reduce the speed of generating archived redo logs << Also implied that all currently running jobs are mostly read jobs.

I forgot to mention in my first reply that if one of the running jobs is using 'select for update' then that can cause the type of behavior you are seeing. This is because Oracle must read all the rows requested in the statement and mark the rows as locked before returning any. Oracle maintains this lock information in the data block and will have to rewrite blocks to the file before completing the query to make room in the buffer pool. Hence, some redo is generated by a read process where normally you would get next to none.

Mark Powell -- Oracle 7 Certified DBA
- The only advice that counts is the advice that you follow so follow your own advice - Received on Sun May 24 1998 - 11:01:13 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US