BRARCHIVE outputs the following warning:
BR017W Archive log x not found.
Case 1:
-------
Archive logs were deleted using the operating system before they could be saved or the Oracle ARCHIUVELOG mode was temporarily switched off, for example, during an upgrade.
BRARCHIVE was started with options -s, -sd, -ss or -ssd.
Case 2:
-------
Archive logs were deleted using the operating system after they were saved once with BRARCHIVE but before they were deleted by BRARCHIVE.
BRARCHIVE was started with options -sc, -scd, -ds or -dc.
Case 1:
-------
This warning refers to the fact that there are gaps in the archive directory. In such a case, the database cannot be recovered, if the recovery process is begun for an archive log with a smaller log sequence number.
A full save of the database is recommended.
The warning is normally only output once. After at least one archive log with a larger log sequence number was saved, it is automatically suppressed. Therefore in this case action is not necessary.
Case 2:
-------
The warning is output repeatedly in this case if BRARCHIVE was started with options -sc, -scd, -ds oder -dc. To suppress this, you must edit the summary BRARCHIVE log $ORACLE_HOME/saparch/arch
Before:
#ARCHIVE.. 622 /oracle/K11/saparch/K11arch1_622 1995-03-03 03.36.47
#SAVED.... acovzgvj ssd #K11A34/13 1995-03-03 08.05.18 ........
#COPIED... ........ ... ................. .......... ........ ........
#DELETED.. ........ ... .......... ........
After:
#ARCHIVE.. 622 /oracle/K11/saparch/K11arch1_622 1995-03-03 03.36.47
#SAVED.... acovzgvj ssd #K11A34/13 1995-03-03 08.05.18
+COPIED... ........ ... ................. .......... ........ ........
+DELETED.. ........ ... .......... ........
Caution:
--------
This situations will be automatically handled by BRARCHIVE in SAP release 2.1L/2.2F or later.
No comments:
Post a Comment