Search This Blog

Friday, July 17, 2009

Checkpoint Not Complete In Alert.log

In our production database we are getting a lots of message like below
Thu Jul 16 22:02:07 2009
Thread 1 cannot allocate new log, sequence 66271
Checkpoint not complete
Current log# 4 seq# 66270 mem# 0:

When I searched on web/metalink found the below workaround ...

"archive_lag_target" should be disabled to fix the above message in the alertlog file.

"alter system set archive_lag_target=0 scope=both;"

check metalink note: 435780.1

No comments: