The following text describes sbr81090.gif.

This illustration provides a scenario in which a gap in the sequence of archived redo log results when you are creating a new standby database. This scenario starts with the primary database in normal production mode, processing transactions, and generating online redo logs and local archived redo logs. Concurrently, you are setting up a standby database to operate in manual recovery mode. As you work, the primary database generates the local archived redo logs 4 and 5. Then, as soon as you instantiate the standby database, the primary database also archives logs 6, 7, and 8 to the standby database. However, log apply services immediately warn you that logs 4 and 5 are missing and logs 6, 7, and 8 cannot be applied to the standby database until you manually copy and apply logs 4 and 5 to the new standby database.