Messages from BR029E to BR70W (SAP Library - Database Administration (Oracle) with SAPDBA)

Messages from BR029E to BR70W

BR029E Stopping BRARCHIVE started with option %s failed.

Explanation: The BRARCHIVE run started with brarchive -f could not be stopped.

Program response: brarchive -f stop is canceled

User action: Note the other messages. Try to correct the error(s), then repeat the process.

BR030W BRARCHIVE log %s not found - volume management reset.

Explanation: The summary BRARCHIVE log <ORACLE_HOME>/saparch/arch<DBSID>.log forms the foundation for volume management. If it no longer exists, BRARCHIVE loses the information about the volumes (tapes) used.

Program response: BRARCHIVE requests the first volume from pool volume_archive and continues processing.

User action: If you do not want this response, cancel BRARCHIVE and restore the summary log. The summary log from the last BRARCHIVE backup volume can be imported with the call brrestore -n sum_log .

BR031W Redo log sequence number was reset for database instance %s.

Explanation: BRARCHIVE has detected that the current log sequence number is smaller than the log sequence number of the last archived offline redo log file. This can occur, for example, when the database instance was opened with ALTER DATABASE OPEN RESETLOGS after a recovery.

Program response: Processing is continued.

User action: None.

BR032I %d offline redo log file/s found from database instance %s.

Explanation: The number of offline redo log files selected by BRARCHIVE for a database instance is output.

Program response: None.

User action: None.

BR033E Archive directory %s not found.

Explanation: The archiving directory defined in profile init<DBSID>.ora in log_archive_dest does not exist.

Program response: The program is terminated because it cannot find any offline redo log files.

User action: Correct the parameters or create the directory. Then repeat the process.

BR051I BRBACKUP %s

Explanation: BRBACKUP version number. This number is independent of the SAP release number.

Program response: None.

User action: None.

BR052I BRBACKUP terminated successfully

Explanation: BRBACKUP terminated successfully, with return code 0.

Program response: None.

User action: None.

BR053I BRBACKUP terminated with warnings.

Explanation: BRBACKUP terminated with return code 1. The backup was performed successfully.

Program response: None.

User action: Pay careful attention to the warnings. Analyze them and - if necessary - correct the cause of the warnings.

BR054I BRBACKUP terminated with errors.

Explanation: BRARCHIVE finished with a return code greater than 1.

Program response: The BRBACKUP run was terminated.

User action: Analyze and correct the specified errors. Then repeat the backup.

BR055I Start of database backup: %s %s %s

Explanation: BRBACKUP start message. The action ID ( b<encoded timestamp> ), the function ID (extension), and the start timestamp (date, time) are listed in that order, to characterize the backup. The action ID and the function ID form the file name of the detail BRBACKUP log.

Program response: None.

User action: None.

BR056I End of database backup: %s %s %s

Explanation: BRBACKUP end message. The action ID, function ID, and end timestamp are output. See BR055I.

Program response: None.

User action: None.

BR057I Backup of database: %s

Explanation: The name of the database for backup is displayed.

Program response: None.

User action: None.

BR058I BRBACKUP action ID: %s

Explanation: The action ID contains an encoded timestamp that specifies the starting time of BRBACKUP. It appears at the start of the file name of the detail BRBACKUP log, after a "b".

Program response: None.

User action: None.

BR059I BRBACKUP function ID: %s

Explanation: The function ID (extension) indicates the backup mode in which the BRBACKUP run was performed. It appears second in the file name of the detail BRBACKUP log. See Names of the Detail Logs.

Program response: None.

User action: None.

BR060I Tablespaces for backup: %s

Explanation: List of the tablespaces for backup. If all is specified, all the tablespaces are backed up. If you perform an offline backup, all the online redo log files are also backed up.

Program response: None.

User action: None.

BR061I %d files found for backup, total size %4.3f MB.

Explanation: The total number and total size of files for backup is displayed.

Program response: None.

User action: None.

BR062I %d files/directories found for backup, total size %4.3f MB.

Explanation: The total number and total size of the files for backup is displayed. This message is issued when you also want to back up directories.

Program response: None.

User action: None.

BR063I %d of %d files processed - %4.3f MB of %4.3f MB done.

Explanation: The current status of the database backup is displayed.

Program response: None.

User action: None.

BR064I The database instance %s will be shut down now.

Explanation: During an offline backup, the database instance is shut down once the BRBACKUP initialization phase is complete.

Program response: None.

User action: If you are not working in unattended mode, you can terminate the backup at this point.

BR065E Tablespace %s not found.

Explanation: This error message is issued when a tablespace you specified (using the BRBACKUP option -m <tablespace name> or by defining the tablespace name in parameter backup_mode of the init.sap profile) is not defined in the database.

Program response: The BRBACKUP run is terminated.

User action: Check the tablespace name and start BRBACKUP again.

BR066E For online backup, the database must be in ARCHIVELOG mode.

Explanation: An online backup only possible when ARCHIVELOG mode is active. This ensures that the online redo log files are archived in the archiving directory before they are overwritten during a redo log file switch. The redo logs are required for any necessary recovery.

Program response: No BRBACKUP run possible.

User action: Start the database system with the ARCHIVELOG mode active..

BR067E For online backup, automatic archival must be ENABLED for all database instances.

Explanation: An online backup can only be performed when automatic archiving is active - that is, ORACLE background process ARCH (for archiving the online redo log files to the archiving directory during a redo log file switch) must be active.

Program response: No BRBACKUP run possible.

User action: Activate automatic archiving of redo log files and repeat the operation. See Archiving Parameters.

BR068E SAP system is running or SAPR3 user is connected at offline backup.

Explanation: This error message appears when an SAP System is still running (or an SAPR3 user is still logged on to the database via SQLPLUS/SQLDBA) and you tried to start an offline backup. Transactions and jobs in the SAP System would be terminated when the database instance was shut down. BRBACKUP prevents this.

Program response: BRBACKUP terminates.

User action: Shut down the SAP System (with stopsap , for example) and then start BRBACKUP again. You can also set the init<DBSID>.ora parameter backup_type to offline_force . The database instance will then be shut down when BRBACKUP is started regardless of whether the SAP System is running or not

BR069E File name %s not unique - backup/verification impossible.

Explanation: Because the file name is not unique, files in the backup directory (during a backup to disk) could be overwritten.

Program response: The BRBACKUP run is terminated.

User action: Shut down the SAP System. Use the following SQLDBA to rename the file:

connect internal
shutdown immediate
startup mount
alter database rename '<file name>' to '<file name>';
alter database open;

Then start BRBACKUP again.

BR070W File %s greater than volume size - trying to back it up, anyway.

Explanation: The file may not fit on the tape. The actual tape switch is triggered by cpio when the physical end of the tape has been reached.

Program response: BRBACKUP attempts to save the file on a volume individually.

User action: When the physical end of the tape is reached, mount a continuation tape in the tape device. Please note that BRBACKUP considers both tapes to be one logical tape. It is the user’s responsibility to provide these two volumes, in the correct sequence, even though BRBACKUP only requests one tape. SAP recommends that you not define any files in the database that are larger than the physical tape size. See cpio Continuation Tape.