SAP Note 19914 - Subsequent processing after incomplete recovery

Symptom:

Below you will find a description of measures which you have to execute for the specified cases after an incomplete recovery:
Case 1:
Reload a complete offline backup and then open the database without recovering the database.
Case 2:
Reload a complete online or offline backup which is followed by a point-in-time-recovery of the database (with ALTER DATABASE OPEN RESETLOGS).

Cause and prerequisites

Possible problems:

Situation A:
The information stored in database tables SDBAH and SDBAD on the last backups and the data carriers used in this case were lost, because the database is not up-to-date in both cases. For this reason, BRBACKUP requests a data carrier during the next backup (because of the automatic data carrier management) that are logically free but physically blocked.

Situation B:
The current log sequence number was reset during an incomplete recovery.

• in case 1 to a smaller value

• in case 2 to value 1
  BRARCHIVE does not find new offline-redo-log-files after the reloading because offline-redo-log-files were already saved with these log sequence numbers. The summarized BRARCHIVE log arch.log still contains entries on the successful archiving of these offline-redo-log-files and as a result BRARCHIVE does not recognize the offline-redo-log files as files to be archived.

Solution
Solutions for the different problems:

Situation A:
By means of the detailed BRBACKUP logs, you can determine the last used data carrier. By means of the specifications for the data carrier pool in the initialization profile init.sap (parameter volume_backup), you can determine the next data carrier to be used for the backup. Start the first of the following backups explicitly on these determined data carriers:
brbackup -v [,,...]

Situation B:
Make sure that the old offline-redo-log-files are renamed in the archiving directory.
Case 1:
You can determine the current log sequence number from the detailed BRBACKUP log of the backup from which the reloading was made. For this reason, search for the line 'Current log sequence' (message BR116I). Then change the log sequence number in the last line of the summarized BRARCHIVE log arch.log, which begins with #ARCHIVE to the value: <(determined current log sequence number) -1>.
Example for the above entry:
#ARCHIVE.. 2786 /oracle/C11/saparch/C11arch_2786 1995-04-18 15.55.55
determined current log sequence number: 2730
Example for the changed entry:
#ARCHIVE.. 2729 /oracle/C11/saparch/C11arch_2786 1995-04-18 15.55.55
After the archiving, you should undo the changes in this line (which is now the second to last line).
Case 2:
Change the log sequence number in the last line of the summarized BRARCHIVE log arch.log
which begins with #ARCHIVE to value zero (0).
Example for the above entry:
#ARCHIVE.. 2786 /oracle/C11/saparch/C11arch_2786 1995-04-18 15.55.55
Example for the changed entry:
#ARCHIVE.. 0 /oracle/C11/saparch/C11arch_2786 1995-04-18 15.55.55
After the archiving, you should undo the changes in this line (which is now the second to last line).

Caution:
--------
As of SAP Release 2.2E, BRARCHIVE recognizes automati cally the resetting of the log sequence nummber, if the database is already open when starting BRARCHIVE. In this case, the actions described under "Situation B" are not required.

Comment: You should delete offline-redo-log-files that were reloaded from the tape to the disk after the recovery.