I am receiving the following message in my alert log and can find no
documentation explaining what this error means or how to correct it.


Thanks,
Michael

"Michael" <mbulchand (AT) gmail (DOT) com> a écrit dans le message de news:
2b047962-b90e-44f7-a422-cb9b0cd6e2b6...oglegroups.com...
Search again, for instance on Google.

Regards
Michel

On Sep 14, 6:30*am, Michael <mbulch... (AT) gmail (DOT) com> wrote:
The answers vary somewhat by version. In general it is not a fatal
error as long as it isn't compounding until things die, but it
indicates a misconfiguration of some sort, and likely a performance
problem. In older versions, you might need to configure a checkpoint
process.

So, what version/OS version are you on, and how often are you getting
the error? Are users complaining? How have you configured your log
buffer size? How big are your redo logs and how often are they
switching?

jg
--
@home.com is bogus.
Marketing, feh.
http://www3.signonsandiego.com/stori...tch/?uniontrib

On Sep 14, 12:26*pm, joel garry <joel-ga... (AT) home (DOT) com> wrote:
A "checkpoint not complete" message in the alert log pretty much has
always been an indication that the online redo logs are sized too
small for the amount of redo being generated so that another log
switch takes place before the checkpoint of the previous switch could
be completed.

Take a look at the alert log or use v$log_history to determine the
time between switches. In the absence of Data Guard I aim for 24 - 48
switches per 24 hours. That is one switch every 30 - 60 minutes on
average. If you use Data Guard and you log ship then you generally
want smaller redo logs and will aim for a higher switch total but even
so you need to make sure the online redo logs are not badly
undersized.

Too many log switches too close together so that multiple checkpoint
not complete messages occur can result in Oracle stopping current
activity so that it completes a check point.

HTH -- Mark D Powell --