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
Troubleshooting the UNIX browser interface and wizards
If you do not see the Oracle database instance in your Backup, Archive, and Restore interface, verify the following:
A NetBackup for Oracle license is installed on the master server.
For browsing in the restore window, the policy type must be set to Oracle.
Perform the following actions to change the client policy type:
On the Actions menu, select .
In thedrop-down list, select .
On Windows, to change the client policy type:
On the File menu, select .
On the Specify NetBackup Machines dialog, click the Clients/Policy Type tab.
In thedrop-down list, select .
On UNIX, the oratab file is in the correct location (/etc/oratab or /var/opt/oracle/oratab) and contains all of the available Oracle SIDs. Although Oracle allows the use of wild cards in the
oratabfile, the NetBackup BAR GUI requires that each SID be specified.
If you have trouble connecting to the Oracle database, verify the following:
Make sure that the database is in a mount state or an open state.
Make sure that your login ID and password have Oracle SYSDBA or SYSBACKUP privileges. Initially, NetBackup for Oracle attempts OS Authentication to log on. If that fails, you are prompted for a user name, password, and an optional Transparent Network Substrate (TNS) alias. The user name and password you enter must have SYSDBA or SYSBACKUP privileges.
In a clustered environment, failure to connect to the database can mean a problem with the network configuration. The browser must connect locally. However, in some environments, all connections are considered to be remote connections, even a connection to a local database. This behavior is true for example in an Oracle Real Application Clusters (RAC) environment. In such cases, you must make the connection using a TNS alias.
In a Linux environment, Oracle backups and restores fail if the Linux logon is not the Oracle user. In such cases, Oracle generates the following message:
INF - ORA-19554: error allocating device, device type: SBT_TAPE, device name: INF - ORA-27211: Failed to load Media Management Library
If you want to start an Oracle job as someone other than an Oracle user, augment the default shared library search path. Use the Linux ldconfig(8) command to add $ORACLE_HOME/lib to the search path.