cannot allocate new log,xxx checkpoint not complete

Wed Apr 13 07:17:48 2011
Thread 1 advanced to log sequence 8487
  Current log# 2 seq# 8487 mem# 0: +DG1/orcl/onlinelog/group_2.262.668253153
Wed Apr 13 07:21:36 2011
Thread 1 cannot allocate new log, sequence 8488
Checkpoint not complete
  Current log# 2 seq# 8487 mem# 0: +DG1/orcl/onlinelog/group_2.262.668253153
Thread 1 advanced to log sequence 8488
  Current log# 1 seq# 8488 mem# 0: +DG1/orcl/onlinelog/group_1.261.668253153
Wed Apr 13 07:28:56 2011
Thread 1 advanced to log sequence 8489
  Current log# 2 seq# 8489 mem# 0: +DG1/orcl/onlinelog/group_2.262.668253153

在导入大量数据的时候在alter日志文件中一直报上面错误。通常来说，在日志写满的时候会切换到日志文件组，这个时候会触发checkpoint,dbwr进程将内存中的脏块写入到数据文件中，如果归档开启，还会触发arch。当redo log 产生过快，dbwn,arch还未完成，lgwr将日志组写满，要往当前日志组写的时候，会产生冲突，数据库就会挂起，并一直向alert日志文件中报上面错误。

解决方法如下所示：

1) Give the checkpoint process more time to cycle through the logs
-  add more redo log groups
-  increase the size of the redo logs
2) Reduce the frequency of checkpoints
- increase LOG_CHECKPOINT_INTERVAL
- increase size of online redo logs
3) Improve the efficiency of checkpoints enabling the CKPT process
with CHECKPOINT_PROCESS=TRUE
4) Set LOG_CHECKPOINT_TIMEOUT = 0.  This disables the checkpointing
based on
time interval.
5) Another means of solving this error is for DBWR to quickly write
the dirty buffers on disk.

 

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/22779291/viewspace-692380/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/22779291/viewspace-692380/