Messages from BR270W to BR307I (SAP Library - Database Administration (Oracle) with SAPDBA)

Messages from BR270W to BR307I

BR270W Unknown process with ID %d terminated.

Explanation: A subprogram that was not started by the main program was terminated.

Program response: Termination of the subprogram is ignored and processing is continued.

User action: Could involve an ORACLE background process error or an internal error.

BR271W Read from a pipe failed for '%s'
BR271E Read from a pipe failed for '%s'

Explanation: The reading of messages from subprograms whose output was routed through a pipe mechanism failed.

Program response: Processing is continued (BR271W) or terminated (BR271E).

User action: Analyze the other error messages and repeat the operation, once you correct the error.

BR272W Execution of program '%s' through pipe failed.
BR272E Execution of program '%s' through pipe failed.

Explanation: The start of subprograms whose output was routed through a pipe mechanism failed.

Program response: Processing is continued (BR272W) or terminated (BR272E).

User action: Analyze the other error messages and repeat the operation, once you correct the error.

BR273W Determination of file status for %s failed.
BR273E Determination of file status for %s failed.

Explanation: Information about a file could not be determined, possibly because the file does not exist or the user is not authorized, for example.

Program response: Processing is continued (BR273W) or terminated (BR273E).

User action: Check the other error messages and correct the error(s).

BR274W File %s not found.
BR274E File %s not found.

Explanation: The specified file does not exist.

Program response: Processing is continued (BR274W) or terminated (BR274E).

User action: The action depends on the file category.

BR275E File %s is not a regular file.

Explanation: Symbolic links, named pipes, and device files (special files) cannot be backed up.

Program response: Processing terminated.

User action: The action depends on the file category.

BR276E File/directory %s is empty.

Explanation: Files with length 0 and empty directories cannot be backed up.

Program response: Processing terminated.

User action: None.

BR277W Determination of disk volume status for %s failed.
BR277E Determination of disk volume status for %s failed.

Explanation: Information about a disk volume could not be determined. The disk volume status is used mainly to determine the freespace on a disk.

Program response: Processing is continued (BR277W) or terminated (BR277E).

User action: Correct the error and then start the operation again.

BR278W Command output of '%s': %s
BR278E Command output of '%s': %s

Explanation: The error messages from this command are displayed. In most cases, messages from the cpio or mt commands are involved. A few examples:

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 for backup cannot be read. In most cases, this involves hardware problems on the disk where 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 for backup cannot be written to the volume. In most cases, this involves hardware problems with the volume or the backup device.
No such device or address [sh: ]/dev/...:cannot create	The backup device is not responding, e.g. when no volume (tape) has been mounted in the backup device.
[cpio: ]cannot open...	The input or output file cannot be open. In most cases, this involves authorization problems with the operating system user.
[cpio: ]can’t open /dev/tty to prompt for more media	The physical end of the tape was reached. Because a parallel backup is being performed or the option -c force was used, however, cpio is not able to request a continuation volume. The tape size (parameter tape_size ) must be reduced.

Program response: Processing is continued (BR278W) or terminated (BR278E).

User action: Analyze the error messages. Correct the error(s) listed in the message displayed for the subprogram command.

BR279W Return code from '%s': %d
BR279E Return code from '%s': %d

Explanation: The return code of a command is displayed. This involves the return code of a subprogram started by the main program. The message often appears together with BR278X.

Program response: Processing is continued (BR279W) or terminated (BR279E).

User action: Also analyze the error messages from the subprogram (BR278X) and correct the error(s).

BR280I Time stamp %s

Explanation: The timestamp is displayed.

Program response: None.

User action: None.

BR281W Program interrupted by signal %d.

Explanation: The program was interrupted by a SIGINT signal from the user or the system.

Program response: Message BR256I is then displayed. Waits for your entry.

User action: Decide whether you want to continue or cancel the program. Continuation of the program will probably fail.

BR282E Directory %s not found.

Explanation: The specified directory does not exist.

Program response: Processing terminated.

User action: Analyze the situation. If necessary, repeat the operation and enter the correct directory name.

BR283E Command/Output buffer overflow.

Explanation: The buffer for the command lines and command output overflowed.

Program response: The buffer contents are displayed and processing is terminated.

User action: Probably involves an internal error. Please contact SAP.

BR284I Time stamp %s, elapsed time: %s

Explanation: An extended timestamp is displayed when you use option -o time . The time that has elapsed since the last timestamp is displayed.

Program response: None.

User action: None.

BR285I This function can take several seconds/minutes - be patient.

Explanation: An action was started that may take several seconds/minutes.

Program response: Action running.

User action: None. Wait for the action to finish.

BR286W Size of file %s is different from Oracle file size.

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.
This warning is also sent if the size of the file changed during an online backup with the Oracle auto-extend mechanism. The size given in the header of the BRBACKUP log is then no longer up-to-date.

Program response: 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 can possibly correct the situation by performing a recovery. Seek help from an ORACLE specialist before you start a recovery.
When auto-extending a file take the increased storage requirements into account when reloading the file.

BR301W SQL error %d at location %s-%d
BR301E SQL error %d at location %s-%d

Explanation: An SQL error has occurred.

Program response: Processing is continued (BR301W) or terminated (BR301E).

User action: Check the SQL code and repeat the operation.

BR302E SQLDBA call for database instance %s failed.

Explanation: The call of the SQLDBA program failed.

Program response: Processing terminated.

User action: This error often occurs when starting up and shutting down a database instance. Check any ORACLE error messages. Correct the error and then repeat the operation.

BR303E Determination of Oracle RDBMS version failed.

Explanation: Before the database is accessed, SQLDBA determines the ORACLE version. This operation failed.

Program response: Processing terminated.

User action: Note the ORACLE error messages.

BR304I Starting the database instance %s...

Explanation: The database instance is being started by BRBACKUP via SQLDBA.

Program response: None.

User action: None.

BR305I Startup of database instance %s successful.

Explanation: The database instance startup via SQLDBA was successful.

Program response: None.

User action: None.

BR306E Startup of database instance %s failed.

Explanation: The database instance startup via SQLDBA failed.

Program response: Processing terminated.

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

BR307I Shutting down the database instance %s...

Explanation: The database instance is being shut down by BRBACKUP via SQLDBA.

Program response: None.

User action: None.