Veritas NetBackup™ for Oracle Administrator's Guide

The status codes and their meanings are as follows:

• Status Code 9. An extension package is needed but was not installed.

  The client does not have the NetBackup binaries required to do BLI backups. Use update_clients on the server to push out new binaries. Also, use vxlicense -p to verify that the Storage Checkpoint feature [83] and the Veritas Storage Foundation for Oracle [100] are installed.

• Status Code 69. Invalid file list specification.

  Look for a message such as the following in the error log on the server:

  FTL - /oradata is not in a VxFS file system. A block incremental
  backup of it is not possible.

  This indicates that there was an attempt to back up a file system that is not a VxFS file system with the Block level incremental attribute. This error can also occur if the file system is not mounted.

• Status Code 73. bpstart_notify failed.

  When running the notify scripts, the bpstart_notify script exited with a nonzero status code, or the permission bits are set wrong on the bpstart_notify script. The script must have execute permission. If the permission bits are set, check the bpstart_notify_output.ORACLE_SID file in the /usr/openv/netbackup/bin/BLOCK_INCR directory.

• Status Code 74. Client timed out waiting for bpstart_notify to complete.

  Check the BPSTART_TIMEOUT setting on the NetBackup server. The BPSTART_TIMEOUT specified did not allow enough time for the script to complete. The shutdown database operation might be taking too long, or the script might be waiting for other streams to start. Check the bpstart_notify_output.ORACLE_SID file and the post_checkpoint_notify_output.ORACLE_SID file in the /usr/openv/netbackup/bin/BLOCK_INCR directory. Make sure that the policies and schedules are configured with appropriate multiplexing factors and that the required storage units that allow all streams to start at the same time are configured. Check to see if all needed tape drives are working and available. Make sure that the database is not processing transactions so that the instance cannot be shut down immediately (if you are using one of the backup methods where the database is shut down).

  Finally, make sure that the priority on the BLI policies is higher than other policies, so they get access to the tape drives before the other policies.

• Status Code 75. Client timed out waiting for bpend_notify to complete.

  Check the BPEND_TIMEOUT setting on the NetBackup server. The BPEND_TIMEOUT specified did not allow enough time for the script to complete. The restart database operation might be taking too long, or the script might be waiting for other streams to call the bpend_notify script. Check the bpend_notify_output.ORACLE_SID file and the post_checkpoint_notify_output.ORACLE_SID file in the /usr/openv/netbackup/bin/BLOCK_INCR directory. Make sure that the policies and schedules are configured with appropriate multiplexing factors and that the required storage units that can allow all streams to be started at the same time are configured. Verify that all needed tape drives are working and available during backup.

• Status Code 77. Execution of the specified system command returned a nonzero status code.

  Check the post_checkpoint_notify_output.KEYWORD file in the /usr/openv/netbackup/bin/BLOCK_INCR directory for the possible cause. The post_checkpoint_notify script exited with a nonzero status code.

• Status Code 143. Invalid command protocol.

  Check to see if the Block level incremental policy attribute is selected without a keyword specified. Set the Keyword phrase in the policies to the Oracle database instance name ($ORACLE_SID).