SAP Note 10170 - BRARCHIVE does not find archive logs to save

Symptom

Key word: BRARCHIVE (with option -s or -sd)
"BR013W No archive logs found to be processed."
Message arrives although the logs were never saved.

Cause and prerequisites

1.

If the DB is opened after a recovery with
ALTER DATABASE OPEN RESETLOGS;
the "log sequence number" is also reset to 1. However, since the
brarchive log arch.log in directory $ORACLE_HOME/saparch still
contains entries for successful archive log backups with higher numbers,
brarchive does not recognize the new logs as logs to be saved.
The same may happen after a database migration from ORACLE version 6 to
ORACLE version 7 in a SAP Release upgrade from 2.0F/2.0G/2.0H to 2.1,
where the above-mentioned ORACLE command is given inplicitly.

2,
BRARCHIVE was started with option -sc/-scd before option -s was
used - second backup before the first one took place.

Solution
First possibility:
Change the last line in the summary log of brarchive
/$ORACLE_HOME/saparch/arch.log (begins with #ARCHIVE..)
using a text editor. Reset the specified log sequence number
(the first field after #ARCHIVE..) to 0.
Example:
Last line:
#ARCHIVE.. 2786 /usr/ora/P20/saparch/P20arch_2786 1994-05-18 15.55.55
is changed to:
#ARCHIVE.. 0 /usr/ora/P20/saparch/P20arch_2786 1994-05-18 15.55.55
Once you have performed the backup, undo the change again so that the
log contains the correct information. The changed line before the last
line is now the last but one.
As of SAP version 2.1I or 2.2C, this change will no longer be necessary
if the backup with brarchive is made with an open DB because brarchive
recognizes that a RESETLOGS took place. If the first archive log backup
takes place with a closed DB, however, this manual action will still be
necessary.

Second possibility:
First use option -s.