Can Not Allocate Log
(Doc ID 1265962.1)
Last updated on JULY 05, 2023
Applies to:
Oracle Database Cloud Exadata Service - Version N/A and laterOracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Information in this document applies to any platform.
Goal
PROBLEM DESCRIPTION
Error messages in alert log:
Thread <number> cannot allocate new log, sequence <number>
Checkpoint not complete
OR / AND
ORACLE Instance <name> - Can not allocate log, archival required
Thread <number> cannot allocate new log, sequence <number>
From the AWR we can see what issue is more frequent:
a) DBWR has not finished checkpointing (log file switch (checkpoint incomplete) )
b) ARCH has not finished copying the redo log file to the archive destination (Archival required)
These error messages are addressed in a similar way.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| 1) Enlarge the existing REDO log files |
| 2) Add REDO log groups |
| 3) Tune checkpoints |
| 4) Increase I/O speed for writing online REDO log/Archived REDO |
| References |