Checkpoint not complete in DB13

[Former Member]

Hi all,

I'm getting this warning message every day in the checkDB job of DB13 :

BR0976W Database message alert - level: WARNING, line: 193239, time: 2008-02-13 13.01.39, message: Checkpoint not complete BR0976W Database message alert - level: WARNING, line: 194490, time: 2008-02-14 00.32.58, message: Checkpoint not complete BR0976W Database message alert - level: WARNING, line: 194509, time: 2008-02-14 00.34.10, message: Checkpoint not complete BR0976W Database message alert - level: WARNING, line: 194630, time: 2008-02-14 01.25.17, message: Checkpoint not complete BR0976W Database message alert - level: WARNING, line: 194655, time: 2008-02-14 01.26.37, message: Checkpoint not complete

Here is the content of the alert file at line 194655

Thu Feb 14 01:26:37 2008 Thread 1 cannot allocate new log, sequence 104916 Checkpoint not complete Current log# 13 seq# 104915 mem# 0: G:\ORACLE\PRD\ORIGLOGA\LOG_G13M1.DBF Current log# 13 seq# 104915 mem# 1: H:\ORACLE\PRD\MIRRLOGA\LOG_G13M2.DBF

Can someone helps me to solve that problem ?

Many thanks,

Alex

[Former Member · Accepted solution]

Hi

Follow the instructions below

1. Check at first if the problem only happens at times with an extraordinary high amount of redo logs.Check if it is possible to reduce the amount of redo log information being generated. If e.g. the "checkpoint not complete" situation only happens during online backups, you should make sure that the tablespaces are set into backup mode sequentially and not in parallel.

2. Check if there is a temporary or permanent I/O bottleneck related to DBWR. Possible indications are high values for the wait events "write complete waits", "free buffer waits" or "db file parallel write. In addition you can perform an ORADEBUG trace of the DBWR process. In case of doubts please also contact your hardware vendor. Especially if the database seems to get stuck with "checkpoint not complete" for a longer time (> 1 minute), (temporary) I/O problems are likely.

3. If "checkpoint not complete" occurs sporadically especially during times of high system load, you can increase the amount of redo log space or the number of DBWR processes:

a) Increase the size of the redo log files (e.g. double size) Increasing the size of the redo log files is particularly useful if there are small time frames between the log switches (< 1 minute during peak load). The disadvantage of big redo log files is the lower checkpoint frequency and the longer time Oracle needs for an instance recovery.

Hope this helps

Farooq

[Former Member · Accepted solution]

Hi,

Note 79341 - Checkpoint not complete

Try this one also.

Regards

Vijay