Solution : https://service.sap.com/sap/support/notes/10170 (SAP Service marketplace login required)
Summary :
The SAP Note addresses an issue encountered with BRARCHIVE, specifically with the options -s or -sd. Users may encounter the "BR013W No archive logs found to be processed." message, even though the archive logs were never saved. This issue occurs if the database is opened after a recovery using ALTER DATABASE OPEN RESETLOGS, or after a migration from ORACLE version 6 to 7 during a SAP Release upgrade, which implicitly resets the log sequence number. Another cause is initiating BRARCHIVE with -sc/-scd options before -s, leading to a sequence misalignment. Solutions include altering the brarchive summary log to reset the sequence number or running -s first.
Key words :
directory $oracle_home/saparch stillcontains entries, 2786 /usr/ora/p20/saparch/p20arch_2786 1994-05-18 15, 0 /usr/ora/p20/saparch/p20arch_2786 1994-05-18 15, brarchive/$oracle_home/saparch/arch<sid>, recovery withalter database open resetlogs, thebrarchive log arch<sid>, successful archive log backups, archive log backuptakes place, oracle version 6 tooracle version 7, archive logs found
Related Notes :
| 490976 | BR013W No offline redo log files found for processing |