Veritas NetBackup™ for Oracle Administrator's Guide
- NetBackup for Oracle QuickStart
- Installing NetBackup for Oracle
- About linking Oracle RMAN with NetBackup for UNIX
- Linking Oracle RMAN with NetBackup on UNIX platforms
- Oracle policy configuration
- Preparing for NetBackup for Oracle configuration
- Instance management for an Oracle Intelligent Policy
- About Oracle Intelligent Policies (OIP)
- About script- or template-based Oracle policies
- About adding backup selections to an Oracle policy
- About configuring the run-time environment
- About creating templates and shell scripts
- About creating RMAN scripts manually
- Performing backups and restores of Oracle
- About NetBackup for Oracle backups
- About NetBackup for Oracle restores
- Redirecting a restore to a different client
- Using NetBackup for Oracle in a Microsoft Windows cluster environment
- Guided Recovery
- Troubleshooting Guided Recovery
- NetBackup for Oracle with Snapshot Client
- About NetBackup for Oracle with Snapshot Client
- How NetBackup for Oracle with Snapshot Client works
- About configuring Snapshot Client with NetBackup for Oracle
- Restoring NetBackup for Oracle from a snapshot backup
- About NetBackup for Oracle restores of volumes and file systems using snapshot rollback
- About configuring NetBackup for Oracle block-level incremental backups on UNIX
- About Snapshot Client effects
- About Oracle support for Replication Director
- Troubleshooting RMAN backup or restore errors
- Appendix A. Real Application Clusters
- Appendix B. Best practices for protecting Oracle RAC with NetBackup
- Appendix C. Deduplication best practices
- Appendix D. Snapshot Client support of SFRAC
- Appendix E. Script-based block-level incremental (BLI) backups without RMAN on UNIX and Linux systems
- Verifying installation requirements for BLI backups without RMAN
- Creating NetBackup policies for script-based BLI backup
- Creating notify scripts for BLI backups
- Performing backups and restores
- About troubleshooting backup or restore errors
- Appendix F. XML Archiver
- NetBackup for Oracle XML export and XML import
- About XML export templates and shell scripts
- Performing an XML export archive
- Restoring an XML export archive
- About redirecting a restore of an XML export archive to a different client
- Troubleshooting XML export or XML import errors
- Appendix G. Register authorized locations
Checking the logs to determine the source of an error
This topic describes how to check the logs to determine the source of an error.
To check the logs
- 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.
- 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.
For more information about debug logs and reports, refer to the NetBackup Administrator's Guide, Volume I.