cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Checkpoint not complete

former_member84399
Participant
0 Likes
5,233

Dear all,

After four Oracle 10 upgrades, the only remaining warning I have on db13 in all databases I upgraded is about "checkpoint not complete" . This only happens when there is a lot of activity in the database . It never happened before though, even when there was a lot of activity in the database.

I found note #79341 and #1068186 and I have set DISABLESELFTUNE_CHECKPOINTING

to FALSE, but this didn't particularly help, still get the warnings

My questions are:

The log buffer size is increased by the upgrade to 14M (instead of 1M that is used to be). I have 2 groups of redo log files, with 2 files each. Each file is 20M on size.

I was thinking of increasing them to 30M each. Do you think that this is a good thing to do?

Under /oracle/SID/saptrace/background, I see in the log writer trace the messages below. Do you know why I get these messages and are they relevant to the issue I have with the checkpoint?

      • SERVICE NAME:() 2007-08-09 09:56:38.059

      • SESSION ID:(316.1) 2007-08-09 09:56:38.059

Maximum redo generation record size = 197120 bytes

Maximum redo generation change vector size = 190204 bytes

tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x10)

tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0x10)

      • 2007-08-09 12:55:29.062

LGWR: Archivelog for thread 1 sequence 3662 will NOT be compressed

      • 2007-08-09 14:56:22.902

LGWR: Archivelog for thread 1 sequence 3663 will NOT be compressed

      • 2007-08-09 15:09:29.136

LGWR: Archivelog for thread 1 sequence 3664 will NOT be compressed

      • 2007-08-09 18:25:38.287

Many thanks

Andreas

View Entire Topic
Former Member
0 Likes

SAP Note 830576 has this for buffer size: LOG_BUFFER 1048576

I had the same problem with checkpoints and reduced the log_buffer size to 1048576 and the issue went away.

fidel_vales
Employee
Employee
0 Likes

Hi,

Keep in mind that in Oracle 10g you cannot control the size of the redo log buffer as before with the mentioned parameter. Oracle will allocate the space based in granules. Setting the log buffer to 1048576, you are indicating Oracle 10g the minimun size to be allocated.

Former Member
0 Likes

I did not know that! Thanks!