ÎÒÍ.: ÎÒÍ.: How to track logfile switch
Date: Fri, 3 Oct 2008 18:59:41 +0300
This sound promising. What DML could cause log switch (other than "alter system switch logfile" and "alter system archive log ...")?
The issue happens during normal daily load.
Îò: Bort, Guillermo [guillermo.bort_at_eds.com] Èçïðàòåíè: 03 Îêòîìâðè 2008 ã. 18:45
Äî: Yavor Ivanov; Bobak, Mark; oracle-l
Òåìà: RE: ÎÒÍ.: How to track logfile switch
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?
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.