17163 brarchive brbackup messages and codes

SAP Note

Header Data

Symptom

BR*Tools-Meldungen.

Other Terms

BR*Tools

Reason and Prerequisites

Information.

Solution

Messages and Return Codes BRARCHIVE, BRBACKUP, BRCONNECT, BRRECOVER, BRRESTORE, BRSPACE, BRTOOLS The programs BRARCHIVE, BRBACKUP, BRCONNECT, BRRECOVER, BRRESTORE, BRSPACE and BRTOOLS issue messages in the following form: BR<NNNN><X<>)> message text NNNN: Sequence number of the message X: Message type: - I: Information - W: Warning - E: The system issues an error message. The following are placeholders for: %s : a character string %d : an integer %f: a real number in floating point format. In most cases, the SAP utilities issue a group of messages, which will enable you to precisely analyze the error. Return codes: The following return codes may be issued: 0 - Successful backup/restore. 1 - Backup/restore ended with warnings. All files were saved/restored. 2 - Backup/restore canceled during the initialization phase by a user or another signal. 3 - Errors occurred during the initialization phase, backup/restore was not started. 4 - Backup/restore was canceled by a user or another signal during processing. 5 - Backup/restore was started, but not completed because errors occurred during processing. 6 - Internal termination of the backup/restore (this value is also visible in summary logs during the program run) 9 - Program run was not complete (this value is only visible in a summary log stored on a backup medium) Messages: BR0002I BRARCHIVE %s BR0002I BRARCHIVE %s Explanation: BRARCHIVE version number. This number is independent of the SAP release number. Program reaction: There are none. User action: There are none. BR0003I BRARCHIVE terminated successfully. BR0003I BRARCHIVE erfolgreich beendet. Explanation: BRARCHIVE ended successfully with return code 0. Program reaction: There are none. User action: There are none. BR0004I BRARCHIVE terminated with warnings. BR0004I BRARCHIVE beendet mit Warnungen. Explanation: BRARCHIVE ended with return code 1. Archiving or deleting was completed successfully. Program reaction: There are none. User action: Pay careful attention to the warnings.

17163 - BRARCHIVE/BRBACKUP messages and codes

Version 17 Validity: 16.04.2012 - active Language English

Released On 16.04.2012 03:28:05

Release Status Released for Customer

Component BC-DB-ORA-DBA Database Administration with Oracle

Priority Recommendations / Additional Info

Category Help for error analysis

Analyze them and, if necessary, correct the cause of the problem. BR0005I BRARCHIVE terminated with errors. BR0005I BRARCHIVE beendet mit Fehlern. Explanation: BRARCHIVE finished with a return code greater than 1. Program reaction: The BRARCHIVE run was canceled. User action: Analyze and correct the specified errors. Then repeat the archiving run. BR0006I Start of offline redo log processing: %s %s %s BR0006I Start der Offline-Redo-Log-Verarbeitung: %s %s %s 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 reaction: There are none. User action: There are none. BR0007I End of offline redo log processing: %s %s %s BR0007I Ende der Offline-Redo-Log-Verarbeitung: %s %s %s Explanation: BRARCHIVE end message. The action ID, function ID, and end timestamp are issued. See BR0006I. Program reaction: There are none. User action: There are none. BR0008I Offline redo log processing for database instance/s: %s BR0008I Offline-Redo-Log-Verarbeitung fuer die Datenbank-Instanz/en: %s Explanation: The name of the database instance(s), the offline redo log files of which are to be processed, is issued. Program reaction: There are none. User action: There are none. BR0009I BRARCHIVE action ID: %s BR0009I BRARCHIVE Aktions-ID: %s 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 reaction: There are none. User action: There are none. BR0010I BRARCHIVE function ID: %s BR0010I BRARCHIVE Funktions-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 BRARCHIVE log. Program reaction: There are none. User action: There are none. BR0011I %d offline redo log files found for processing, total size %4.3f MB. BR0011I %d Offline-Redo-Log-Dateien zum Verarbeiten gefunden, Gesamtgroesse %4.3f MB. Explanation: The number of offline redo log files selected for processing by BRARCHIVE is displayed. Program reaction: There are none. User action: There are none. BR0012I %d next offline redo log files found for processing, total size %4.3f MB. BR0012I %d naechste Offline-Redo-Log-Dateien zum Verarbeiten gefunden, Gesamtgroesse %4.3f MB. 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 this is the case, their number is displayed in this message, and processing is continued. This case may occur during a BRARCHIVE run with Option -s, - sd, -ss, or -ssd, and of course during a run with Option -f. Program reaction: If offline redo log files are found, BRARCHIVE archives them. User action: There are none. BR0013W 'No offline redo log files found for processing' BR0013W Keine Offline-Redo-Log-Dateien zum Verarbeiten gefunden. Explanation: No suitable offline redo log files were found in the archiving directory for the selected BRARCHIVE function. Program reaction: BRARCHIVE terminates. User action: There are none. BR0014I %d of %d offline redo log files processed - %4.3f MB of %4.3f MB done. BR0014I %d von %d Offline-Redo-Log-Dateien verarbeitet, %4.3f MB von %4.3f MB fertig. Explanation: The current status of the processing of the offline redo log files is displayed. Program reaction: There are none. User action: There are none. BR0015I Offline redo log file %s deleted. BR0015I Offline-Redo-Log-Datei %s gelöscht. Explanation: Confirms the deletion of an offline redo log file. Program reaction: There are none. User action: There are none. BR0016I %d Offline redo log files processed. BR0016I %d Offline-Redo-Log-Dateien verarbeitet. Explanation: The total number of processed offline redo log files is displayed when the BRARCHIVE run is finished. Program reaction: There are none. User action: There are none. BR0017W Offline redo log file %s not found. BR0017W Offline-Redo-Log-Datei %s nicht gefunden. Explanation: This warning informs you that there are gaps in the archiving directory. The database cannot be recovered in such cases if the recovery process is started with 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 the 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 reaction: The offline redo log file is ignored. User action: Case 1: SAP recommends a full backup of the database. 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 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 '*'. For 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.. ........ ... .......... ........ Display after: #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.. ........ ... .......... ........ BR0018I Waiting for the next offline redo log file... BR0018I Warten auf die naechste Offline-Redo-Log- Datei... Explanation: When you select Option -f in the BRARCHIVE command, BRARCHIVE waits for the next offline redo log file and immediately archives it when it appears in the archiving directory. 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 Program reaction: The program continues if offline redo log files appear in the archiving directory. User action: There are none. If necessary, you can interrupt the BRARCHIVE run with Option -f stop. BR0019I Volume size limit reached - no more offline redo log files will be processed. BR0019I Datentraeger-Groesse erreicht - keine weiteren Offline-Redo-Log-Dateien werden verarbeitet. Explanation: BRARCHIVE can only use one tape for the requested archiving - in other words it does not support continuation tapes. The number of selected offline redo log files depends on parameter tape_size. Program reaction: BRARCHIVE processes the selected offline redo log files and terminates automatically. Several redo log files remain in the archiving directory. User action: The remaining offline redo log files will be saved during the next BRARCHIVE run. If you want to saved them immediately, you must restart BRARCHIVE. BR0020E BRARCHIVE already running or was killed. BR0020E BRARCHIVE laeuft gerade oder wurde abgebrochen. Explanation: You tried to start an archiving process for a specific database. Program reaction: BRARCHIVE is not started. User action: If another BRARCHIVE process is running, you have to wait until it has terminated. If a BRARCHIVE run terminates, refer to the other messages. BR0021I Please delete the file %s if BRARCHIVE was killed. BR0021I Bitte die Datei %s loeschen, wenn BRARCHIVE abgebrochen wurde Explanation: This message appears together with BR0020E. Program reaction: BRARCHIVE is not started. User action: Check whether BRARCHIVE is running (for example using the UNIX command ps). If not, delete the specified file and start BRARCHIVE again. BR0022I Setting BRARCHIVE lock failed. BR0022I Setzen von BRARCHIVE-Sperre gescheitert. Explanation: This message appears together with BR0020E. Program reaction: BRARCHIVE processing terminates because the lock cannot be set. User action: See BR0020E and BR0021I. BR0025E Not enough backup devices for this function. BR0025E Nicht genug Sicherungs-Geraete fuer diese Funktion. Explanation: You used option -ss or -ssd (parallel archiving on two backup devices), but have only specified one backup device in the init<DBSID>.sap parameter file. Program reaction: The BRARCHIVE run is not performed. User action: Make sure at least two backup devices are used for archiving. Even though you can specify more devices, only two will be used. Restart BRARCHIVE. BR0026I BRARCHIVE started with option %s will be stopped now. BR0026I BRARCHIVE gestartet mit Option %s wird jetzt gestoppt. Explanation: A brarchive -f run was stopped with brarchive -f stop. Program reaction: BRARCHIVE terminates properly. User action: There are none. BR0027I BRARCHIVE started with option %s has been stopped. BR0027I BRARCHIVE gestartet mit Option %s wurde gestoppt. Explanation: This message confirms that BRARCHIVE that was started with brarchive -f was stopped successfully. Program reaction: There are none. User action: There are none. BR0028E BRARCHIVE started with option %s is not running. BR0028E BRARCHIVE gestartet mit Option %s laeuft gerade nicht. Explanation: The BRARCHIVE run could not be stopped because brarchive -f is not running. Program reaction: The program is not called. User action: There are none. BR0029E Stopping BRARCHIVE started with option %s failed. BR0029E Stoppen von BRARCHIVE gestartet mit Option %s gescheitert.

Explanation: The BRARCHIVE run that was started with brarchive -f could not be stopped. Program reaction: brarchive -f stop terminates. User action: Take the other messages into account. Try to correct the error. Then repeat the processing. BR0030W BRARCHIVE log %s not found - volume management reset. BR0030W BRARCHIVE-Protokoll %s nicht gefunden - Datentraeger-Verwaltung zurueckgesetzt. Explanation: The summary BRARCHIVE log <ORACLE_HOME>/saparch/arch<DBSID>.log forms the foundation for volume management. If this no longer exists, BRARCHIVE loses the information about volumes used. Program reaction: BRARCHIVE requests the first volume from the volume_archive pool and continues processing. User action: If you do not want this response, cancel BRARCHIVE and restore the summary log. The summary log can be imported from the last BRARCHIVE backup volume by calling brrestore -n sum_log. BR0031W Redo log sequence number was reset for database instance %s. BR0031W Redo-Log-Sequenznummer wurde zurueckgesetzt fuer Datenbank-Instanz %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, if the database instance was opened with ALTER DATABASE OPEN RESETLOGS after a recovery. Program reaction: Processing continues. User action: There are none. BR0032I %d offline redo log file/s found from database instance %s. BR0032I %d Offline-Redo-Log-Datei/en gefunden von Datenbank-Instanz %s. Explanation: The number of offline redo log files selected by BRARCHIVE for a database instance is issued. Program reaction: There are none. User action: There are none. BR0033E Archive directory %s not found. BR0033E Archivierungs-Verzeichnis %s nicht gefunden. Explanation: The archiving directory defined in Profile init<DBSID>.ora in log_archive_dest does not exist. Program reaction: The program terminates because it cannot find any offline redo log files. User action: Correct the parameter or create the directory. Then repeat the process. BR0051I BRBACKUP %s BR0051I BRBACKUP %s Explanation: BRBACKUP version number. This number is independent of the SAP release number. Program reaction: There are none. User action: There are none. BR0052I BRBACKUP terminated successfully. BR0052I BRBACKUP erfolgreich beendet. Explanation: BRBACKUP terminates successfully with return code 0. Program reaction: There are none. User action: There are none. BR0053I BRBACKUP terminated with warnings. BR0053I BRBACKUP beendet mit Warnungen. Explanation: BRBACKUP ended with return code 1. The backup was successful. Program reaction: There are none. User action: Pay careful attention to the warnings. Analyze them and, if necessary, correct the cause of the problem. BR0054I BRBACKUP terminated with errors. BR0054I BRBACKUP beendet mit Fehlern. Explanation: BRARCHIVE finished with a return code greater than 1. Program reaction: The BRBACKUP run is terminated. User action: Analyze and correct the specified errors. Then repeat the backup. BR0055I Start of database backup: %s %s %s BR0055I Start der Datenbank-Sicherung: %s %s %s Explanation: BRBACKUP start message. The action ID (b<encoded timestamp>), the function ID (extension), and the start timestamp (date, time) are specified in this order, to characterize the backup. The action ID and the function ID form the file name of the detail BRBACKUP log. Program reaction: There are none. User action: There are none. BR0056I End of database backup: %s %s %s BR0056I Ende der Datenbank-Sicherung: %s %s %s Explanation: BRBACKUP end message. The action ID, function ID, and end timestamp are issued. See BR0055I. Program reaction: There are none. User action: There are none. BR0057I Backup of database: %s BR0057I Sicherung der Datenbank: %s Explanation: The name of the database to be backed up is issued. Program reaction: There are none. User action: There are none. BR0058I BRBACKUP action ID: %s BR0058I BRBACKUP Aktions-ID: %s Explanation: The action ID contains an encoded timestamp that specifies the starting time of BRBACKUP. This timestamp appears at the beginning of the file name of the detail BRBACKUP log, after a "b". Program reaction: There are none. User action: There are none. BR0059I BRBACKUP function ID: %s BR0059I BRBACKUP Funktions-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.

Program reaction: There are none. User action: There are none. BR0060I Tablespaces for backup: %s BR0060I Tablespaces fuer Sicherung: %s Explanation: List of the tablespaces to be backed up. If all is specified, all tablespaces are backed up. If you carry out an offline backup, all the online redo log files are also backed up. Program reaction: There are none. User action: There are none. BR0061I %d files found for backup, total size %4.3f MB. BR0061I %d Dateien zum Sichern gefunden, Gesamtgroesse %4.3f MB. Explanation: The total number and total size of files for backup is displayed. Program reaction: There are none. User action: There are none. BR0062I %d files/directories found for backup, total size %4.3f MB. BR0062I %d Dateien/Verzeichnisse zum Sichern gefunden, Gesamtgroesse %4.3f MB. Explanation: The total number and total size of files for backup is displayed. This message is also issued when you back up directories. Program reaction: There are none. User action: There are none. BR0063I %d of %d files processed - %4.3f MB of %4.3f MB done. BR0063I %d von %d Dateien verarbeitet - %4.3f MB von %4.3f MB fertig. Explanation: The current status of the database backup is displayed. Program reaction: There are none. User action: There are none. BR0064I The database instance %s will be shut down now. BR0064I Die Datenbank-Instanz %s wird jetzt gestoppt. Explanation: During an offline backup, the database instance is stopped once the BRBACKUP initialization phase is complete. Program reaction: There are none. User action: If you are not working in unattended mode, you can terminate the backup at this point. BR0065E Tablespace %s not found. BR0065E Tablespace %s nicht gefunden. 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 the parameter backup_mode of the init.sap profile) is not defined in the database. Program reaction: The BRBACKUP run terminates. User action: Check the tablespace name and restart the BRBACKUP. BR0066E For online backup, the database must be in ARCHIVELOG mode. BR0066E Fuer Online-Sicherung muss die Datenbank im ARCHIVELOG Modus sein. Explanation: You can only carry out an online backup if the 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 recovery. Program reaction: No BRBACKUP run possible. User action: Start the database system with the ARCHIVELOG mode active. BR0067E For online backup, automatic archival must be ENABLED for all database instances. BR0067E Fuer Online-Sicherung muss automatische Archivierung fuer alle Datenbank-Instanzen ENABLED sein. Explanation: You can only carry out an online backup if automatic archiving is activated - in other words, the ORACLE Background Process ARCH must be active (this backgound process is used to archive the online redo log files during a redo log file switch in the archiving directory). Program reaction: No BRBACKUP run possible. User action: Activate the automatic archiving of redo log files and repeat the processing. BR0068E SAP system is running or SAPR3 user is connected at offline backup. BR0068E SAP-System laeuft oder SAPR3-Benutzer angemeldet bei Offline-Sicherung. Explanation: This error message appears if an SAP system is still running (or if an SAPR3 user is still logged on to the database via SQLPLUS/SQLDBA) and you want to start an offline backup. Transactions and jobs in the SAP System would be terminated if the database instance was shut down. BRBACKUP prevents this. Program reaction: 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>.sap parameter backup_type to offline_force. The database instance is then stopped when the BRBACKUP is started, independent of whether the SAP system is running. BR0069E File name %s not unique - backup/verification impossible. BR0069E Dateiname %s nicht eindeutig - Sicherung/Verifikation unmoeglich. Explanation: Because the file name is not unique, files in the backup directory could be overwritten (during a backup to disk). Program reaction: The BRBACKUP run is terminated. User action: Stop the database. Rename the file at operating system level. Use the SYRMGR commands to rename the file on the database. connect internal shutdown immediate startup mount alter database rename file '<file name>' to '<file name>'; alter database open; Then restart BRBACKUP. BR0070W File %s greater than volume size - trying to back it up, anyway. BR0070W Datei %s groesser als Datentraeger-Groesse - es wird in jedem Fall versucht, sie zu sichern. 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 reaction: BRBACKUP attempts to save the file on a volume individually. User action: If the physical end of the tape is reached, insert a continuation tape in the tape device. Note that BRBACKUP considers both tapes to be one logical tape. It is your responsibility to always provide these two volumes in the correct sequence when necessary, even though BRBACKUP only requests

one tape. SAP recommends that you do not create files in the database if these are larger than the physical tape size. BR0071E BRBACKUP currently running or was killed. BR0071E BRBACKUP laeuft gerade oder wurde abgebrochen. Explanation: Only one backup process should be started for each specific database. Program reaction: BRBACKUP is not started. User action: When another BRBACKUP process is running, you have to wait until it has terminated. If a BRBACKUP run terminates, refer to the other messages. BR0072I Please delete file %s if BRBACKUP was killed. BR0072I Bitte die Datei %s loeschen, wenn BRBACKUP abgebrochen wurde. Explanation: This message appears together with BR0071E. Program reaction: BRBACKUP is not started. User action: Check whether BRBACKUP is running (for example using the UNIX command ps). If not, delete the specified file and start BRBACKUP again. BR0073I Setting BRBACKUP lock failed. BR0073I Setzen von BRBACKUP-Sperre gescheitert. Explanation: This message appears together with BR0071E. Program reaction: The BRBACKUP processing terminates because the lock cannot be set. User action: See BR0071E and BR0072I. BR0074W BRCONNECT call failed. BR0074W BRCONNECT-Aufruf gescheitert. BR0074E BRCONNECT call failed. BR0074E BRCONNECT-Aufruf gescheitert. Explanation: Program BRCONNECT is started if you start a backup with BRBACKUP, in order to monitor the database status. Program reaction: Continuation (BR0074W) or termination (BR0074E) of the BRBACKUP processing. User action: Analyze the other error messages that were issued. Try to correct this error. If BRBACKUP was terminated, repeat the processing. BR0077I Database files for backup: %s BR0077I Datenbankdateien fuer Sicherung:%s Explanation: The online redo log files to be backed up, the control file, and other database files that were specified individually using the backup_mode parameter or Option -m (not using the tablespace name) are issued. Program reaction: There are none. User action: There are none. BR0078I Non-database files for backup: %s BR0078I Nicht-Datenbankdateien fuer Sicherung: %s Explanation: The non-database files to be backed up are displayed. Program reaction: There are none. User action: There are none. BR0079I Directories for backup: %s BR0079I Verzeichnisse fuer Sicherung: %s Explanation: The directories to be backed up are displayed. Program reaction: There are none. User action: There are none. BR0080E File %s to be backed up not found. BR0080E Zu sichernde Datei %s nicht gefunden. Explanation: The file to be backed up does not exist. Program reaction: Termination of the BRBACKUP run. User action: Correct the backup_mode parameter or use option -m to specify the correct file name. Then repeat the processing. BR0081W Directories will not be compressed. BR0081W Verzeichnisse werden nicht komprimiert. Explanation: Software compression is activated (compress = yes or option -k yes). However, the contents of the directories are not compressed. Program reaction: Directory contents are not compressed. User action: There are none. This is a limitation of BRBACKUP. BR0082W Backups of directories will not be verified. BR0082W Sicherungen von Verzeichnissen werden nicht verifiziert. Explanation: Backup verification is activated (option -w|- verify). However, the backed-up contents of directories are not verified. Program reaction: Backed-up directory contents are not verified. User action: There are none. This is a limitation of BRBACKUP. BR0083W Compression rates out of date - run BRBACKUP with option '-k only'. BR0083W Kompressionsraten veraltet - starten Sie BRBACKUP mit Option '-k only'. Explanation: The last simulated backup with compression to determine the compression rates (compress = only or option -k only) was started more than a year ago. This is a warning that is only issued when hardware compression is activated (compress = hardware or option -k hardware). This message is also displayed the first time BRBACKUP Version 3.0 is started, regardless of when the last simulated backup with compression took place. Program reaction: The old compression rates are accepted or, if none are available, the default values are used. User action: You can continue processing. Start the detection of the compression rate (compress = only or option -k only) on a regular basis so that the most recent compression rates are available to BRBACKUP. BR0100E Internal error for '%s' at location %s-%d. BR0100E Interner Fehler fuer '%s' an der Stelle %s-%d. Explanation: Internal error during processing. Program reaction: Processing terminates. User action: Contact SAP.

BR0101I Parameters BR0101I Parameter Explanation: The current values of the parameters relevant for the backup/restore operation are displayed. Program reaction: There are none. User action: There are none. BR0102I Following backup devices will be used: %s BR0102I Folgende Sicherungs-Geraete werden benutzt: %s Explanation: The backup devices (in accordance with the value of the init.sap profile parameter tape_address) that are used for the backup are issued. Program reaction: There are none. User action: There are none. BR0103I The following backup volumes will be used: %s BR0103I Folgende Sicherungs-Datentraeger werden benutzt: %s Explanation: The names of the volumes, selected by automatic volume management or with option -v|-volume, that are used for backup are issued. Program reaction: There are none. User action: There are none. BR0104I %d scratch volume will be used. BR0104I %d Scratch-Datentraeger werden benutzt. Explanation: The number of the volume required for the backup is displayed. You used option -v or one of the init.sap parameters volume_backup and volume_archive with the reserved word SCRATCH. This deactivated the automatic volume management. This means that the program only checks the expiration period for the inserted backup volume(s); any name is possible. To find out the actual names of the volumes used, see message BR209I. Program reaction: Any volume with an expired expiration period (lock period) is accepted. User action: Provide any volume with an expired expiration period. BR0105E Only %d free backup volumes found, %d required. BR0105E Nur %d freie Sicherungs-Datentraeger gefunden, %d erforderlich. Explanation: Free volumes (with an expired expiration period) are sought in the list of backup volumes specified in Profile init.sap. Fewer free volumes were found than are required. Program reaction: Processing terminates. User action: Either add the required number of valid volumes to the list in the profile, or use the Command Option -v SCRATCH when you start the program. Repeat the processing. The problem can also be corrected by reducing the expiration period (parameter expir_period in Profile init<DBSID>.sap). Observe the SAP recommendations for the expiration period BR0106I Files will be saved on disk in directories: %s BR0106I Dateien werden auf Platte gesichert in Directory: %s Explanation: During a backup to disk, only the directory names (in accordance with init.sap parameter backup_root_dir) that are used for backup are displayed. Program reaction: There are none. User action: There are none. BR0107I Remote backup device will be accessed through pipe. BR0107I Auf entferntes Sicherungs-Geraet wird ueber pipe zugeriffen. Explanation: Confirms that parameter backup_dev_type or option -d|-device is set to pipe or pipe_auto. Program reaction: The backup is performed in a remote system defined in the init.sap parameter read_fifo_cmd. User action: There are none. BR0108I Automatic volume remount active. BR0108I Automatischer Datentraeger-Wechsel aktiv. Explanation: BRBACKUP was called with the init<DBSID>.sap parameter backup_dev_type=tape_auto|pipe_auto (or option -d tape_auto|pipe_auto). Program reaction: There are none. User action: No operator action is necessary during a volume switch when you use tape devices with automatic tape changing. BR0109I Files will be saved by backup utility at file level. BR0109I Dateien werden gesichert von Backup-Utility auf Datei-Ebene. Explanation: Confirms that the backup is performed at file level using an external backup program. Parameter backup_dev_type = util_file or option -d util_file was set. Program reaction: There are none. User action: There are none. BR0111I Files will be compressed. BR0111I Dateien werden komprimiert. Explanation: Confirms that the software compression configured with parameter compress = yes or option -k yes is active. Program reaction: There are none. User action: There are none. BR0112I Files will not be compressed. BR0112I Dateien werden nicht komprimiert. Explanation: Confirms that files are to be compressed during the backup. Parameter compress = no or option -k no was set. Program reaction: There are none. User action: There are none. BR0113I Files will be compressed by hardware. BR0113I Dateien werden komprimiert mit hardware. Explanation: Confirms that tape devices with hardware compression are used and that this fact will be taken into account. Parameter compress = hardware or option -k hardware was set. Program reaction: There are none. User action: There are none. BR0114I Compression will not be performed for backup utility.

BR0114I Komprimierung wird nicht durchgefuehrt fuer Backup-Utility. Explanation: The requested compression is not performed if the backup is performed using an external backup program. Program reaction: No compression is performed. User action: Set the init.sap parameter compress = no or use the command option -k no. BR0115I Compression rate for all files %5.4f:1 BR0115I Kompressionsrate fuer alle Dateien %5.4f:1 Explanation: The average compression rate is calculated from the quotient of the total size of the files before the compression and the total size of the files after the compression. Program reaction: There are none. User action: There are none. BR0116I %s before backup for database instance %s BR0116I %s vor Backup fuer Datenbank-Instanz %s Explanation: Records that command ARCHIVE LOG LIST was issued by SQLDBA before the backup was started. Program reaction: There are none. User action: There are none. BR0117I %s after backup for database instance %s BR0117I %s nach backup fuer Datenbank-Instanz %s Explanation: Records that command ARCHIVE LOG LIST was issued by SQLDBA after the backup was completed. Program reaction: There are none. User action: There are none. BR0118I Tablespaces and data files BR0118I Tablespaces und Datendateien Explanation: A description of all tablespaces and their database files is displayed. Program reaction: There are none. User action: There are none. BR0119I Redo log files BR0119I Redo-Log-Dateien Explanation: A description of all online redo log files that are in the database is issued. Program reaction: There are none. User action: There are none. BR0120I Control files BR0120I Steuerdateien Explanation: A description of all control files in the database is displayed. Program reaction: There are none. User action: There are none. BR0121W Processing of the log file %s failed. BR0121W Verarbeiten der Protokolldatei %s gescheitert. BR0121E Processing of the log file %s failed. BR0121E Verarbeiten der Protokolldatei %s gescheitert. Explanation: The BRARCHIVE/BRBACKUP log files can only be processed if they correspond to the SAP standard. Program reaction: The message is ignored (BR0121W) or processing terminates (BR0121E). User action: Note the additional messages and check the log information. If you have manually changed a log file, undo the change you have made. If a termination occurred, restart the process. BR0122E Line %d in %s longer than %d characters. BR0122E Zeile %d in %s laenger als %d Zeichen. Explanation: This message appears together with BR0121X. A line in a BRARCHIVE/BRBACKUP log file is too long. Program reaction: Processing terminates. User action: Correct the log. Then restart the operation. BR0123E Format error in line %d in %s found. BR0123E Formatfehler in Zeile %d von %s gefunden. Explanation: This message appears together with BR0121X. A line in a BRARCHIVE/BRBACKUP log file has an incorrect format. Program reaction: Processing terminates. User action: Correct the log. Then restart the operation. BR0124I Query option set - no processing. BR0124I Abfrage-Option gesetzt - keine Verarbeitung. Explanation: The program was called with option -q. Program reaction: The required resources are displayed, but no backup is started. User action: If you want to start the back-up after the query option, install the required volume and provide further resources that may be required. BR0125I Compression only - no backup. BR0125I Nur Komprimierung - keine Sicherung. Explanation: The program was started with parameter compress = only or with option -k only. The program simulates a backup with compression, but no backup is started. The compression rates can be determined in this manner. Program reaction: There are none. User action: There are none. BR0126I Unattended mode active - no confirmation required. BR0126I Unbeaufsichtigter Modus aktiv - keine Bestaetigung erforderlich. Explanation: The SAP utility was started with option -c. Program reaction: The first confirmations and mount requests are suppressed. Remount prompts are displayed. User action: There are none. BR0127I Fill volume option set - waiting for offline redo log files possible. BR0127I Fill-Option gesetzt - warten auf Offline- Redo-Log-Dateien moeglich. Explanation: BRARCHIVE was called with option -f. Offline redo log files that were saved to the archiving directory are immediately archived.

Program reaction: If all the redo logs to this point have been processed, BRARCHIVE waits for the next offline redo log files. User action: There are none. To cancel this BRARCHIVE, run use option - f stop. BR0128W Option '%s' ignored for '%s'. BR0128W Option '%s' ignoriert fuer '%s'. Explanation: In the case of two contradictory options (option and parameter), one is given priority. Program reaction: The option is ignored. User action: When you next call, do not use the option that is now ignored. BR0129W Force option set - no label checking during initialization. BR0129W Force-Option gesetzt - keine Kennsatz- Pruefung bei Initialisierung. Explanation: The SAP utility was called with option -i force. Important: No label check is performed during volume initialization with option -i force. This means that a volume that is still locked could be overwritten. Program reaction: No label check. User action: There are none. BR0130I Backup device type: %s BR0130I Sicherungs-Geraetetyp: %s Explanation: The value of init.sap parameter backup_dev_type or option -d|-device is displayed. Program reaction: There are none. User action: There are none. BR0131I All volumes get the name SCRATCH. BR0131I Alle Datentraeger bekommen den Namen SCRATCH. Explanation: During volume initialization, parameter volume_archive/volume_backup or option -v|-volume was set to SCRATCH. This solution is not normally recommended, because the volume names are not unique. This may cause problems when reloading a backup of such volumes. Program reaction: The name SCRATCH is assigned to all volumes. User action: There are none. BR0132I Show option set - volume label will be displayed without initialization. BR0132I Show-Option gesetzt - Datentraeger-Kennsatz wird angezeigt ohne Initialisierung. Explanation: The SAP utility was called with option -i show. The volume labels are displayed. Program reaction: Volume is not initialized, only the label is displayed. User action: There are none. BR0133I Label of volume in device %s: BR0133I Kennsatz von Datentraeger in Geraet %s: Explanation: The contents of the volume label are displayed. Program reaction: There are none. User action: There are none. BR0134I Unattended mode with 'force' active - no confirmation allowed. BR0134I Unbeaufsichtigter Modus mit 'force' aktiv - keine Bestaetigung erlaubt. Explanation: The program was started with option -c force. Program reaction: All interaction with the operator and cpio is suppressed (exception: password entry). User action: There are none. BR0135I Query with check option set - no processing. BR0135I Abfrage-mit-Pruefung-Option gesetzt - keine Verarbeitung. Explanation: The program was called with option -q check. The required resources are displayed. The system checks that the correct volumes are inserted in the backup devices. No backup is started. Program reaction: If incorrect volumes are inserted into the devices, these volumes are rejected. User action: There are none. Use this option, for example, if you want to use CRON to schedule backups. This way you can make sure that the right volumes are inserted. BR0136I Verify option set - double the work to do. BR0136I Verify-Option gesetzt - doppelte Arbeit zu tun. Explanation: The SAP utility program was called with option -w|- verify. Program reaction: The saved files are imported again and compared with the original data. User action: Using this option roughly doubles the backup time. Therefore, allow more time for the backup. BR0137W Verification will not be performed for backup utility. BR0137W Verifikation wird nicht durchgefuehrt fuer Backup-Utility. Explanation: Option -w|-verify is ignored when the backup is performed using an external backup program. Program reaction: The backup is performed without a verification run. User action: There are none. Use an external backup program to start the next backup without this option. BR0138I Non-database files BR0138I Nicht-Datenbankdateien Explanation: A description of the non-database files that are backed up is displayed. Program reaction: There are none. User action: There are none. BR0139I Directories BR0139I Verzeichnisse Explanation: A description of the directory contents that are backed up is displayed. Program reaction: There are none. User action: There are none. BR0140I Number of parallel copy processes: %d. BR0140I Anzahl der parallelen Kopierprozesse: %d. Explanation: The number of copy processes to be started by BRBACKUP is issued. Program reaction: There are none. User action: There are none. BR0142I Files will be switched to backup status during the backup. BR0142I Dateien werden waehrend der Sicherung in Backup-Status versetzt.

Explanation: Parameter backup_dev_type or option -d was set to util_file_online. Therefore, the tablespaces are dynamically reset to backup status during the backup. Program reaction: There are none. User action: There are none. BR0151E Environment variable %s should not be set. BR0151E Umgebungsvariable %s sollte nicht gesetzt werden. Explanation: Generally, this message appears in connection with the TWO_TASK environment variable. SAP utility programs should only run on the database server. Program reaction: The utility terminates. User action: Display the environment variables and delete the variable. Then restart the relevant program. BR0152I Environment variable %s not set. BR0152I Umgebungsvariable ist %s nicht gesetzt. Explanation: This message indicates that an environment variable, for example ORACLE_HOME or ORACLE_SID, is not set. Program reaction: Processing terminates. User action: Set the appropriate environment variable and repeat the processing. BR0153E Unknown option '%s' found at position %d. BR0153E Unbekannte Option '%s' an der Stelle %d gefunden. Explanation: Call error. The option used is unknown. Program reaction: Processing terminates. User action: Check the command syntax (for example using option -h) and repeat the processing. BR0154E Unexpected option value '%s' found at position %d. BR0154E Unerwarteter Optionswert '%s' an der Stelle %d gefunden. Explanation: Call error. The option value that is used is not allowed in this position. Program reaction: Processing terminates. User action: Check the command syntax (for example using option -h) and repeat the processing. BR0155E No value found for option %s. BR0155E Kein Wert fuer Option %s gefunden. Explanation: Call error. An option value is missing. Program reaction: Processing terminates. User action: Check the command syntax (for example using option -h) and repeat the processing. BR0156E Illegal value '%s' found for option '%s'. BR0156E Illegaler Wert 's' fuer Option '%s'. Explanation: Call error. The option value is not allowed. Program reaction: Processing terminates. User action: Check the command syntax (for example using option -h) and repeat the processing. BR0157E Value '%s' for option %s longer than %d characters. BR0157E Wert '%s' fuer Option %s laenger als %d Zeichen. Explanation: Call error. The option value is too long. Program reaction: Processing terminates. User action: Check the command syntax (for example using option -h) and repeat the processing. BR0158E Error reading init_ora profile %s BR0158E Fehler beim Lesen des init_ora-Profiles %s Explanation: Errors were determined during the reading of the init<DBSID>.ora profile. Program reaction: Processing terminates. User action: Check the syntax of the information in the init <DBSID>.ora profile. Note the detailed notes listed there. Then restart the operation. BR0159E Error reading init_sap profile %s BR0159E Fehler beim Lesen des init_sap-Profiles %s Explanation: Errors were found during the reading of the init<DBSID>.sap profile. Program reaction: Processing terminates. User action: Check the syntax of the information in the init <DBSID>.sap profile. Note the detailed notes listed there. Then restart the operation. BR0160E Unexpected symbol '%s' found for parameter %s. BR0160E Unerwartetes Symbol '%s' fuer Parameter %s gefunden. Explanation: A syntax error was found when reading a parameter. Program reaction: Processing terminates. User action: Correct the syntax. BR0161E More data expected in file %s BR0161E Mehr Daten erwartet in Datei %s Explanation: Syntax error in the specified file. The definition of a parameter was not completed properly. Program reaction: Processing terminates. User action: Correct the syntax. BR0162E Parameter %s in file %s not supported. BR0162E Parameter %s in Datei %s nicht unterstuetzt. Explanation: Profile error. The specified parameter should not be used. An init.ora parameter that is not supported is often corrected here. Program reaction: Processing terminates. User action: Delete the parameter, restart the database and repeat the action. BR0163E Unknown parameter %s found in file %s BR0163E Unbekannter Parameter %s in Datei %s gefunden. Explanation: Profile error. The parameter used is unknown. Program reaction: Processing terminates. User action: Check the entry you have made. Also see BR0162W. BR0164E Illegal value '%s' found for parameter %s. BR0164E Illegaler Wert '%s' fuer Parameter %s gefunden. Explanation: Profile error. The parameter value is not allowed. Program reaction: Processing terminates. User action: Check the parameter definition.

BR0165E Parameter %s is not set in %s BR0165E Parameter %s ist nicht gesetzt in %s Explanation: Profile error. A required parameter was not defined. Program reaction: Processing terminates. User action: Check the profile. Compare the specifications, for example with the initSID.sap sample profile. BR0166W Parameter %s not found in file %s - default assumed. BR0166W Parameter %s nicht gefunden in Datei %s - Default angenommen. Explanation: Since the parameter was not found, the ORACLE default value is selected. The default value can be platform-specific. Program reaction: Default value ORACLE is assumed. User action: Normally none. If you want to suppress this warning, define the parameter. BR0167E Unexpected value '%s' found for parameter %s. BR0167E Unerwarteter Wert '%s' fuer Parameter %s gefunden. Explanation: Profile error. Only one value is accepted for this parameter, a value list is not accepted. Program reaction: Processing terminates. User action: Correct the parameter definition. BR0168E Please define only one value for parameter %s. BR0168E Bitte definieren Sie nur einen Wert fuer Parameter %s. Explanation: Only define one value for this parameter, do not define a value list. Program reaction: Processing terminates. User action: Correct the parameter definition. BR0169W Value '%s' of parameter %s ignored for '%s' - '%s' assumed. BR0169W Wert '%s' von Parameters %s wird ignoriert fuer '%s'- '%s' angenommen. Explanation: The parameter value is not allowed for this call constellation. Program reaction: The value is replaced by a different value and processing continues. User action: No longer use this value in future calls of the program. BR0170E Value of parameter %s should be enclosed in double quotes. BR0170E Wert des Parameters %s sollte in Anfuehrungszeichen stehen. Explanation: Profile error. Quotation marks are missing. Program reaction: Processing terminates. User action: Enclose the value of this parameter in double quotes. BRBACKUP/BRARCHIVE uses this syntax in the init<DBSID>.sap profile. Make sure you use this syntax (compare, for example, with the sample profile initSID.sap). BR0171E Value '%s' of parameter %s longer than %d characters. BR0171E Wert '%s' fuer Parameter %s laenger als %d Zeichen. Explanation: The parameter value is too long. Program reaction: Processing terminates. User action: Correct the parameter definition. BR0172E Root directories %s and %s on same disk volume. BR0172E Root-Verzeichnisse %s und %s auf demselben Platte-Datentraeger. Explanation: If you specify several directories in the backup_root_dir profile parameter, these directories should be on different disks. Program reaction: Processing terminates. User action: Correct the information in the init.sap profile. BR0173E Option %s missing in parameter %s. BR0173E Option %s fehlt in Parameter %s. Explanation: The specified option is missing. This message normally refers to option -c of parameter compress_cmd. We recommend always using option -c of the compress command in the init<DBSID>.sap parameter compress_cmd, to ensure that the original file is not deleted during compression. Program reaction: Processing terminates. User action: Correct the parameter definition. BR0174E Dollar character missing. BR0174E Dollar-Zeichen fehlt. Explanation: The parameter syntax requires one or more "$" characters as placeholders in the parameter value. This message appears together with BR164E, in which the parameter name is displayed. Program reaction: Processing terminates. User action: Correct the parameter definition. BR0175E Character 'K' or 'M' should directly follow volume size. BR0175E Zeichen 'K' oder 'M' sollte direkt der Datentrager-Groesse folgen. Explanation: The value of parameter tape_size must end with "K" or "M" as the last character. This message appears together with BR164E, in which the parameter name is displayed. Program reaction: Processing terminates. User action: Correct the parameter definitions. BR0176E Parameter %s may not begin with a pipe character. BR0176E Parameter %s kann nicht mit einem Pipe- Zeichen beginnen. Explanation: The init.sap parameter read_fifo_cmd does not require a "|" character at the beginning of the parameter specifications. BRBACKUP/BRARCHIVE uses the syntax specified in sample profile initSID.sap for this parameter. Program reaction: Processing terminates. User action: Correct the parameter value. BR0177E Parameter %s may not include the dd command. BR0177E Parameter %s kann nicht das dd-Kommando enthalten. Explanation: The init.sap parameter read_fifo_cmd does not require a dd command within the parameter specifications. BRBACKUP/BRARCHIVE uses the syntax specified in Sample Profile initSID.sap for this parameter. Program reaction: Processing terminates. User action: Correct the parameter value. BR0178E Please use %s and %s parameters to define dd command.

BR0178E Bitte benutzen Sie %s und %s Parameter, um dd-Kommando zu definieren. Explanation: The dd command is defined in the specified parameters. Parameters copy_in_cmd and copy_out_cmd control the backup to a remote system. Only the host name and (optionally) the user name are specified in parameter read_fifo_cmd. Program reaction: Processing terminates. User action: Correct the parameter value. BR0179E Number of backup devices with and without rewind is not the same. BR0179E Anzahl der Sicherungs-Geraete mit und ohne rewind ist nicht gleich. Explanation: The number of device addresses in both parameters must be the same. Program reaction: Processing terminates. User action: Check the values for parameters tape_address and tape_address_rew. Make sure that the number of device addresses is the same in both parameters. BR0180E Backup devices with and without rewind have the same address. BR0180E Sicherungs-Geraete mit und ohne rewind haben die gleiche Adresse.. Explanation: The names of the device addresses in both parameters must be different. Program reaction: Processing terminates. User action: Check the values for parameters tape_address and tape_address_rew. Make sure that the device addresses in both parameters are different. You often find that the only difference between no-rewind addresses and rewind addresses is that there is an additional "n" in the name for no-rewind addresses. BR0181W Option '%s' not supported for '%s'. BR0181W Option '%s' nicht unterstuetzt fuer '%s'. BR0181E Option '%s' not supported for '%s'. BR0181E Option '%s' nicht unterstuetzt fuer '%s'. Explanation: The option is not supported in the call constellation. Program reaction: The option is ignored and processing continues (BR0181W). Processing terminates (BR0181E). User action: Check the command syntax (for example, using option -h). If a termination occurred, repeat the process. BR0182E Checking parameter %s failed. BR0182E Pruefung von Parameter %s gescheitert. Explanation: Errors were discovered when checking the parameter. The cause of the error is described in additional messages. Program reaction: Processing terminates. User action: Correct the parameter definition. Repeat the processing. BR0183E Values '%s' of option '%s' not ascending. BR0183E Werte '%s' von Option '%s' nicht aufsteigend. Explanation: The values of the option must be defined in ascending order. Program reaction: Processing terminates. User action: Correct the program call and then repeat the process. BR0184E Maximal %d values can be defined for parameter %s. BR0184E Maximal %d Werte koennen fuer Parameter %s definiert werden. Explanation: The number of values for the parameter exceeds the maximum number permitted. Program reaction: Processing terminates. User action: Correct the parameter and repeat the process. BR0185E File %s defined in IFILE parameter not in %s BR0185E Datei %s definiert in IFILE-Parameter nicht in %s Explanation: The file defined in the init<DBSID>.ora parameter IFILE is not in the <ORACLE_HOME>/dbs directory. Program reaction: Processing terminates. User action: Correct the parameter and repeat the process. BR0186E Compress directories %s and %s on the same disk volume. BR0186E Komprimierungs-Verzeichnisse %s und %s auf demselben Platten-Datentraeger. Explanation: If you specify several directories in the profile parameter compress_dir, they should be on different disks. Program reaction: Processing terminates. User action: Correct the information in the init.sap profile. BR0187E Value %d of option %s greater than %d. BR0187E Wert %d von Option %s groesser als %d. Explanation: The value of the specified option exceeds the maximum value permitted. Program reaction: Processing terminates. User action: Correct the entry and repeat the process. BR0188E Value %d of parameter %s greater than %d. BR0188E Wert %d von Parameter %s groesser als %d. Explanation: The value of the specified parameter exceeds the maximum value permitted. Program reaction: Processing terminates. User action: Correct the parameter and repeat the process. BR0189W Expiration period equals 0 - volumes could be immediately overwritten! BR0189W Sperrfrist gleich 0 - Datentraeger koennten sofort ueberschrieben werden! Explanation: The value of parameter expir_period is 0 - the expiration period check has been switched off. This means that volumes that were created on this day could be overwritten. As a result, the current back-up could be lost. Program reaction: Processing continues. User action: Correct the parameter. The value of expiration_period should be set to 0 for test purposes only. BR0201I Compressing %s BR0201I Komprimierung von %s Explanation: Compression of a file has been started. Program reaction: There are none. User action: There are none. BR0202I Saving %s

BR0202I Sicherung von %s Explanation: Backup of a file has been started. Program reaction: There are none. User action: There are none. BR0203I to %s... BR0203I auf %s... Explanation: The backup medium for the file listed in BR0202I is displayed. Program reaction: There are none. User action: There are none. BR0204I Percentage done:%3.2f%%, estimated end time:%02d:%02d BR0204I Prozentsatz fertig: %3.2f%%, geschaetzte Endzeit: %02d:%02d Explanation: The percentage of processed data is displayed. The end time of the processing is estimated based on this number. Program reaction: There are none. User action: There are none. BR0205I Backup volume initialization. BR0205I Sicherungs-Datentraeger-Initialisierung. Explanation: You called the SAP utility with option -i. Program reaction: The inserted volumes are initialized and/or their labels are displayed. User action: There are none. BR0206I End of backup volume initialization. BR0206I Ende der Sicherungs-Datentraeger- Initialisierung. Explanation: End of volume initialization. Program reaction: There are none. User action: There are none. BR0207I Volumes in devices: %s will be initialized with names: %s BR0207I Datentraeger in Geraeten: %s werden initialisiert mit Namen: %s Explanation: The system displays the names that will be assigned to the volumes during initialization. Program reaction: There are none. User action: There are none. BR0208I Volume with name %s required in device %s BR0208I Datentraeger mit Namen: %s erforderlich in Geraet %s Explanation: Because of volume management, one or more volumes with the name(s) listed have been found for which the expiration period has expired. Program reaction: The program checks whether the correct volume was inserted. User action: For the back-up, you must insert the volume(s) into the device(s) mentioned. BR0209I Volume in device %s has name %s BR0209I Datentraeger in Geraet %s hat Namen %s Explanation: The name of the volume in a backup device is displayed. Program reaction: There are none. User action: There are none. BR0210I Please mount the volumes, if you have not already done so! BR0210I Bitte montieren Sie die Datentraeger, wenn dies noch nicht getan wurde! Explanation: The requested volume must be inserted in the device. Program reaction: The system awaits confirmation. User action: For the back-up, you must insert the volume(s) into the device(s). BR0211W Unattended mode impossible - volume remount required! BR0211W Unbeaufsichtigter Modus unmoeglich - Datentraeger-Wechsel erforderlich! BR0211E Unattended mode impossible - volume remount required! BR0211E Unbeaufsichtigter Modus unmoeglich - Datentraeger-Wechsel erforderlich! Explanation: If you use option -c in BRBACKUP/BRARCHIVE calls, you suppress most of the confirmation messages. However, if - during the process flow of the service program in question, more volumes are required than the number of devices available, you have to intervene in the process and change the volume. BRBACKUP therefore issues this warning at the start of the process. You will be prompted to switch the volume at the appropriate time. If you use option -c force, this situation causes the program to terminate. Program reaction: Processing continues (BR0211W) or terminates (BR0211E). User action: If a warning is issued, you will be prompted to switch volumes at a later time. If a termination occurs in the next program call, use option -c without the force addition. BR0212I Please check the volume or the device! BR0212I Pruefen Sie bitte den Datentraeger oder das Geraet! Explanation: A volume or device error has occurred. Program reaction: Processing terminates due to previous errors. User action: To characterize the error, examine the preceding error messages. Correct the error. BR0213W Rewind of volume in device %s failed. BR0213W Spulen von Datentraeger in Geraet %s gescheitert. BR0213E Rewind of volume in device %s failed. BR0213E Spulen von Datentraeger in Geraet %s gescheitert. Explanation: The rewind of the volume or the positioning on a specific file failed. Program reaction: Waits for user action (BR0213W) or for the processing to terminate (BR0213E). User action: Analyze the preceding error messages and correct the error. BR0214W Label on volume in device %s not found. BR0214W Kennsatz auf Datentraeger in Geraet %s nicht gefunden. BR0214E Label on volume in device %s not found. BR0214E Kennsatz auf Datentraeger in Geraet %s nicht gefunden. Explanation: Case 1: If this error occurs at the beginning of the backup, the volume is probably not an SAP volume. Case 2: If this error occurs at the end of a backup, it means that the backup to that volume was not successful. Program reaction: Waits for user action (BR0214W) or for the processing to terminate (BR0214E). User action: Case 1: Initialize the volume with option -i force and repeat the processing. Case 2: Check whether parameters tape_address (no-rewind address) and tape_address_rew (rewind

address) are defined correctly. Make sure that no other processes access the backup device during the backup. If necessary, analyze the volume contents. Then repeat the processing. BR0215W Label on volume in device %s has wrong format. BR0215W Kennsatz auf Datentraeger in Geraet %s hat falsches Format. BR0215E Label on volume in device %s has wrong format. BR0215E Kennsatz auf Datentraeger in Geraet %s hat falsches Format. Explanation: The contents of a volume label are corrupted. Program reaction: Waits for user action (BR0215W) or for the processing to terminate (BR0215E). User action: Correct the error and then repeat the process. Also see the notes regarding message BR0214X. BR0216W Wrong volume %s in device %s, should be %s BR0216W Falscher Datentraeger %s in Geraet %s, sollte %s sein. BR0216E Wrong volume %s in device %s, should be %s BR0216E Falscher Datentraeger %s in Geraet %s, sollte %s sein. Explanation: You inserted an incorrect volume in the backup device. The volume name was determined automatically. The program requires that you accept this proposal. Program reaction: Waits for the user to insert the correct volume (BR0216W) or processing to terminate (BR0216E). User action: Insert the correct volume and continue the operation or repeat the processing. BR0217W Lock period for volume %s in device %s not expired. BR0217W Sperrfrist fuer Datentrager %s in Geraet %s nicht abgelaufen. BR0217E Lock period for volume %s in device %s not expired. BR0217E Sperrfrist fuer Datentrager %s in Geraet %s nicht abgelaufen. Explanation: The volume inserted in the backup device is still physically locked. You can only use the volume when the period configured by parameter expir_period in the init.sap profile has expired. Program reaction: Waits for the user to insert the correct volume (BR0217W) or for processing to terminate (BR0217E). User action: Find out about the lock management and repeat the action with the correct parameters. BR0218W Reading volume label from %s failed. BR0218W Kennsatz-Pruefung auf Datentrager in Geraet %s gescheitert. BR0218E Reading volume label from %s failed. BR0218E Kennsatz-Pruefung auf Datentrager in Geraet %s gescheitert. Explanation: This is a general error which is displayed along with other label errors. This may concern a non-SAP volume, even though an SAP volume was requested, or problems may exist with the device used. Program reaction: Waits for the user to insert the correct volume (BR0218W) or for processing to terminate (BR0218E). User action: Analyze and correct the error, repeat the process if necessary. BR0219W Initialization of volume %s in device %s failed. BR0219W Initialisierung von Datentraeger %s in Geraet %s gescheitert. BR0219E Initialization of volume %s in device %s failed. BR0219E Initialisierung von Datentraeger %s in Geraet %s gescheitert. Explanation: The initialization of a volume has failed. Program reaction: Waits for the user to insert the correct volume (BR0219W) or for processing to terminate (BR0219E). User action: If you used option -i for initialization, the volume that is inserted must be an SAP volume. Check that this is the case. If the correct volume was inserted, inspect the device. If you want to initialize another volume (non-SAP), use the -i force option. You should also refer to the other error messages. BR0220W Volume in device %s is write protected! BR0220W Datentraeger in Geraet %s ist schreibgeschützt! Explanation: The volume in the device is write-protected. Program reaction: The operation can continue when cpio can write to the terminal window. User action: Remove the write protection and continue the process. BR0221W Writing of volume header files to %s failed. BR0221W Schreiben der Datentraeger-Kopfdateien auf %s gescheitert. BR0221E Writing of volume header files to %s failed. BR0221E Schreiben der Datentraeger-Kopfdateien auf %s gescheitert. Explanation: The write process for the first files (label, init<DBSID>.ora, init<DBSID>.sap) on the volume failed. Program reaction: Waits for user action (BR0221W) or the processing terminates (BR0221E). User action: Note the other error messages issued along with this message. Correct the error and then repeat the process. BR0222W Copying %s to/from %s failed due to previous errors. BR0222W Kopieren von %s auf/von %s gescheitert aufgrund frueherer Fehler. BR0222E Copying %s to/from %s failed due to previous errors. BR0222E Kopieren von %s auf/von %s gescheitert aufgrund frueherer Fehler. Explanation: This message is issued after other error messages that display the termination of a file backup. If you only use one device, the entire backup terminates. If several devices are available, the backup continues on the other devices. Program reaction: Waits for user action (BR0222W) or for the processing to terminate (BR0222E). User action: Note the other messages. Correct the error and, if necessary, repeat the processing for the objects that were not backed up. BR0223E Last copy process failed. BR0223E Letzter Kopierprozess gescheitert. Explanation: The last copy process on the last available device failed due to a previous error. Program reaction: Processing terminates. User action: Note the other messages. Correct the error and then repeat the process. BR0224E Compress of %s to %s failed. BR0224E Komprimieren von %s auf %s gescheitert. Explanation: A file could not be compressed. Program reaction: Processing terminates. User action: Note the other messages. Correct the error and then repeat the process.

BR0225W Maximal 255 backup devices can be used. BR0225W Maximal 255 Sicherungs-Geraete koennen benutzt werden. Explanation: This is the maximum number of devices that can be used in parallel. These devices were defined in parameters tape_address and tape_address_rewind. Program reaction: Only the first 255 backup devices are used. The rest are ignored. User action: Remove the unnecessary device addresses from the parameters in profile init<DBSID>.sap. BR0227W Not enough disk space in %s for backup, missing %4.3f MB. BR0227W Nicht genug Plattenplatz in %s fuer Sicherung, fehlt %4.3f MB. BR0227E Not enough disk space in %s for backup, missing %4.3f MB. BR0227E Nicht genug Plattenplatz in %s fuer Sicherung, fehlt %4.3f MB. Explanation: During a disk backup, the free space check determined that the existing disk space is not sufficient for the backup. Program reaction: If you used option -q, only a warning is issued. Otherwise, processing terminates. User action: If you are backing up to disk, define a different file directory in parameter backup_root_dir, or try to create more space in the existing directory. If necessary, restart the process. BR0228W Not enough disk space in %s for compression, missing %4.3f MB. BR0228W Nicht genug Plattenplatz in %s fuer Komprimierung, fehlt %4.3f MB. BR0228E Not enough disk space in %s for compression, missing %4.3f MB. BR0228E Nicht genug Plattenplatz in %s fuer Komprimierung, fehlt %4.3f MB. Explanation: During the free space check, the system determined that the directory defined by parameter compress_dir does not have enough free space for the largest compressed file. The size of the compressed file is calculated based on the last available compression rates. If none exist, default values for the compression rates are used. Program reaction: If you used option -q, only a warning is issued. Otherwise, processing terminates. User action: Define a different file directory in parameter compress_dir, or try to create more space in the existing directory. Then restart the operation. BR0229I Calling backup utility... BR0229I Backup-Utility wird aufgerufen... Explanation: Reports that the BACKINT interface program is being called in order to establish a connection to an external backup program. Program reaction: There are none. User action: There are none. BR0230I Backup utility called successfully. BR0230I Backup-Utility erfolgreich aufgerufen. Explanation: The external backup program has successfully completed the backup request. Program reaction: There are none. User action: There are none. BR0231E Backup utility call failed. BR0231E Aufruf von Backup-Utility gescheitert. Explanation: The external backup program could not carry out the backup request. Program reaction: Processing terminates. User action: Note the other error messages, particularly those from the external backup program. Correct the error and then repeat the process. If necessary, contact the supplier of the external backup program. BR0232I %d of %d files saved by backup utility. BR0232I %d von %d Dateien durch Backup-Utility gesichert. BR0232E %d of %d files saved by backup utility. BR0232E %d von %d Dateien durch Backup-Utility gesichert. Explanation: The number of files saved by the external backup program is displayed. Program reaction: If this number is smaller than the number of files to be backed up, it means that errors have occurred, and processing terminates. User action: If errors occurred, analyze them. Also note the other error messages, particularly those from the external backup program. If necessary, contact the supplier of the external backup program. BR0233E Error in backup utility while saving file %s BR0233E Fehler in Backup-Utility bei Sicherung der Datei %s Explanation: The external backup program reported an error while saving the file. Program reaction: Processing terminates. User action: Check the other messages from the external backup program. If required, contact the supplier of the external backup program (the supplier of interface program BACKINT). BR0234E Unknown file %s saved by backup utility. BR0234E Unbekannte Datei %s gesichert durch Backup- Utility. Explanation: A file that was not part of the backup request was saved by the external backup program. Program reaction: Processing terminates. User action: Contact the supplier of the external backup program (the supplier of interface program BACKINT). BR0235W Recommended number of usages of volume %s exceeded. BR0235W Empfohlene Anzahl der Benutzungen von Datentraeger %s ueberschritten. Explanation: The recommended number of overwrites for the specified volume (as defined in tape_use_count) has been exceeded. Program reaction: The backup continues. User action: Do not use this volume for any more backups. BR0236I Perhaps volume initialization with option '-i force' required. BR0236I Vielleicht Datentraeger-Initialisierung mit Option '-i force' erforderlich. Explanation: This message appears when you try to start a backup on a non-initialized volume. One of the following cpio messages (platform-specific) may appear along with this message: Operating System/Message SINIX cpio: Bad header - checksum error. cpio: Not a cpio file.

AIX Cannot read from the specified input. Out of phase. HP-UX Out of phase -- get help. End of volume. OSF1 Not a cpio archive. SUN cpio: impossible header type. NT cpio: bad magic number in archive Program reaction: Processing terminates. User action: Initialize the volume using option -i force, then repeat the process. BR0237I Scratch volume required in device %s BR0237I Scratch-Datentraeger erforderlich in Geraet %s Explanation: Prompt to provide a scratch volume for the backup. Program reaction: Waits for a volume to be inserted. User action: Any volume with an expiration period (lock period) that has expired may be inserted into this device. BR0238I cpio continuation volume required in device %s. BR0238I cpio-Fortsetzungs-Datentraeger erforderlich in Geraet %s Explanation: The cpio command reached the physical end of the volume. Program reaction: Waits for a continuation volume to be inserted. User action: In this case, as the continuation volume, you should only insert a volume that has not been used for BRBACKUP/BRARCHIVE backups (for example a volume that is not specified in the pool). If a cpio continuation volume is described, any existing labels are simply overwritten. To avoid this situation in future, reduce the value of parameter tape_size. BR0239W No label checking on cpio continuation volume. BR0239W Keine Kennsatz-Pruefung auf cpio- Fortsetzungs-Datentraeger. Explanation: The volume labels will not be checked for a cpio continuation volume. Program reaction: The backup continues. User action: To avoid this situation in future, we recommend reducing the volume size defined by parameter tape_size in profile init<DBSID>.sap so that BRBACKUP/BRARCHIVE can assume the continuation volume handling. BR0240E Less data backed up than the size of file %s BR0240E Weniger Daten gesichert als die Groesse der Datei %s Explanation: The quantity of saved data reported by cpio is less than the size of the file for backup. Program reaction: Processing terminates. User action: Also check the other error messages to find and eliminate the cause of the error. BR0241I Checking label on volume in device %s BR0241I Kennsatz-Pruefung auf Datentrager in Geraet %s Explanation: Before a volume can be used for a backup, its label is checked. This check is also performed after the backup to ensure that the backup was performed successfully. Program reaction: Processing continues. User action: Depends on the program reaction. See volume administration, check the volume label. BR0242I Scratch volume in device %s will be renamed to %s BR0242I Scratch-Datentrager in Geraet %s wird umbenannt in %s Explanation: A volume with the name SCRATCH is renamed during a backup. This can only happen if the volume had the name SCRATCH. Program reaction: The volume is renamed. User action: There are none. However, you should not initialize any volumes with the name SCRATCH. BR0243W Wrong creation date %s for volume %s in device %s device %s BR0243W Falsches Erstellungsdatum %s fuer Datentraeger %s in Geraet %s BR0243E Wrong creation date %s for volume %s in device %s BR0243E Falsches Erstellungsdatum %s fuer Datentraeger %s in Geraet %s Explanation: The creation date found in the label is wrong. The volume was not described during the backup that you should use for the restore. Program reaction: Processing terminates. User action: Find out the cause of the error. Repeat the process with a correct volume. BR0244I Unload the volume in device %s and mount it once again! BR0244I Entladen Sie den Datentraeger in Geraet %s und montieren Sie ihn nochmal! Explanation: The properties of the backup device require you to unload the volume and mount it again. Program reaction: Waits for execution. User action: Unload the volume and mount it again. BR0245W Directory %s will not be compressed. BR0245W Verzeichnis %s wird nicht komprimiert. Explanation: Despite the fact that software compression is activated (parameter compress = yes or option -k yes), the directory contents are not compressed. This is a limitation of BRBACKUP. Program reaction: Processing is continued without compression. User action: There are none. BR0246E Error in backup utility for unknown file %s BR0246E Fehler in Backup-Utility fuer unbekannte Datei %s Explanation: The external backup program reported an error when backing up a file that was not part of the backup request. Program reaction: Processing terminates. User action: Contact the supplier of the external backup program (supplier of interface program BACKINT). BR0247E No Backup utility ID or ID longer than %d characters. BR0247E Keine Backup-Utility-ID oder ID laenger als %d Zeichen.

Explanation: The backup utility ID returned by the external backup program is longer than 16 characters. This is not allowed. Program reaction: Processing terminates. User action: Contact the supplier of the external backup program (supplier of interface program BACKINT). BR0251W Function %s failed at location %s-%d BR0251W Funktion %s gescheitert an der Stelle %s-%d BR0251E Function %s failed at location %s-%d BR0251E Funktion %s gescheitert an der Stelle %s-%d Explanation: A standard C function could not be executed. Program reaction: Warning and processing continues (BR0251W) or the processing terminates (BR0251E). User action: If a termination occurred, the function has returned an error return code (BR0253E). The information about the termination point should be forwarded to SAP Support. BR0252W Function %s failed for '%s' at location %s-%d BR0252W Funktion %s gescheitert fuer '%s' an der Stelle %s-%d BR0252E Function %s failed for '%s' at location %s-%d BR0252E Funktion %s gescheitert fuer '%s' an der Stelle %s-%d Explanation: A standard C function could not be executed. Program reaction: Warning and processing continues (BR0252W) or the processing terminates (BR0252E). User action: See BR0251X. In addition, the current parameters of the function that caused the termination are displayed. BR0253W errno %d: %s BR0253W errno %d: %s BR0253E errno %d: %s BR0253E errno %d: %s Explanation: The system error number and the relevant system text are displayed. These should help you find out why the standard C function failed. Program reaction: Warning and processing continues (BR0253W) or the processing terminates (BR0253E). User action: Analyze this message and try to correct the error. BR0254E Memory allocation of %d bytes failed at location %s BR0254E Speicheranforderung von %d Bytes gescheitert an der Stelle %s-%d Explanation: No main memory is available. This is either because of an internal program error or because the swap area was defined too small. Program reaction: Processing terminates. User action: Try to correct the error. BR0255W Cannot read from standard input. BR0255W Von Standardeingabe kann nicht gelesen werden. BR0255E Cannot read from standard input. BR0255E Von Standardeingabe kann nicht gelesen werden. Explanation: The standard input (console) is not available, if you used CRON or SAP CCMS to start the program, for example. Program reaction: Warning and processing continues (BR0255W) or the processing terminates (BR0255E). User action: If additional error messages are displayed, analyze them and correct the error(s). BR0256I Please enter 'cont' to continue, 'stop' to cancel the program: BR0256I Bitte 'cont' eingeben um fortzusetzen, 'stop' um Programm abzubrechen: Explanation: Entry prompt to confirm the action to be carried out. Program reaction: Waits for entry. User action: Enter one of the two character strings to either continue or cancel processing. BR0257I Your reply: '%s' BR0257I Ihre Antwort: '%s' Explanation: Confirms a correct reply to message BR0256I. Program reaction: Reply 'cont' - processing continues. Reply 'stop' - processing terminates. User action: There are none. BR0258I Wrong reply: '%s' BR0258I Falsche Antwort: '%s' Explanation: An incorrect reply was entered for message BR0256I. Program reaction: The program displays message BR0256I and prompts you to enter a correct reply. User action: Reply correctly with 'cont' or 'stop'. BR0259I Program execution will be continued... BR0259I Programmausführung wird fortgesetzt... Explanation: Confirms that program execution is continued if you reply to message BR0256I with 'cont'. Program reaction: Processing continues. User action: There are none. BR0260E Program cancelled by user! BR0260E Programm von Benutzer abgebrochen! Explanation: You cancelled the program by entering 'stop' as the reply to BR256I. Program reaction: Processing terminates. User action: There are none. BR0261E Program cancelled by signal %d! BR0261E Programm durch Signal %d abgebrochen! Explanation: The program received a signal from the user or the system. If this message appears together with BR0312E or BR0313E, BRBACKUP was interrupted by BRCONNECT. Program reaction: Processing terminates. User action: Analyze the situation and repeat the process if necessary. BR0262I Please enter DBA user name [/password]: BR0262I Bitte DBA Benutzername[/Kennwort] eingeben: Explanation: You used option -u without any other entries.

Program reaction: Prompt for interactive entry of user name and password. User action: Enter the name and password. In this case, the password will not appear in the process list. The following length restrictions apply to the passwords: HP-UX: 8 characters, OSF/1: 16 characters, AIX: 32 characters, SINIX: 8 characters, SUN: 8 characters BR0263I Please enter password for user '%s' (maximal %d characters): BR0263I Bitte Kennwort eingeben fuer Benutzer '%s' (maximal %d Zeichen): Explanation: You only used option -u when specifying the user name. Program reaction: Prompt for interactive entry of password. User action: Enter the password. In this case, the password will not appear in the process list, and is hidden upon entry. The following length restrictions apply to the passwords: HP-UX: 8 characters, OSF/1: 16 characters, AIX: 32 characters, SINIX: 8 characters, SUN: 8 characters BR0264E Username/password cannot be read. BR0264E Benutzername/Kennwort kann nicht gelesen werden. Explanation: The program tried to read from the standard input (console). However, this is not available if, for example, you used CRON or SAP CCMS to start the program. Program reaction: Processing terminates. User action: The documentation contains examples of how you can use CRON to schedule backups. BR0265W Execution of program '%s' failed. BR0265W Ausfuehrung des Programms '%s' gescheitert. BR0265E Execution of program '%s' failed. BR0265E Ausfuehrung des Programms '%s' gescheitert. Explanation: The execution of a subroutine that was called by the main program failed. This does not mean that the subroutine to be executed reported errors, but rather that the program could not be called properly. Program reaction: Processing continues (BR0265W) or terminates (BR0265E). User action: Analyze and correct the error(s) and then repeat the process. BR0266W Program '%s' interrupted, exit status: %x BR0266W Programm '%s' unterbrochen, exit status: %x BR0266E Program '%s' interrupted, exit status: %x BR0266E Programm '%s' unterbrochen, exit status: %x Explanation: A subroutine was interrupted and an exit status specified. Program reaction: Processing continues (BR0266W) or terminates (BR0266E). User action: Information about the cause of the error can be found in the exit status. The status information depends on the operating system. BR0267W Asynchronous execution of program failed. BR0267W Asynchrone Ausfuehrung eines Programms gescheitert. BR0267E Asynchronous execution of program failed. BR0267E Asynchrone Ausfuehrung eines Programms gescheitert. Explanation: The asynchronous execution of a subroutine failed. This error can occur, for example, if you use several devices for asynchronous copy processes. The message does not mean that the subroutine reported errors, but rather that the program could not be called properly. Program reaction: Processing continues (BR0267W) or terminates (BR0267E). User action: Analyze and correct the error(s) and then repeat the process. BR0268W Asynchronous execution of a program interrupted, exit status: %x BR0268W Asynchrone Ausführung eines Programms unterbrochen, exit status: %x BR0268E Asynchronous execution of a program interrupted, exit status: %x BR0268E Asynchrone Ausführung eines Programms unterbrochen, exit status: %x Explanation: The asynchronous execution of a subroutine was interrupted and an exit status was specified. This error can occur, for example, if you use several devices for asynchronous copy processes. Program reaction: Processing continues (BR0267W) or terminates (BR0267E). User action: Information about why the subroutine was interrupted can be found in the exit status. The status information depends on the operating system. BR0269W Wait situation interrupted - probably cannot continue. BR0269W Wartesituation unterbrochen - wahrscheinlich Fortsetzung unmoeglich. Explanation: The program was interrupted by CTRL C (or by signal SIGINT) while it was waiting for one of its subroutines to finish. Program reaction: Continuation of processing will probably fail. User action: If message BR0256I is also displayed, decide whether you want to continue or cancel the program. BR0270W Unknown process with ID %d terminated. BR0270W Unbekannter Prozess mit ID %d beendet. Explanation: A subroutine that was not started by the main program terminated. Program reaction: Termination of the subroutine is ignored and processing continues. User action: This could be due to an ORACLE background process error or an internal error. BR0271W Read from a pipe failed for '%s' BR0271W Lesen von einer Pipe gescheitert fuer '%s' BR0271E Read from a pipe failed for '%s' BR0271E Lesen von einer Pipe gescheitert fuer '%s' Explanation: The reading of messages from subroutines whose output was routed through a pipe mechanism failed. Program reaction: Processing continues (BR0271W) or terminates (BR0271E). User action: Once you have corrected the error, analyze the other error messages and repeat the process. BR0272W Execution of program '%s' through pipe failed. BR0272W Ausfuehrung des Programms '%s' ueber pipe gescheitert. BR0272W Execution of program '%s' through pipe failed. BR0272E Ausfuehrung des Programms '%s' ueber pipe gescheitert. Explanation: The start of subroutines whose output was routed through a pipe mechanism failed. Program reaction: Processing continues (BR0272W) or terminates (BR0272E). User action: Once you have corrected the error, analyze the other error messages and repeat the process. BR0273W Determination of file status for %s failed. BR0273W Ermittlung von Dateistatus fuer %s gescheitert.

BR0273E Determination of file status for %s failed. BR0273E Ermittlung von Dateistatus fuer %s gescheitert. Explanation: Information about a file could not be determined. This may be because the file does not exist or because there is an authorization problem. Program reaction: Processing continues (BR0273W) or terminates (BR0273E). User action: Check the other error messages and correct the error. BR0274W File %s not found. BR0274W Datei %s nicht gefunden. BR0274E File %s not found. BR0274E Datei %s nicht gefunden. Explanation: The specified file does not exist. Program reaction: Processing continues (BR0274W) or terminates (BR0274E). User action: The action depends on the file category. BR0275E File %s is not a regular file. BR0275E Datei %s ist keine normale Datei. Explanation: Symbolic links, named pipes, and device files (special files) cannot be backed up. Program reaction: Processing terminates. User action: The action depends on the file category. BR0276E File/directory %s is empty. BR0276E Datei/Verzeichnis %s ist leer. Explanation: Files with length 0 and empty directories cannot be backed up. Program reaction: Processing terminates. User action: There are none. BR0277W Determination of disk volume status for %s failed. BR0277W Ermittlung von Platten-Datentraeger-Status fuer %s gescheitert. BR0277E Determination of disk volume status for %s failed. BR0277E Ermittlung von Platten-Datentraeger-Status fuer %s gescheitert. Explanation: Information about a disk volume could not be determined. The disk volume status is mainly used to determine the free space on a disk. Program reaction: Processing continues (BR0277W) or terminates (BR0277E). User action: Correct the error, then restart the operation. BR0278W Command output of '%s': %s BR0278W Kommando-Ausgabe von '%s': %s BR0278E Command output of '%s': %s BR0278E Kommando-Ausgabe von '%s': %s Explanation: The error messages of this command are displayed. In most cases they are messages from the cpio or mt commands. The following are examples: Sample messages: Message/Explanation [cpio:]cannot read... [cpio:]read error... [cpio:]can't read input... [cpio:]I/O Error... [cpio:]read failed:I/O Error. The file to be backed up cannot be read. In most cases, this is due to hardware problems on the disk on which the file is stored. [cpio:]cannot write... [cpio:]write error... [cpio:]can't write output... [cpio:]I/O Error... [cpio:]write failed:I/O Error. The file to be backed up cannot be written to the volume. In most cases, this is due to hardware problems with the volume or the backup device. No such device or address [sh:]/dev/...:cannot create The backup device is not responding, for example if no volume (tape) was inserted in the backup device. [cpio:]cannot open... The input or output file cannot be opened. The operating system user is experiencing authorization problems. [cpio:]can't open /dev/tty to prompt for more media The physical end of the tape was reached. However, since a parallel backup is performed or the option -c force was used, cpio cannot request a cpio continuation volume. The tape size (parameter tape_size) must be reduced. Program reaction: Processing continues (BR0278W) or terminates (BR0278E). User action: Analyze the error messages. Correct the error in accordance with the message displayed by the subroutine command. BR0279W Return code from '%s': %d BR0279W Return-Code von '%s': %d BR0279E Return code from '%s': %d BR0279E Return-Code von '%s': %d Explanation: The return code of a command is displayed. This involves the return code of a subroutine that is started by the main program. The message often appears together with BR0278X. Program reaction: Processing continues (BR0279W) or terminates (BR0279E). User action: Also analyze the error messages of the subroutine (BR0278X) and correct the error. BR0280I Time stamp %s BR0280I Zeitstempel %s Explanation: The time stamp is displayed. Program reaction: There are none. User action: There are none. BR0281W Program interrupted by signal %d. BR0281W Program durch Signal %d unterbrochen. Explanation: The program was interrupted by a SIGINT signal from the user or the system. Program reaction: Message BR0256I is then displayed. Waits for your entry.

User action: Decide whether you want to continue or cancel the program. Continuation of processing will probably fail. BR0282E Directory %s not found. BR0282E Verzeichis %s nicht gefunden. Explanation: The specified directory does not exist. Program reaction: Processing terminates. User action: Analyze the situation. If required, repeat the process by entering the correct directory name. BR0283E Command/Output buffer overflow. BR0283E Kommando-/Ausgabepuffer uebergelaufen. Explanation: The buffer for the command lines and command output overflowed. Program reaction: The buffer contents are issued and processing terminates. User action: This is probably due to an internal error. Contact SAP. BR0284I Time stamp %s, elapsed time: %s BR0284I Zeitstempel %s, verstrichene Zeit: %s Explanation: An extended timestamp is displayed when you use option -o time. The time displayed is the time that has elapsed since the last time stamp (elapsed time). Program reaction: There are none. User action: There are none. BR0285I This function can take several seconds/minutes - be patient. BR0285I Diese Funktion kann einige Sekunden/Minuten dauern - bitte um Geduld. Explanation: An action was started that may take several seconds/minutes. Program reaction: Action running. User action: There are none. Wait for the action to finish. BR0286W Size of file %s is different from Oracle file size. BR0286W Größe der Datei %s ist verschieden von Oracle-Dateigröße. Explanation: The file size in the file system is different from the file size saved in the ORACLE dictionary (in the control file). The file may be corrupted. Program reaction: The program tries to save the file. User action: Check your disks, the file system (file system check), and the ORACLE ALERT file. If you discover errors, you may be able to correct the situation by performing a recovery. Contact an ORACLE specialist before you start a recovery. BR0301W SQL error %d at location %s-%d BR0301W SQL-Fehler %d an der Stelle %s-%d BR0301E SQL error %d at location %s-%d BR0301E SQL-Fehler %d an der Stelle %s-%d Explanation: An SQL error has occurred. Program reaction: Processing continues (BR0301W) or terminates (BR0301E). User action: Check the SQL code and repeat the processing. BR0302E SQLDBA call for database instance %s failed. BR0302E SQLDBA-Aufruf fuer Datenbank-Instanz %s gescheitert. Explanation: The call of the SQLDBA program failed. Program reaction: Processing terminates. User action: This error often occurs when starting up and shutting down a database instance. Take into account any ORACLE error messages that appear. Correct the error and then repeat the process. BR0303E Determination of Oracle RDBMS version failed. BR0303E Ermittlung der Oracle RDBMS Version gescheitert. Explanation: Before the database is accessed, SQLDBA determines the ORACLE version. This operation failed. Program reaction: Processing terminates. User action: Take into account any ORACLE error messages. BR0304I Starting the database instance %s... BR0304I Starten der Datenbank-Instanz %s... Explanation: The database instance is started by BRBACKUP using SQLDBA. Program reaction: There are none. User action: There are none. BR0305I Startup of database instance %s successful. BR0305I Starten der Datenbank-Instanz %s erfolgreich. Explanation: The database instance startup using SQLDBA was successful. Program reaction: There are none. User action: There are none. BR0306E Startup of database instance %s failed. BR0306E Starten der Datenbank-Instanz %s gescheitert. Explanation: The database instance startup using SQLDBA failed. Program reaction: Processing terminates. User action: Analyze the detailed error information and repeat the process once you have corrected the error. BR0307I Shutting down the database instance %s... BR0307I Stoppen der Datenbank-Instanz %s... Explanation: The database instance is shut down by BRBACKUP using SQLDBA. Program reaction: There are none. User action: There are none. BR0308I Shutdown of database instance %s successful. BR0308I Stoppen der Datenbank-Instanz %s erfolgreich. Explanation: The database instance shutdown using SQLDBA was successful. Program reaction: There are none. User action: There are none. BR0309E Shutdown of database instance %s failed. BR0309E Stoppen der Datenbank-Instanz %s gescheitert. Explanation: The database instance shutdown using SQLDBA failed. Program reaction: Processing terminates. User action: Analyze the detailed error information and repeat the process once you have corrected

the error. BR0310W Connect to database instance %s failed. BR0310W Verbindungsaufbau zu Datenbank-Instanz %s gescheitert. BR0310E Connect to database instance %s failed. BR0310E Verbindungsaufbau zu Datenbank-Instanz %s gescheitert. Explanation: The connection to the database instance could not be established. Program reaction: Processing continues (BR0310W) or terminates (BR0310E). User action: Analyze the ORACLE error message and, if required, repeat the process once you have corrected the error. BR0311E Connect to database instance %s during online backup failed. BR0311E Verbindungsaufbau zu Datenbank-Instanz %s waehrend Online-Sicherung gescheitert. Explanation: The database instance must be available during an online backup. This was not the case. Program reaction: Processing terminates. User action: Analyze the ORACLE error message and repeat the process once you have corrected the error. BR0312E Database instance %s shutdown during online backup. BR0312E Datenbank-Instanz %s gestoppt waehrend Online-Sicherung. Explanation: The database instance was shut down during an online backup. Program reaction: Processing terminates. User action: The database instance must always be active during an online backup. Repeat the processing. BR0313E Database instance %s started up during offline backup. BR0313E Datenbank-Instanz %s gestartet waehrend Offline-Sicherung. Explanation: The database instance was started up during an offline backup. Program reaction: Processing terminates. User action: The database instance must always remain shut down during an offline backup. Repeat the processing. BR0314E Collection of information on database files failed. BR0314E Sammlung der Information ueber Datenbankdateien gescheitert. Explanation: Information about the database files could not be determined. Program reaction: Processing terminates. User action: This is due to an SQL error that you must correct. Then restart the operation. BR0315I Alter tablespace %s begin backup successful. BR0315I Alter tablespace %s begin backup erfolgreich. Explanation: A tablespace was successfully switched to backup status. Program reaction: There are none. User action: There are none. BR0316E Alter tablespace %s begin backup failed. BR0316E Alter tablespace %s begin backup gescheitert. Explanation: The attempt to switch a tablespace to backup status failed. Program reaction: Processing terminates. User action: Analyze the ORACLE error message and repeat the process once you have corrected the error. BR0317I Alter tablespace %s end backup successful. BR0317I Alter tablespace %s end backup erfolgreich. Explanation: The termination of the backup status for the tablespace was successful. Program reaction: There are none. User action: There are none. BR0318E Alter tablespace %s end backup failed. BR0318E Alter tablespace %s end backup gescheitert. Explanation: The termination of the backup status for the tablespace failed. Program reaction: Processing terminates. User action: Analyze the ORACLE error message and repeat the process once you have corrected the error. BR0319I Control file copied to %s BR0319I Steuerdatei kopiert auf %s Explanation: A copy of the control file has been created. Such a copy is always created before you start an online backup. Program reaction: There are none. User action: There are none. BR0320E Copying of control file failed. BR0320E Kopieren der Steuerdatei gescheitert. Explanation: The copy of the control file could not be created. Program reaction: Processing terminates. User action: This error message is displayed during an online backup. Analyze the ORACLE error messages and correct the error. Then repeat the backup. BR0321I Switch to next online redo log file for database instance %s successful. BR0321I Umschalten zur naechsten Online-Redo-Log- Datei fuer Datenbank-Instanz %s erfolgreich. Explanation: The redo log file switch was successful, in other words, it was switched to the next online redo log file. This file switch is always performed after an online backup. Program reaction: There are none. User action: There are none. BR0322E Switch to next online redo log file for database instance %s failed. BR0322E Umschalten zur naechsten Online-Redo-Log- Datei fuer Datenbank-Instanz %s gescheitert. Explanation: The redo log file switch failed, in other words, the program could not switch to the next online redo log file. Program reaction: Processing terminates. User action: This error message is displayed during an online backup. Analyze the ORACLE error messages and correct the error. Then repeat the backup.

BR0323W 'Archive log list' failed. BR0323W 'Archive log list' gescheitert. BR0323E 'Archive log list' failed. BR0323E 'Archive log list' gescheitert. Explanation: The SQLDBA call for ARCHIVE LOG LIST failed. Program reaction: Processing continues (BR0323W) or terminates (BR0323E). User action: This is often due to an ORACLE problem. Analyze the ORACLE error messages and correct the error. Do not repeat the backup run if it has already finished. BR0324W Insertion of database log header failed. BR0324W Einfuegen des Datenbank-Protokollkopfs gescheitert. Explanation: An entry could not be added to table SDBAH. This error can occur when a message is sent by BRBACKUP/BRARCHIVE to the Computing Center Management System. Program reaction: The table is not changed and the process is continued. User action: This is often due to an ORACLE problem. Analyze the ORACLE error messages and correct the error, so it does not occur during the next run. BR0325W Writing of database log failed. BR0325W Schreiben des Datenbank-Protokolls gescheitert. Explanation: Table SDBAD could not be updated. Program reaction: The table is not changed and the process is continued. User action: This is often due to an ORACLE problem. Analyze the ORACLE error messages and correct the error, so it does not occur during the next run. BR0326W Update of database log header failed. BR0326W Aktualisieren des Datenbank-Protokollkopfs gescheitert. Explanation: An entry in table SDBAH could not be updated. Program reaction: The table is not changed and the process is continued. User action: This is often due to an ORACLE problem. Analyze the ORACLE error messages and correct the error, so it does not occur during the next run. BR0327W Disconnect from database instance %s failed. BR0327W Verbindungsabbau zu Datenbank-Instanz %s gescheitert. Explanation: The connection to the database instance could not be closed properly. Program reaction: The error is ignored and processing continues. User action: This is often due to an ORACLE problem. Analyze and correct the error and repeat the processing. BR0328E Database file %s from tablespace %s is already in backup status. BR0328E Datenbankdatei %s vom Tablespace %s ist schon in Backup-Status. Explanation: The tablespace to which the file belongs was just backed up, or the last backup was cancelled. The file is not updated to backup status. Program reaction: Processing terminates. User action: If the last backup was cancelled, manually enter the SQLDBA command ALTER TABLESPACE <tablespace name> END BACKUP. BR0329I Database instance %s is shut down - it will be started now. BR0329I Datenbank-Instanz %s ist gestoppt - sie wird jetzt gestartet. BR0329I Datenbank-Instanz %s ist gestoppt - sie wird jetzt gestartet. Explanation: BRBACKUP confirmation prompt as to whether the database instance can be started up before the backup is started. Program reaction: Waits for confirmation. User action: If message BR0256I is also displayed, decide whether you want to continue or cancel the program. BR0330I Trying 'alter tablespace end backup' using sqldba... BR0330I Versuch von 'alter tablespace end backup' ueber sqldba... Explanation: When an online backup is cancelled, BRBACKUP tries to cancel this status for all tablespaces in the backup status. If the direct attempt fails, BRBACKUP tries to use SQLDBA to do this indirectly. Program reaction: There are none. User action: There are none. BR0331I 'alter tablespace end backup' using sqldba successful. BR0331I 'alter tablespace end backup' ueber sqldba erfolgreich. Explanation: The attempt described in Message BR0330I was successful. Program reaction: There are none. User action: There are none. BR0332E 'alter tablespace end backup' using sqldba failed. BR0332E 'alter tablespace end backup' ueber sqldba gescheitert. Explanation: The attempt described in message BR0330I failed. Program reaction: Processing terminates. User action: Correct the errors that caused the online backup to terminate, and repeat the processing. BR0333W Status of tablespace %s is %s. BR0333W Status von Tablespace %s ist %s. Explanation: The tablespace status given in DBA_TABLESPACES is neither ONLINE nor READ_ONLY. Program reaction: There are none. User action: Decide whether the status is acceptable. If required, use the relevant SQLDBA command to change the status. BR0334W Status of database file %s is %s. BR0334W Status von Datenbankdatei %s ist %s. Explanation: The file status given in V$DATAFILE is neither ONLINE nor SYSTEM. Program reaction: There are none. User action: Decide whether the status is acceptable. If required, use the relevant SQLDBA command to change the status. BR0335W Status of online redo log file %s is %s. BR0335W Status von Online-Redo-Log-Datei %s ist %s. Explanation: The online redo log file status given in V$LOGFILE is neither ' ' nor STALE. Program reaction: There are none. User action: Decide whether the status is acceptable. If required, use the relevant SQLDBA command to change the status.

BR0339W Number of parallel instances different from number of threads. BR0339W Anzahl der parallelen Instanzen verschieden von der Anzahl der Threads. Explanation: The number of ORACLE instances (threads) defined by means of the init<DBSID>.sap parameter parallel_instances does not agree with the contents of table V$THREAD. Program reaction: The process can be continued despite this warning. User action: Check the init.sap parameter, if required, correct it and repeat the process. BR0340I Switching to next online redo log file for database instance %s... BR0340I Umschalten zur naechsten Online-Redo-Log- Datei fuer Datenbank-Instanz %s... Explanation: There is a redo log file change for the specified instance, and this means that it will be switched to the next online redo log file. Program reaction: There are none. User action: There are none. BR0351I Restoring %s BR0351I Zurueckladen von %s Explanation: The restore operation for a file was started. Program reaction: There are none. User action: There are none. BR0352I Decompressing %s BR0352I Dekomprimierung von %s Explanation: The decompression of a file was started. Program reaction: There are none. User action: There are none. BR0353I Verifying backup of %s BR0353I Verifikation der Sicherung von %s Explanation: The verification of a file was started. Program reaction: There are none. User action: There are none. BR0354I Decompressing and verifying the backup of %s BR0354I Dekomprimierung und Verifikation der Sicherung von %s Explanation: Decompression and verification of one file started in one process. Program reaction: There are none. User action: There are none. BR0355I from %s ... BR0355I von %s ... Explanation: Device or file from which the file is restored/decompressed/verified. Program reaction: There are none. User action: There are none. BR0357I Verifying volume %s in device %s ... BR0357I Verifikation von Datentraeger %s in Geraet %s ... Explanation: The verification of the backups of all files on a volume was started. Program reaction: There are none. User action: There are none. BR0359E Restore of %s from %s failed. BR0359E Zurueckladen von %s von %s gescheitert. Explanation: The restore operation for a file failed. Program reaction: Processing terminates. User action: Analyze the error messages and, if required, repeat the process. BR0360W Not enough disk space in %s for restore/verification, missing %4.3f MB. BR0360W Nicht genug Plattenplatz in %s fuer Zurueckladen/Verifikation, fehlt %4.3f MB. BR0360E Not enough disk space in %s for restore/verification, missing %4.3f MB. BR0360E Nicht genug Plattenplatz in %s fuer Zurueckladen/Verifikation, fehlt %4.3f MB. Explanation: The check for free disk space shows that the space is not sufficient for the restore/verification. Program reaction: Processing continues (BR0360W) or terminates (BR0360E). User action: Make sure that enough free disk space is available, and, if required, repeat the process. BR0361I Restore/verification of %s waiting for disk space... BR0361I Zurueckladen/Verifikation von %s wartet auf Plattenplatz... Explanation: During a parallel backup with verification, the directories from the value list of parameter compress_dir are used for the restore operation. The free space in these directories must be at least as large as the file to be backed up. If the free space is larger than the total size of the n largest files (n is the number of backup devices used), then no bottlenecks can occur with the directories. Program reaction: If temporary space shortages occur in the directories, BRBACKUP waits until other verification runs are finished. User action: If you want to avoid having to wait, provide more free disk space. BR0362I Verification of backup of %s successful. BR0362I Verifikation der Sicherung von %s erfolgreich. Explanation: Confirms that the verification of a saved file was successful. Program reaction: There are none. User action: There are none. BR0363E Verification of backup of %s failed. BR0363E Verifikation der Sicherung von %s gescheitert. Explanation: The verification of a saved file failed. Program reaction: Processing terminates. User action: Analyze and correct the error. BR0364E Verification of header files on volume in device %s failed. BR0364E Verifikation der Kopfdateien auf Datentraeger in Geraet %s gescheitert. Explanation: The verification of the volume header files failed: .tape.hdr0, init<DBSID>.ora, and init<DBSID>.sap. Program reaction: Processing terminates. User action: Analyze and correct the error.

BR0365E The contents of file %s and %s are different. BR0365E Der Inhalt der Dateien %s und %s ist ungleich. Explanation: The verification showed, that the contents of the saved file differ from those of the original file. The backup was not successful. Program reaction: Processing terminates. User action: Check your volume and the backup devices. Repeat the backup to make sure you have a valid backup available. BR0366E The size of the saved file %s is wrong. BR0366E Die Groesse der gesicherten Datei %s ist falsch. Explanation: The verification showed that the size of the saved file differs from that of the original file. The backup was not successful. Program reaction: Processing terminates. User action: Check your volume and the backup devices. Repeat the backup to make sure you have a valid backup available. BR0367W No verification on cpio continuation volume. BR0367W Keine Verifikation auf cpio-Fortsetzungs- Datentraeger. Explanation: Files that were saved on the cpio continuation volumes (including the files on the first volume) cannot be verified. Program reaction: No verification is performed. User action: There are none. BR0368W Backup of directory %s will not be verified. BR0368W Sicherung von Verzeichnis %s wird nicht verifiziert. Explanation: The backup of the contents of a directory cannot be verified. Program reaction: No verification is performed. User action: There are none. This is a limitation of BRBACKUP. BR0369E %s is not a directory. BR0369E %s ist kein Verzeichnis. Explanation: The path displayed should refer to a directory. Program reaction: Processing terminates. User action: Correct your entry. BR0370I Directory %s created. BR0370I Verzeichnis %s angelegt. Explanation: A directory was created. Program reaction: There are none. User action: There are none. BR0371I Link from %s to %s created. BR0371I Link von %s zu %s angelegt. Explanation: A symbolic link was created. Program reaction: There are none. User action: There are none. BR0373I Perhaps cpio_disk_flags '%s' should be used. BR0373I Vielleicht sollten cpio_disk_flags '%s' benutzt werden. Explanation: Special cpio flags are required when backing up or restoring directories to/from disk. Program reaction: Processing terminates due to previous errors. User action: Correct the parameter definition for cpio_disk_flags in profile init<DBSID>.sap. BR0374I %d of %d files restored by backup utility. BR0374I %d von %d Dateien durch Backup-Utility zurueckgeladen. BR0374E %d of %d files restored by backup utility. BR0374E %d von %d Dateien durch Backup-Utility zurueckgeladen. Explanation: The number of files successfully restored by the external backup program is displayed. If the number of restored files was lower than the number of files that were supposed to be restored, errors occurred. Program reaction: Processing continues (BR0374I) or terminates (BR0374E). User action: Check the other messages from the external backup program. If required, contact the supplier of the external backup program (the supplier of interface program BACKINT). BR0375E Error in backup utility while restoring file %s BR0375E Fehler in Backup-Utility beim Zurueckladen der Datei %s Explanation: The external backup program reported an error while restoring the file. Program reaction: Processing terminates. User action: Check the other messages from the external backup program. If required, contact the supplier of the external backup program (the supplier of interface program BACKINT). BR0376E Unknown file %s restored by backup utility. BR0376E Unbekannte Datei %s zurueckgeladen durch Backup-Utility. Explanation: A file that was not part of the restore request was restored by the external backup program. Program reaction: Processing terminates. User action: Contact the supplier of the external backup program (the supplier of interface program BACKINT). BR0377E BRTOOLS call failed. BR0377E BRTOOLS-Aufruf gescheitert. Explanation: A call from program BRTOOLS failed. This program is used for internal purposes, for example, when verifying backups. Program reaction: Processing terminates. User action: Analyze the other error messages and correct the error. BR0378W Volume name %s not unique - automatic restore impossible. BR0378W Datentraegername %s nicht eindeutig - automatisches Zurueckladen ummoeglich. BR0378E Volume name %s not unique - automatic restore impossible. BR0378E Datentraegername %s nicht eindeutig - automatisches Zurueckladen ummoeglich. Explanation: To distinguish the volumes during a restore, their names must be different in the backup. Program reaction: Processing continues (BR0378W, during backup) or terminates (BR0278E, during restore). User action: Make sure that the volume names are different in both parameters.

BR0379I Distribution of files on volume %s: BR0379I Verteilung der Dateien auf Datentraeger %s: Explanation: The SAP utility was called using option -i force. As a result, a list of the file distribution is displayed. Program reaction: There are none. User action: There are none. BR0380I Duration of backup for files saved to volume %s: BR0380I Dauer der Sicherung von Dateien gesichert auf Datentraeger %s: Explanation: BRBACKUP/BRARCHIVE was called using option -o time. As a result, BRBACKUP/BRARCHIVE displays a list with backup durations. Program reaction: There are none. User action: There are none. BR0381I Duration of restore for files saved to volume %s: BR0381I Dauer des Zurueckladens von Dateien gesichert auf Datentraeger %s: Explanation: BRRESTORE was called using option -o time. As a result, BRRESTORE issues a list with restore durations. Program reaction: There are none. User action: There are none. BR0383E Raw disk %s not found. BR0383E Raw-Platte %s nicht gefunden. Explanation: A file is to be restored on a raw device that does not exist. Program reaction: Termination of the process. User action: Compare the database configuration with the hardware configuration and, if required, adjust the hardware configuration. BR0384E %s is not a raw disk. BR0384E %s ist keine Raw-Platte. Explanation: A backup of a file located on a raw device can only be restored to a raw device. Program reaction: Termination of the process. User action: Compare the database configuration with the hardware configuration and, if required, adjust the hardware configuration. BR0385E Compress of %s waiting for disk space... BR0385E Komprimierung von %s wartet auf Plattenplatz... Explanation: During parallel compression, the directories from the value list of parameter compress_dir are used for restoring. The free space in these directories must be at least as large as the largest file to be compressed. Program reaction: If there is a temporary shortage of space in these directories, BRBACKUP waits until other compression runs have finished. User action: If you want to avoid having to wait, provide more free disk space. BR0401I BRRESTORE %s BR0401I BRRESTORE %s Explanation: BRRESTORE version number. This number is independent of the SAP release number. Program reaction: There are none. User action: There are none. BR0402I BRRESTORE terminated successfully. BR0402I BRRESTORE erfolgreich beendet. Explanation: BRRESTORE terminates successfully with return code 0. Program reaction: There are none. User action: There are none. BR0403I BRRESTORE terminated with warnings. BR0403I BRRESTORE beendet mit Warnungen. Explanation: BRRESTORE ended with return code 1. The restore was performed successfully. Program reaction: There are none. User action: Pay careful attention to the warnings. Analyze them and, if required, correct the cause of these warnings. BR0404I BRRESTORE terminated with errors. BR0404I BRRESTORE beendet mit Fehlern. Explanation: BRRESTORE finished with a return code greater than 1. Program reaction: The BRRESTORE run was terminated. User action: Analyze and correct the specified errors. Then repeat the restore operation. BR0405I Start of database restore: %s %s %s BR0405I Start des Datenbank-Zurueckladens: %s %s %s Explanation: Start message for BRRESTORE. The action ID (r<encoded timestamp>), the function ID (extension), and the start timestamp (date, time) are listed in sequence to characterize the restore process. The action ID and the function ID form the file name of the detail BRBACKUP log. Program reaction: There are none. User action: There are none. BR0406I End of database restore: %s %s %s BR0406I Ende des Datenbank-Zurueckladens: %s %s %s Explanation: End message for BRRESTORE. The action ID, function ID, and end timestamp are issued. See BR0405I. Program reaction: There are none. User action: There are none. BR0407I Restore of database: %s BR0407I Zurueckladen der Datenbank: %s Explanation: Name of the database, to which the files for the restore operation belong is issued. Program reaction: There are none. User action: There are none. BR0408I BRRESTORE action ID: %s BR0408I BRRESTORE action ID: %s Explanation: The action ID contains an encoded timestamp that specifies the starting time of

BRRESTORE. This timestamp appears at the beginning of the file name of the detail BRRESTORE log, after an "r". Program reaction: There are none. User action: There are none. BR0409I BRRESTORE function ID: %s BR0409I BRRESTORE Funktions-ID: %s Explanation: The function ID (extension) indicates the mode of the restore process. It appears second in the file name of the detailed BRARCHIVE log. Program reaction: There are none. User action: There are none. BR0410I Tablespaces for restore: %s BR0410I Tablespaces fuer Zurueckladen: %s Explanation: List of tablespaces to be restored. When brrestore - all or brrestore -full are specified, the files of all tablespaces are restored. Program reaction: There are none. User action: There are none. BR0411I Database files for restore: %s BR0411I Datenbankdateien fuer Zurueckladen: %s Explanation: List of the database files to be restored. Program reaction: There are none. User action: There are none. BR0412I Non-database files for restore: %s BR0412I Nicht-Datenbankdateien fuer Zurueckladen: %s Explanation: List of non-database files to be restored. Program reaction: There are none. User action: There are none. BR0413I Directories for restore: %s BR0413I Verzeichnisse fuer Zurueckladen: %s Explanation: List of directories to be restored. Program reaction: There are none. User action: There are none. BR0414I Offline redo log file/s for restore from database instance %s: %s BR0414I Offline-Redo-Log-Datei/en fuer Zurueckladen von Datenbank-Instanz %s: %s Explanation: List of offline redo log files to be restored. The log sequence numbers of these files are displayed. BRRESTORE was called with one of the options -a|-a1|- a2. Program reaction: There are none. User action: There are none. BR0415I Files for restore using backup utility ID %s: %s BR0415I Dateien fuer Zurueckladen mittels Backup- Utility-ID %s: %s Explanation: List of the files to be restored using an external backup program. Program reaction: There are none. User action: There are none. BR0416I %d files found to restore, total size %4.3f MB. BR0416I %d Dateien zum Zurueckladen gefunden, Gesamtgroesse %4.3f MB. Explanation: The total number and the total size of the files to be restored is displayed. Program reaction: There are none. User action: There are none. BR0417E No files found for restoring. BR0417E Keine Dateien zum Zurueckladen gefunden. Explanation: No valid files were found for restoring. Program reaction: Processing terminates. User action: Correct the call options for BRRESTORE. BR0418I %d of %d files restored - %4.3f MB of %4.3f MB done. BR0418I %d von %d Dateien zurueckgeladen - %4.3f MB von %4.3f MB fertig. Explanation: Logs the current status of the restore process. Program reaction: There are none. User action: There are none. BR0419I Files will be restored from backups: %s BR0419I Dateien werden zurueckgeladen von Sicherungen: %s Explanation: The name of the log of backup BRBACKUP that is to be used, is displayed. Program reaction: There are none. User action: There are none. BR0420I Files will be restored from directories: %s BR0420I Dateien werden zurueckgeladen von Verzeichnissen: %s Explanation: The names of the directories, in which backup BRBACKUP was stored (backed up on disk), are issued. Program reaction: There are none. User action: There are none. BR0421I Backup device type for restore: %s BR0421I Sicherungs-Geraetetyp fuer Zurueckladen: %s Explanation: The type of backup devices that will be used for the restore is issued. Program reaction: There are none. User action: There are none. BR0422I File for restore directly from tape volume: %s BR0422I Datei fuer Zurueckladen direkt von Band- Datenträger: %s Explanation: The position of the file on tape or its symbolic name (init_ora, init_sap, det_log, sum_log, reorg_log) is issued. BRRESTORE was called using option -n. Program reaction: There are none. User action: There are none.

BR0423I Files will be decompressed. BR0423I Dateien werden dekomprimiert. Explanation: Confirms that the files are decompressed during the restore. The backup that is used for the restore was created using software compression (compress = yes). Program reaction: There are none. User action: There are none. BR0424I Files will not be decompressed. BR0424I Dateien werden nicht dekomprimiert. Explanation: Confirms that the files are decompressed during the restore. The backup used for the restore did not use software compression (compress = no). Program reaction: There are none. User action: There are none. BR0425I Files will be decompressed by hardware. BR0425I Dateien werden dekomprimiert mit hardware. Explanation: Confirms that the files are decompressed by the hardware during the restore. The backup that is used for the restore was created using hardware compression (compress = hardware). Program reaction: In this case, BRRESTORE has no effect on the decompression operation. BRRESTORE proceeds as if no compression had taken place. User action: Make sure that the backup device is configured properly. BR0426W Directories do not need to be decompressed. BR0426W Verzeichnisse muessen nicht dekomprimiert werden. Explanation: Although the software decompression is active, the directory contents are decompressed, since they were not compressed during the backup. Program reaction: There are none. User action: There are none. BR0427W All files will be restored to the new Oracle home directory! BR0427W Alle Dateien werden in das neue Oracle- Home-Verzeichnis zurueckgeladen! Explanation: The current settings for ORACLE_HOME and ORACLE_SID are different from those during the backup. Program reaction: The new values have priority. User action: This method can be used to create a copy of the database. Make sure you know which other steps are required. BR0428W File %s will be overwritten. BR0428W Datei %s wird ueberschrieben. Explanation: An existing file is overwritten during the restore operation. Program reaction: There are none. User action: There are none. BR0429W Directory %s will be overwritten. BR0429W Verzeichnis %s wird ueberschrieben. Explanation: An existing directory is overwritten during the restore operation. Program reaction: There are none. User action: There are none. BR0430E Start BRRESTORE either with '%s' or '%s' option. BR0430E Starten Sie BRRESTORE entweder mit '%s'- oder '%s'-Option. Explanation: BRRESTORE was called with contradictory options. Program reaction: Processing terminates. User action: Use only one of the displayed options. BR0431E BRRESTORE with option '%s' currently running or was killed. BR0431E BRRESTORE mit Option '%s' laeuft gerade oder wurde abgebrochen. Explanation: A BRRESTORE process is already running or was terminated. Program reaction: BRRESTORE is not started. User action: When another BRRESTORE process is running, you have to wait until it has terminated. If a BRRESTORE run terminates, refer to the other messages. BR0432I Please delete the file %s if BRRESTORE was killed. BR0432I Bitte die Datei %s loeschen, wenn BRRESTORE abgebrochen wurde. Explanation: This message appears in connection with BR0431E. Program reaction: BRRESTORE is not started. User action: Check whether BRRESTORE is running (for example using the UNIX command ps). If not, delete the specified file and restart BRRESTORE. BR0433E Setting BRRESTORE lock failed. BR0433E Setzen von BRRESTORE-Sperre gescheitert. Explanation: This message appears in connection with BR0431E. Program reaction: The BRRESTORE processing terminates because the lock cannot be set. User action: See BR0431E and BR0432I. BR0435E Last successful backup not found in %s BR0435E Letzte erfolgreiche Sicherung nicht gefunden in %s Explanation: The requested backup could not be found in the BRBACKUP summary log. Program reaction: Processing terminates. User action: Use option -b to specify the backup to use for the restore operation. BR0436W Backup %s is not a full database backup. BR0436W Sicherung %s ist keine Vollsicherung der Datenbank. Explanation: BRRESTORE was started with parameter backup_mode = all|full or option -m all|full (all is the default value), but the selected backup was not a complete backup of the database. Program reaction: All the files saved during this backup are restored (full). When all is used, no redo log files or control file are restored. User action: Check whether you really want to use this backup. BR0437W File %s to be restored was not backed up. BR0437W Zurueckzuladende Datei %s wurde nicht gesichert. BR0437E File %s to be restored was not backed up. BR0437E Zurueckzuladende Datei %s wurde nicht gesichert. Explanation: The file to be restored was not found in the selected backup. Program reaction: Processing continues (BR0437W) or terminates (BR0437E).

User action: Check the parameter backup_mode or option -m and, if required, correct the entries you have made. BR0438W Redo log sequence number %d not found in %s BR0438W Redo-Log-Sequenznummer %d nicht gefunden in %s Explanation: The archived redo log files to be restored were not found in the summary BRARCHIVE log. Program reaction: The offline redo log file with this log sequence number is not restored. User action: Check the used options -a|-a1|-a2 and, if required, correct them. BR0439E No offline redo log files found in %s for restoring. BR0439E Keine Offline-Redo-Log-Dateien in %s zum Zurueckladen gefunden. Explanation: None of the offline redo log files to be restored were found in the summary BRARCHIVE log. Program reaction: Processing terminates. User action: Check the used options -a|-a1|-a2 and, if required, correct them. BR0440E Unknown database instance %s defined in option %s. BR0440E Unbekannte Datenbank-Instanz %s definiert in Option %s. Explanation: The name of the database instance that is specified in the BRRESTORE option -a|-a1|-a2 is unknown. Program reaction: Processing terminates. User action: Check the used options -a|-a1|-a2 and, if required, correct them. BR0441E Database instance %s not unique in option %s. BR0441E Datenbank-Instanz %s nicht eindeutig in Option %s. Explanation: The name of the database instance that is specified in the BRRESTORE option -a|-a1|-a2 is not unique. Program reaction: Processing terminates. User action: Check the used options -a|-a1|-a2 and, if required, correct them. BR0442I Second copy of offline redo log files will be used for restore. BR0442I Zweite Kopie von Offline-Redo-Log-Dateien wird fuers Zurueckladen benutzt. Explanation: BRRESTORE was called with option -a2|- archive2, in order to restore offline redo log files. Program reaction: There are none. User action: There are none. BR0451E Message %s not found in %s BR0451E Meldung %s nicht gefunden in %s Explanation: One of the required messages of the BRBACKUP/BRARCHIVE log header was not found. This could indicate an internal error, or that the log has been changed manually. Program reaction: Processing terminates. User action: If the log was changed manually, undo the changes. BR0452E Continuation of message %s not found in %s BR0452E Fortsetzung von Meldung %s nicht gefunden in %s Explanation: The continuation of a message that extends over several lines was not found in the BRBACKUP/BRARCHIVE log file. This could indicate an internal error, or that the log has been changed manually. Program reaction: Processing terminates. User action: If the log was changed manually, undo the changes. BR0453W Error message found in %s: BR0453W Fehlermeldung in %s gefunden: Explanation: The error message was not found in the BRBACKUP/BRARCHIVE log. This could negatively affect the restore operation. Program reaction: The message is ignored and the operation continues. User action: Analyze the message and decide whether you want to continue (message BR0256I is displayed). BR0454W Values of %s are different: current '%s', backup %s '%s'. BR0454W Werte von %s sind verschieden: aktuell '%s', Sicherung %s '%s'. BR0454E Values of %s are different: current '%s', backup %s '%s'. BR0454E Werte von %s sind verschieden: aktuell '%s', Sicherung %s '%s'. Explanation: The current parameter value differs from the value for the backup time. Program reaction: Processing continues (BR0454W) or terminates (BR0454E). User action: BRRESTORE automatically adjusts some values and you have to manually adjust others. Restart BRRESTORE with the adjusted parameter values. BR0455W Value '%s' of %s will be used for restore. BR0455W Wert '%s' von %s wird benutzt fuer Zurueckladen. Explanation: The current parameter value differs from the value for the backup time. Program reaction: BRRESTORE automatically adjusts the value. User action: Decide whether or not you should accept this adjusted parameter value (BR0256I is displayed). BR0456W Probable the database must be recovered due to restore from online backup! BR0456W Wahrscheinlich muss die Datenbank wiederhergestellt werden aufgrund Zurueckladens von Online-Sicherung! Explanation: BRRESTORE reports that an online backup was selected. Program reaction: There are none. User action: The database must be recovered after the restore of the online backup (ORACLE recovery required). BR0457W Probable the database must be recovered due to partial restore! BR0457W Wahrscheinlich muss die Datenbank wiederhergestellt werden aufgrund Teilzurueckladens! Explanation: BRRESTORE reports that the backup is partially restored. Program reaction: There are none. User action: The database must be recovered after the partial restore of the online backup (ORACLE recovery required). BR0458E Information about backup file %s not found in log header. BR0458E Information ueber gesicherte Datei %s nicht gefunden im Protokollkopf. Explanation: All the saved files must be described in the log header of the BRBACKUP backup that

you have selected. This is not the case. This could indicate an internal error, or that the log has been changed manually. Program reaction: Processing terminates. User action: If the log was changed manually, undo this change and repeat the processing. BR0459W Backup %s terminated with errors. BR0459W Sicherung %s beendet mit Fehlern. Explanation: The backup terminates with errors. This could negatively affect the restore operation. Program reaction: Waits for confirmation that the process should continue. User action: Analyze the message and decide whether you want to continue processing. BR0460W Termination message not found in %s - log file incomplete. BR0460W Ende-Meldung nicht gefunden in %s - Protokoll unvollstaendig. Explanation: The message about the termination of the backup was not found in the backup log. Case 1: The volume restored the log. Case 2: You changed the log manually. Program reaction: Waits for confirmation that the process should continue. User action: Case 1: Continue processing. Case 2: Undo the manual changes, cancel the processing, and then repeat the process. BR0461W Redo log sequence number in line %d in %s not ascending. BR0461W Redo-Log-Sequenznummer in Zeile %d in %s nicht aufsteigend. Explanation: The log sequence numbers that are listed in the summary BRARCHIVE log should be stored in ascending order. If this isn't the case, it means that a RESET LOGS was executed, which is quite common after an incomplete recovery. Program reaction: All offline redo log files that were created before the RESET LOGS are ignored. User action: Analyze the message and decide whether you want to continue processing. BR0462W All lines in %s till line %d will be ignored! BR0462W Alle Zeilen in %s bis zu Zeile %d werden ignoriert! Explanation: Appears together with BR461X if a RESET LOGS was performed. Duplicate log sequence numbers were assigned. Program reaction: All offline redo log files that were created before the RESET LOGS are ignored. User action: Analyze the message and decide whether you want to continue processing. BR0464W Line %d in %s ignored because of different backup device types. BR0464W Zeile %d in %s ignoriert aufgrund verschiedener Sicherungs-Geraetetypen. Explanation: Offline redo log files can only be restored when the device types used for the backup and those specified for the restore are compatible (the following combinations of backup_dev_type parameters are not allowed, for example: tape and util_file, pipe and util_file. However, the combination of tape and pipe is allowed). Program reaction: Processing terminates. User action: Correct the current value of the parameter and repeat the processing. BR0465E Wrong value of %s for the first offline redo log file found. BR0465E Falscher Wert von %s fuer die erste gefundene Offline-Redo-Log-Datei. Explanation: The parameter value during the backup of the first offline redo log file to be restored and the current value (from Profile init<DBSID>.sap or provided by the relevant call option) for the file to be restored are contradictory. This message appears together with BR0464W. Program reaction: Processing terminates. User action: Correct the current value of the parameter and repeat the processing. BR0466I Start BRRESTORE one after the other for each backup device type! BR0466I Starten Sie BRRESTORE nacheinander fuer jeden Sicherungs-Geraetetyp! Explanation: Offline redo log files must be restored in separate BRRESTORE runs if their backup devices specifications are not compatible. This message appears together with BR0464W. Program reaction: Processing terminates. User action: Start BRRESTORE with the requested options for each of the requested backup devices. BR0467W Line %d in %s ignored because of different compress types. BR0467W Zeile %d in %s ignoriert aufgrund verschiedener Komprimierungstypen. Explanation: Offline redo log files can only be restored if the compression type used during backup is compatible with the compression type specified for restoring. Program reaction: Processing terminates. User action: Correct the current value of the parameter and repeat the processing. BR0468I Start BRRESTORE one after other for each compress type. BR0468I Starten Sie BRRESTORE nacheinander fuer jeden Komprimierungstyp. Explanation: Offline redo log files must be restored in separate BRRESTORE runs if their compression type specifications are not compatible. This message appears together with BR0467W. Program reaction: Processing terminates. User action: Start BRRESTORE with the requested options for each of the requested compression types. BR0483I Terminating BRARCHIVE processing after 10 days... BR0483I BRARCHIVE-Verarbeitung wird nach 10 Tagen beendet... Explanation: BRARCHIVE run that has been started using the fill option, terminates automatically after 10 days. This is normal for BRARCHIVE. This system response is due to technical reasons relating to the program and cannot be changed. Program reaction: Processing terminates. User action: Restart BRARCHIVE. We recommend that you restart BRARCHIVE weekly using the following commands: brarchive -u / -f stop -c brarchive -u / -f ...

Other Attributes

ORACLEDatabase System

Validity

This document is not restricted to a software component or software component version

References

This document refers to:

SAP Notes

This document is referenced by:

SAP Notes (2)

442395 Descriptions of specific BR messages

43494 Collective note: BRBACKUP, BRARCHIVE, BRRESTORE

43494 Collective note: BRBACKUP, BRARCHIVE, BRRESTORE

442395 Descriptions of specific BR messages

17163 brarchive brbackup messages and codes

Documents

brarchive log

brarchive run

s br0002i brarchive

programs brarchive

return codes brarchive

brarchive version number

s explanation

user action