Similar to the checkpoint incomplete wait event, if an online redo log is being archived, the log writer background process will not switch to it and begin writing until it has been archived. Doing so would destroy redo that has not yet been archived. If the log writer encounters a nonarchived redo log, it will stop writing and post the wait event log file switch (archive incomplete).

This wait event can be more difficult to resolve quickly because it can clash with recoverability requirements. There are two basic solution approaches:

* Slow down the log switching by increasing the number of online redo log groups and/or increasing the online redo log member size so the archive background process can catch up when the redo writing slows a bit.