You identify the log backups that have been made in the original instance since the last savepoint of the standby instance. To bring the standby instance up to the latest status, you import these log backups in sequence.
The database system numbers the log backups and writes a log history.
The log history of the original instance is not damaged.
Use the Database Manager CLI for the following commands.
...
1. Use the Database Manager CLI to log on to the standby instance.
2. Display the data from the restart record of the standby instance. To do this, enter the following DBM command:
db_restartinfo
The Used LOG Page row specifies the log page from which log entries have to be read first.
Used LOG Page
1157
First LOG Page
2147483647
Restartable
1
Id Restart Record
mycomputer.mynet:DEMODB_20040712_141643
Id LOG Info
mycomputer.mynet:DEMODB_20040712_141643
Consistent
1
3. Use the Database Manager CLI to log on to the original instance.
4. Display the log history of the original instance:
backup_history_open
backup_history_list
backup_history_close
The log history specifies which log pages are contained in the individual log backups.
[...]
40F281390005|LOG_00002|SAVE WARM|2004-07-12 13:59:07|2004-07-12 14:16:57|2004-07-12 14:16:57|2004-07-12 14:16:58|989|1157| |auto|64|1|0| |
[...]
Several log backups were carried out using backup media in the database instance. The log backup to the backup medium LOG_00002 contains log page 1157 and therefore has to be imported first. This is followed by the log backups LOG_00003, LOG_00004 and so on.
See also:
Starting the Standby Instance as an Active Instance