recover_ignore 
Use this command in one of the following recovery situations:
While importing a data backup from multiple data carriers simultaneously
While importing a complete sequence of log backups after a log volume was destroyed (for example after a hardware error)
While importing an incomplete sequence of log backups
Note
Start any recovery process restoring the data backups of the relevant database. Only then import the available log backups. The command to be used for starting the recovery process depends on the point of departure.
Recovering from Multiple Data Carriers Simultaneously
Use the recover_ignore command when the data backup was made using multiple data carriers simultaneously. First start the recovery process. When the data from one of the data carriers involved was imported in full, the system prompts you to specify a succeeding data carrier. If you do not specify another data carrier, but instead execute the DBM command recover_ignore, the system will continue restoring the backup from the remaining data carriers only.
Importing a Complete Sequence of Log Backups
If the log volume has been destroyed because of a hardware problem, you still can recover the log entries retrieving the log backups made until the volume was destroyed. For that purpose, first solve the hardware problem. Then start the recovery process importing the data backups first (See: recover_start). When recovering the first log backup, the database will apply the actions stored in the log entries to the data in the data area, and stop with a return code (-8020: Next volume required) whenever the next log backup in the sequence must be specified. Each time continue the recovery process specifying the next log backup to be imported (recover_replace command) until the last available log backup has been imported. Now execute the recover_ignore command, which terminates the recovery process and starts the database. Afterwards the database will be in the ONLINE operational state and its data is consistent. The log area is empty and only that data has been retrieved that was contained in the log backups. The data that was only stored in the destroyed log volume is lost.
Importing an Incomplete Sequence of Log Backups
If errors ocurred and the sequence of log backups is incomplete because of missing log backups (gaps in the sequence), you still can recover log entries retrieving part of that data. Start the recovery process importing the data backups first (See: db_activate RECOVER). When recovering the first log backup, the database will apply the actions stored in the log entries to the data in the data area, and stop with a return code (-8020: Next volume required) whenever the next log backup in the sequence must be specified. Each time continue the recovery process specifying the next log backup to be imported (recover_replace command) until the last available log backup before the gap has been imported. Now execute the recover_ignore command, which terminates the recovery process and starts the database. Afterwards the database will be in the ONLINE operational state and its data is consistent. The log area has been initialized. Only that data was retrieved that was stored in the actually imported log backups (before the gap). The data contained in the log backups dated after the gap, and the data that was only stored in the log volume, is lost.
Example
You want to import a data backup, which was created using three tape drives simultaneouslyl and consists of a total of 5 tapes. Start importing the data using three tape drives so that tapes 1-3 are imported simultaneouslyl. After a while, the data on the tape in tape drive 1 has been completely imported. The import from drives 2 and 3 is ongoing. The system prompts you to place the next tape in tape drive 1. If you now enter recover_ignore, the import only continues with tape drives 2 and 3.
As soon as the next tape drive (e.g. tape drive 3) prompts you to insert another data carrier, use recover_replace to specify a succeeding data carrier, and import tape 4.
When you are asked to do so by tape drive 2, also use recover_replace to specify a succeeding data carrier, and import tape 5.
Thereafter all 5 backup tapes will have been imported.
The reply to this DBM command displays information about the import of the backup. Pay particular attention to the message number displayed in the Returncode field.
Note that this information is only given when the backup operation is completed or interrupted. For this reason, the reply to this command can take a long time.
Prerequisites
You have the server permission Backup.
You have started recovering a database by importing data (see recover_start) and you are still in the same database session. The operation was interrupted.
Structure
recover_ignore
Result
OK
Returncode <value>
...
Value |
Description |
|---|---|
Date |
Date |
Time |
Start time of the backup |
Server |
Name of the database computer |
Database |
Name of the database |
Kernel Version |
Version of the database kernel |
Pages Transferred |
Number of pages transferred |
Pages Left |
Number of pages still to be transferred |
Volumes |
Number of data carriers used |
Medianame |
Name of the backup template |
Location |
File or device name |
Errortext |
Error message text See also: Messages documentation |
Label |
Backup ID |
Is Consistent |
Only for data backup: Backup is internally consistent |
First LOG Page |
For data backup: First page of the log backup to be read For log backup: First page saved in the log area |
Last LOG Page |
For log backup only: Last page saved in the log area |
DB Stamp 1 Date DB Stamp 1 Time |
Time stamp for the first page of the log backup |
DB Stamp 2 Date DB Stamp 2 Time |
Time stamp for the last page of the log backup |
Page Count |
Total number of pages backed up |
Devices Used |
Number of backup devices used |
Database ID |
Database ID used to identify data and log backups that belong together |
In the event of errors, see Reply Format.