Integrating Oracle and Data Protector

Backing Up an Oracle Database

b.Execute $rman target <target_connect_string> catalog <catalog_connect_string>.

Oracle 8i:

Use rcvcat instead of catalog in the above syntax.

If you do not use the recovery catalog:

On Windows: <ORACLE_HOME>\bin\rman target <Target_Database_Login> nocatalog

On UNIX: <ORACLE_HOME>/bin/rman target <Target_Database_Login> nocatalog

On OpenVMS:

a.Run ORAUSER.COM using $@OMNI$ROOT:[LOG]LOGIN.COM.

b.Execute $rman target <target_connect_string> nocatalog.

Target Database The format of the target database login is

Login<user_name>/<password>@<service>,

where:

<user_name> is the name by which a user is known to Oracle Server and to other users. Every user name is associated with a password and both have to be entered to connect to an Oracle target database. This user must have been granted Oracle SYSDBA or SYSOPER rights.

<password> must be the same as the password specified in the Oracle password file (orapwd), which is used for authentication of users performing database administration.

<service> is the name used to identify an SQL*Net server process for the target database.

Recovery Catalog The format of the Recovery Catalog Database login is

Login<user_name>/<password>@<service>,

where the description of the user name and password is the same as for the login information to the target database. Note that the Oracle user specified here has to be the owner of the Oracle Recovery Catalog.

<service> is the name used to identify SQL*Net server process for the Recovery Catalog Database.

Chapter 1

63