Log File Space / Switch Waits
Log file space/switch waits occur when a redo log entry cannot be made. A redo log cannot be written to when:
- there is no free space in the redo log buffer, or
- it is in the process of being switched.
The following error messages may also be included in the alarm log for the database instance:
- CANNOT ALLOCATE NEW LOG CHECKPOINT NOT COMPLETE
- CANNOT ALLOCATE NEW LOG
- ALL ONLINE LOGS NEED ARCHIVING.
The incidence of these events should be negligible in a well-tuned database. Prior to Oracle 7.3, these two conditions were combined in the event log file space/switch. From 7.3 onwards, they are defined by the following events:
- Log buffer space. Waiting for free space in the redo log buffer. You can reduce this wait by increasing the size of the log buffer (LOG_BUFFER parameter), or by optimizing the performance of the log writer.
- Log file switch (checkpoint incomplete). The next redo log cannot be used because a checkpoint that commenced when the log was last switched has not completed.
- Log file switch (archiving needed). A redo log cannot be used because an archive operation that commenced when it was last switched has not completed.
These waits may indicate that:
- your redo logs are on slow devices,
- your LOG_BUFFER setting is too low, or
- you have too few redo logs, or they are too small.
If you are getting log file switch (archiving needed) events, consider alternating your redo logs across multiple devices to reduce contention between the Log Writer and Archiver processes.
Related Topics
Improve Redo Log Writer Performance
Deal With Wait Events
