Integrating SAP R/3 and Data Protector

Troubleshooting

If you do not use the Recovery Catalog:

Export <ORACLE_HOME> as described on page 225 and start Recovery Manager:

bin/rman target <Target_Database_Login> nocatalog cmd_file=rman_script

An example of the rman_script is listed 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’ release channel ‘dev0’;}

If one of the above procedures fails, refer to the Oracle documentation to learn how to execute backup and restore directly to disk using the Recovery Manager.

Prerequisites on the SAP R/3 Side of the Integration

The following verification steps must be performed in order to verify that SAP R/3 is installed as required for the integration to work. These steps do not include Data Protector components.

1.Verify backup directly to disk as follows: brbackup -d disk -u<user>/<password>

If this fails, check the error messages and resolve possible problems before you continue.

2.Verify restore directly to disk as follows: brrestore -d disk -u<user>/<password>

228

Chapter 2