Messages from BR308I to BR339W (SAP Library - Database Administration (Oracle) with SAPDBA)

Messages from BR308I to BR339W

BR308I Shutdown of database instance %s successful.

Explanation: The database instance shutdown via SQLDBA was successful.

Program response: None.

User action: None.

BR309E Shutdown of database instance %s failed.

Explanation: The database instance shutdown via SQLDBA failed.

Program response: Processing terminated.

User action: Analyze the detailed error information and repeat the operation, once you correct the error.

BR310W Connect to database instance %s failed.
BR310E Connect to database instance %s failed.

Explanation: The connection to the database instance could not be established.

Program response: Processing is continued (BR310W) or terminated (BR310E).

User action: Analyze the ORACLE error message and - if necessary - repeat the operation once you correct the error.

BR311E Connect to database instance %s during online backup failed.

Explanation: The database instance must be available during an online backup. This was not the case.

Program response: Processing terminated.

User action: Analyze the ORACLE error message and repeat the operation once you have corrected the error.

BR312E Database instance %s shutdown during online backup.

Explanation: The database instance was shut down during an online backup.

Program response: Processing terminated.

User action: The database instance must always be active during an online backup. Repeat the operation.

BR313E Database instance %s started up during offline backup.

Explanation: The database instance was started up during an offline backup.

Program response: Processing terminated.

User action: The database instance must always remain shut down during an offline backup. Repeat the operation.

BR314E Collection of information on database files failed.

Explanation: Information about the database could not be determined.

Program response: Processing terminated.

User action: Involves an SQL error that you must correct. Then restart the operation.

BR315I Alter tablespace %s begin backup successful.

Explanation: A tablespace was successfully switched to backup status.

Program response: None.

User action: None.

BR316E Alter tablespace %s begin backup failed.

Explanation: The attempt to switch a tablespace to backup status failed.

Program response: Processing terminated.

User action: Analyze the ORACLE error message and repeat the operation once you have corrected the error.

BR317I Alter tablespace %s end backup successful.

Explanation: The termination of the backup status for the tablespace was successful.

Program response: None.

User action: None.

BR318E Alter tablespace %s end backup failed.

Explanation: The termination of the backup status for the tablespace failed.

Program response: Processing terminated.

User action: Analyze the ORACLE error message and repeat the operation once you have corrected the error.

BR319I Control file copied to %s

Explanation: A copy of the control file has been created. Such a copy is always created when you start an online backup.

Program response: None.

User action: None.

BR320E Copying of control file to %s failed.

Explanation: The copy of the control file could not be created.

Program response: Processing terminated.

User action: This error message is displayed during an online backup. Analyze the ORACLE error messages and correct the error(s). Then repeat the backup.

BR321I Switch to next online redo log file for database instance %s successful.

Explanation: The redo log file switch was successful, that is, the program switched to the next online redo log file. This file switch is always performed after an online backup.

Program response: None.

User action: None.

BR322E Switch to next online redo log file for database instance %s failed

Explanation: The redo log file switch failed, that is, the program could not switch to the next online redo log file.

Program response: Processing terminated.

User action: This error message is displayed during an online backup. Analyze the ORACLE error messages and correct the error(s). Then repeat the backup.

BR323W 'Archive log list' for database instance %s failed.
BR323E 'Archive log list' for database instance %s failed.

Explanation: The SQLDBA call for ARCHIVE LOG LIST failed.

Program response: Processing is continued (BR323W) or terminated (BR323E).

User action: Often involves an ORACLE problem. Analyze the ORACLE error messages and correct the error(s). If the backup run was already finished, it does not need to be repeated.

BR324W Insertion of database log header failed.

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 response: The table is not changed, and the operation is continued.

User action: Often involves an ORACLE problem. Analyze the ORACLE error messages and correct the error(s), so that it no longer occurs during the next run.

BR325W Writing of database log failed.

Explanation: Table SDBAD could not be updated.

Program response: The table is not changed, and the operation is continued.

User action: Often involves an ORACLE problem. Analyze the ORACLE error messages and correct the error(s), so that it no longer occurs during the next run.

BR326W Update of database log header failed.

Explanation: An entry in table SDBAH could not be updated.

Program response: The table is not changed, and the operation is continued.

User action: Often involves an ORACLE problem. Analyze the ORACLE error messages and correct the error(s), so that it no longer occurs during the next run.

BR327W Disconnect from database instance %s failed.

Explanation: The connection to the database instance could not be closed properly.

Program response: The error is ignored and processing is continued.

User action: Often involves an ORACLE problem. Analyze and correct the error(s) and repeat the operation.

BR328E Database file %s from tablespace %s is already 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 changed to backup status.

Program response: Processing terminated.

User action: If the last backup was cancelled, manually enter the SQLDBA command ALTER TABLESPACE <tablespace name> END BACKUP .

BR329I Database instance %s is shut down - it will be started now.

Explanation: BRBACKUP confirmation prompt as to whether the database instance can be started up before the backup is started.

Program response: Waits for confirmation.

User action: When message BR256I is displayed, decide whether you want to continue or cancel the program.

BR330I Trying 'alter tablespace end backup' using sqldba...

Explanation: When an online backup is cancelled, BRBACKUP tries to change all the tablespaces from backup status. When the direct attempt fails, BRBACKUP tries to use SQLDBA.

Program response: None.

User action: None.

BR331I 'alter tablespace end backup' using sqldba successful.

Explanation: The attempt described in message BR330I was successful.

Program response: None.

User action: None.

BR332E 'alter tablespace end backup' using sqldba failed.

Explanation: The attempt described in message BR330I failed.

Program response: Processing terminated.

User action: Correct the error(s) that caused the online backup to terminate and repeat the operation.

BR333W Status of tablespace %s is %s.

Explanation: The tablespace status given in DBA_TABLESPACES is neither "ONLINE" nor "READ_ONLY".

Program response: None.

User action: Decide whether the status is acceptable. If required, change the status with the corresponding SQLDBA command.

BR334W Status of database file %s is %s.

Explanation: The file status given in V$DATAFILE is neither "ONLINE" nor "SYSTEM".

Program respsonse: None.

User action: Decide whether the status is acceptable. If required, change the status with the corresponding SQLDBA command.

BR335W Status of online redo log file %s is %s.

Explanation: The online redo log file status given in V$LOGFILE is neither " " nor "STALE".

Program response: None.

User action: Decide whether the status is acceptable. If required, change the status with the corresponding SQLDBA command.

BR339W Number of parallel instances different from number of threads.

Explanation: The number of ORACLE instances (threads) defined with the init<DBSID>.sap parameter parallel_instances does not agree with the contents of table V$THREAD.

Program response: The process can be continued despite this warning.

User action: Check the init.sap parameter, correct it if necessary and repeat the process.