•
On the application system, verify backup and restore directly to disk using an
RMAN channel type disk:
If you use the recovery catalog:
1.
Export or set the ORACLE_HOME variable as described in
2.
Start RMAN from the bin directory in the ORACLE_HOME directory:
rman target Target_Database_Login catalog
Recovery_Catalog_Login
If you do not use the recovery catalog:
1.
Export or set the ORACLE_HOME variable as described in
2.
Start RMAN from the bin directory in the ORACLE_HOME directory:
rman target Target_Database_Login nocatalog
An example of the RMAN backup script is presented below:
run {
allocate channel 'dev0' type disk;
backup tablespace tablespace_name format
'ORACLE_HOME/tmp/datafile_name';
}
After a successful backup, try to restore the backed up tablespace by running the
following restore script:
run {
allocate channel 'dev0' type disk;
sql 'alter tablespace tablespace_name offline immediate';
restore tablespace tablespace_name;
recover tablespace tablespace_name;
sql 'alter tablespace tablespace_name online';
}
If this fails, see the Oracle documentation for details on how to execute a backup
and restore directly to disk using RMAN.
Additionally, if your configuration or backup failed:
•
Verify that the Data Protector software has been installed properly.
See the HP Data Protector installation and licensing guide for details.
•
Check if the SYSDBA privilege is granted to the Oracle administrator.
•
If you have special Oracle environment settings, ensure that they are entered in
the Data Protector Oracle configuration files on the Cell Manager. See the
util_cmd man page or the HP Data Protector command line interface reference
150
Data Protector Oracle ZDB integration
Step 1
on page 146.
Step 1
on page 146.