NetBackup™ for Oracle Administrator's Guide
- Introduction
- NetBackup for Oracle QuickStart
- Installing NetBackup for Oracle
- About linking Oracle RMAN with NetBackup for UNIX
- Configuring RBAC for the Oracle administrator
- Managing Oracle instances and databases
- Managing Oracle credentials
- Configuring Oracle policies
- Preparing for NetBackup for Oracle configuration
- About Oracle Intelligent Policies (OIP)
- About script-based Oracle policies
- Managing Oracle RAC
- Performing backups and restores of Oracle
- About NetBackup for Oracle backups
- Managing expired backup images
- About NetBackup for Oracle restores
- Using NetBackup for Oracle in a Windows Server Failover Cluster (WSFC)
- Oracle cloning
- NetBackup Copilot for Oracle
- Configuring an OIP using universal shares (Oracle Copilot)
- Oracle Copilot with instant access
- Prerequisites when you configure an instant access Oracle database
- 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 configuring NetBackup for Oracle block-level incremental backups on UNIX
- About Snapshot Client effects
- About Oracle support for Replication Director
- NetBackup Dedupe Direct for Oracle
- Using NetBackup Dedupe Direct for Oracle plug-in
- Other Oracle configuration
- Troubleshooting
- Troubleshooting RMAN backup or restore errors
- Appendix A. Deduplication best practices
- Appendix B. Snapshot Client support of SFRAC
- Appendix C. 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 D. XML Archiver
- NetBackup for Oracle XML export and XML import
- About XML export shell scripts
- Performing an XML export archive
- Restoring an XML export archive
- Troubleshooting XML export or XML import errors
- Appendix E. Register authorized locations
Troubleshooting NetBackup in an SFRAC environment
The following describes some common errors and how to troubleshoot them:
Problem: The backup failed with error code 6 displayed in the GUI. The
rman_script.out
file shows the following error:RMAN-06403: could not obtain a fully authorized session ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist SVR4 Error: 2: No such file or directory
Resolution: Check the ORACLE_HOME and ORACLE_SID values. ORACLE_HOME should not have an extra '/' at the end.
Problem: The backup failed with error code 239. The dbclient logs show the following log statement:
serverResponse: ERR - server exited with status 239: the specified client does not exist in the specified policy 01:02:23.844 [4000] <16> CreateNewImage: ERR - serverResponse() fail
Resolution: The client name mentioned in the policy and in the
bp.conf
file at the client are different.Problem: The backup failed with error 156. The
bpfis
logs show the following error.CVxFSPlugin::vxFreezeAll : ioctl VX_FREEZE_ALL failed with errno : 16 CVxFSPlugin::quiesce - Could not quiesce as VX_FREEZE_ALL failed and VX_FREEZE is not allowed
Resolution: Add the following lines to the
/usr/openv/lib/vxfi/configfiles/vxfsfi.conf
file:file:[QUIESCENCE_INFO] "QUIESCENCE_SERIAL_QUIESCENCE"=dword:00000001
Problem: The rollback failed with the following error displayed in the GUI:
Failed to process backup file <bk_113_1_728619266>
The dbclient logs show the following error:
xbsa_ProcessError: INF - leaving xbsa_QueryObject: ERR - VxBSAQueryObject: Failed with error: Server Status: client is not validated to use the server xbsa_QueryObject: INF - leaving (3) int_FindBackupImage: INF - leaving int_AddToFileList: ERR - Failed to process backup file <bk_113_1_728619266>
Resolution : Add the following line in the
bp.conf
file on the primary node of the cluster PREFERRED_NETWORK = <virtual_name>
More Information