• From the application system, verify that the target database and recovery catalog
database are configured to allow remote connections with the system privileges
and to allow backup:
• If you use the recovery catalog database:
Export or set the ORACLE_HOME and DB_NAME variables as described in Step
1 on page 146.
SQL> connect login_to_recovery_catalog_or_target_database
as sysdba;
> exit
ORACLE_HOME/bin/rman target login_to_target database
catalog login_to_Recovery_Catalog
• If you do not use the recovery catalog database:
Export or set the ORACLE_HOME and DB_NAME variables as described in Step
1 on page 146.
ORACLE_HOME/bin/rman target login_to_target_database
nocatalog
See the Oracle documentation for how to set up a password file and
parameters in the initDB_NAME.ora file and how to add system privileges
for a user.
See the section “Recovery Manager Connection Options” in the Oracle Backup
and Recovery Guide for information.
• If you use the recovery catalog database, verify that the target database is
registered in the recovery catalog:
1. Export or set the ORACLE_HOME variable as described in Step 1 on page 146.
2. Start SQL*Plus from the bin directory in the ORACLE_HOME; directory:
sqlplus /nolog
3. Start SQL*Plus and type:
connect Recovery_Catalog_Login;
select * from rc_database;
exit
If this fails, start the configuration using Data Protector on the application system,
or see the Oracle documentation for information on how to register an Oracle
target database in the recovery catalog database.
Zero downtime backup integration guide 149
To Next Page
Loading...
Need help?
General