• Explanation: BRARCHIVE version number. This number is independent of the SAP release number.
• Program response: None.
• User action: None.

• Explanation: BRARCHIVE ended successfully with return code 0.
• Program response: None.
• User action: None.

• Explanation: BRARCHIVE ended with return code 1. The archiving/ deletion 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.

• Explanation: BRARCHIVE finished with a return code greater than 1.
• Program response: The BRARCHIVE run was terminated.
• User action: Analyze and correct the specified errors. Then repeat the archiving run.

• Explanation: BRARCHIVE start message. The action ID (a<encoded timestamp>), the function ID (extension), and the start timestamp (date, time) are listed in sequence to characterize the backup. The action ID and the function ID form the file name of the detail BRARCHIVE log.
• Program response: None.
• User action: None.

• Explanation: BRARCHIVE end message. The action ID, function ID, and end timestamp are issued. See BR006I.
• Program response: None.
• User action: None.

• Explanation: The name of the database instance(s) whose offline redo log files are to be processed is listed.
• Program response: None.
• User action: None.

• Explanation: The action ID contains an encoded timestamp that specifies the starting time of BRARCHIVE. This timestamp appears at the beginning of the file name of the detail BRARCHIVE log, after an "a".
• Program response: None.
• User action: None.

• Explanation: The function ID (extension) indicates the backup mode in which BRARCHIVE ran. It appears second in the file name of the detail BRARCHIVE log. See Names of the Detail Logs.
• Program response: None.
• User action: None.

• Explanation: The number of offline redo log files selected for processing by BRARCHIVE is displayed.
• Program response: None.
• User action: None.

• Explanation: Once all the offline redo log files in the archiving directory have been processed, BRARCHIVE checks whether ORACLE has written new offline redo log files into the archiving directory in the meantime. If so, their number is displayed in this message, and processing is continued. This case may occur during a BRARCHIVE run with options -s , -sd , -ss , or -ssd , and of course during a run with option -f .
• Program response: If offline redo log files are found, BRARCHIVE archives them.
• User action: None.

• Explanation: No suitable offline redo logs were found in the archiving directory for the selected BRARCHIVE function.
• Program response: BRARCHIVE is terminated.
• User action: None.

• Explanation: The current status of the processing of the offline redo log files is displayed.
• Program response: None.
• User action: None.

• Explanation: Confirms the deletion of an offline redo log file.
• Program response: None.
• User action: None.

• Explanation: The total number of processed offline redo log files is displayed when the BRARCHIVE run is finished.
• Program response: None.
• User action: None.

• Explanation: This warning informs you that gaps are present in the archiving directory. The database cannot be recovered in such cases if the recovery process is started at an offline redo log file with a smaller log sequence number. Possible causes:

Case 1: Offline redo log files were deleted using operating system utilities before they could be archived, or ORACLE ARCHIVELOG mode was temporarily deactivated. BRARCHIVE was started with option -s , -sd , -ss , or -ssd .

Case 2: Offline redo log files were deleted using operating system utilities after they were archived once by BRARCHIVE, but not yet deleted by BRARCHIVE. BRARCHIVE was started with option -sc , -scd , -ds , or -dc .

• Program response: The offline redo log file is ignored.
• User action: Case 1: SAP recommends a full backup of the database. The warning is normally only issued once. After at least one offline redo log file with a larger log sequence number is archived, the message is suppressed automatically, and no manual intervention is required.

Case 2: The warning is issued repeatedly when BRARCHIVE is started with option -sc , -scd , -ds , or -dc . To suppress the message, you have to edit the summary BRARCHIVE log <ORACLE_HOME>/saparch/arch<DBSID>.log . In the #COPIED and #DELETED lines, which refer to the affected offline redo log files, replace the first character, "#", with "+" or "*".

Example:

Display before:

#ARCHIVE.. 622 /oracle/C11/saparch/C11arch1_622 1995-03-03 03.36.47
#SAVED.... acovzgvj ssd #C11A34/13 1995-03-03 08.05.18
#COPIED.............. .................................
#DELETED............. ..................

• Explanation: When you select option -f in the BRARCHIVE command, BRARCHIVE waits for the next offline redo log file and immediately archives it in the archiving directory when it appears. This message is also displayed when the offline redo log files were processed successfully and a new file is being added to the archiving directory. See BR012I.
• Program response: Program continues as soon as new offline redo log files appear in the archiving directory.
• User action: None. If necessary, you can interrupt the BRARCHIVE run with option -f stop . See Canceling a Backup, and -f|-fill.

• Explanation: BRARCHIVE can only use one volume for the requested archiving - it does not support continuation tapes. The number of selected offline redo log files depends on the parameter tape_size (see Parameter tape_size).
• Program response: BRARCHIVE processes the selected offline redo log files and shuts down automatically. Several redo log files remain in the archiving directory.
• User action: The remaining offline redo log files will be archived during the next BRARCHIVE run. If you want to save them now, you will have to start BRARCHIVE again.

• Explanation: You tried to start an archiving process for a specific database.
• Program response: BRARCHIVE is not started.
• User action: When another BRARCHIVE process is running, you have to wait until it is finished. If a BRARCHIVE run was canceled or terminated, see the other messages.

• Explanation: This message appears together with BR020E.
• Program response: BRARCHIVE is not started.
• User action: Check whether BRARCHIVE is running (e.g. using the UNIX command ps ). If not, delete the specified file and start BRARCHIVE again.

• Explanation: This message appears together with BR020E.
• Program response: BRARCHIVE processing terminates because the lock cannot be set.
• User action: See BR020E and BR021I.

• Explanation: You used option -ss or -ssd (parallel archiving on two backup devices), but have only specified one backup device init<DBSID>.sap parameter file.
• Program response: The BRARCHIVE run is not performed.
• User action: Make sure at least two backup devices are used for archiving. More devices can also be specified, but only two are used. See tape_address. Restart BRARCHIVE.

• Explanation: A brarchive -f run was stopped with brarchive -f stop .
• Program response: BRARCHIVE terminates regularly.
• User action: None.

• Explanation: This message confirms that a BRARCHIVE run started with brarchive -f was stopped successfully.
• Program response: None.
• User action: None.

• Explanation: The BRARCHIVE run could not be stopped because brarchive -f is not running.
• Program response: Program call is not performed.
• User action: None.