Veritas NetBackup™ for Oracle Administrator's Guide

To check the logs

1. Check the bporaexp or bporaimp log.

   If the LOG parameter is specified in the bporaexp or bporaimp command's parfile, the commands write logs to the file that is specified as the argument to the LOG parameter. The commands write log information to the screen if LOG is not specified.

   For example, incorrect installation or configuration causes the following common problems:

   • The ORACLE_HOME environment variable was not set.

   • The bporaexp or bporaimp program was unable to connect to the target database.

   When bporaexp and bporaimp are being used and the backup images are being written to an operating system directory, these logs are the only source of error logging and tracking.

2. Check the NetBackup logs.

   On Windows, the first NetBackup log to check is install_path\NetBackup\logs\bporaexp\log.mmddyy or install_path\NetBackup\logs\bporaimp\log.mmddyy.

   On UNIX, the first NetBackup log to check is /usr/openv/netbackup/logs/bporaexp/log.mmddyy or /usr/openv/netbackup/logs/bporaimp/log.mmddyy.

   Examine these logs for messages that show how to determine the source of an error.

   These logs are written by the NetBackup client and contain the following:

   • Requests from bporaexp and bporaimp

   • Activities between bporaexp and bporaimp and NetBackup processes

   If the logs do not contain any messages, the following conditions could be present:

   • bporaexp or bporaimp terminated before requesting service from NetBackup.

   • bphdb (if started by the scheduler or graphical user interface) did not start the template or shell script successfully. Check the bphdb logs for stderr and stdout files.

   Try to run the XML export or XML import template or script file from the command line to determine the problem.

   On UNIX, the error is usually due to a file permission problem for bphdb itself or for the export or import script file.

   Ensure that the full XML export or import script file name is entered correctly in the Backup Selections list of the Oracle policy configuration, or for templates, that the name is correct.

   On UNIX, logs are not created in this directory if the permissions are not set for the Oracle user to write to the directory. The full permissions setting, chmod 777, is best.