Home -> Mailing Lists -> Oracle-L -> RE: ïôî.: How to track logfile switch

RE: ïôî.: How to track logfile switch

From: Bort, Guillermo <guillermo.bort_at_eds.com>
Date: Fri, 3 Oct 2008 10:45:28 -0500
Message-ID: <785A4E1EF4D9E745BAC909B7941BEC0094F23C@usplm201.amer.corp.eds.com> 





It may be silly to mention this, however log switches can be caused by valid dml processing not just alter system switch logfile. I've found that increasing redo log size and redo log buffer often helps lower the number of Checkpoint not Complete.š Do you notice this issue during periods of high transaction load or batch load? Also, do you have fast_start_mttr_target set to a static value?

 



HTH


 

Guillermo Alan Bort



EDS - ITO DBA Main Group

 



From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Yavor Ivanov
Sent: Friday, October 03, 2008 12:36 PM


To: Bobak, Mark; oracle-l


Subject: ïôî.: How to track logfile switch

 



 The value of ARCHIVE_LAG_TARGET is 0 

 



Unfortunately the message "Thread X cannot allocate new log, sequence XXXX" is sometimes followed by "Checkpoint not complete". So I cannot ignore it easily. Yesterday there was a short but noticeable database hang at the same time when this happened.

 



Regards,



Yavor Ivanov



[SNIP]




--
http://www.freelists.org/webpage/oracle-l


Received on Fri Oct 03 2008 - 10:45:28 CDT












Original text of this message