User`s guide

Recovery Manager
Backing Up and Recovering a Database 6-3
While Oracle database is running, the names of all files which it comprises can be
determined by querying the table
V$DATAFILE . Enter the following command
when the SQL prompt is displayed:
SQL> select file#,name FROM V$DATAFILE;
The following is an example of the result that is displayed:
FILE#NAME
-------------------------------
1 :pvs:$dbauserid.sid.DBS.DATABASE1.DBF
2 :pvs:$dbauserid.sid.DBS.DATABASE2.DBF
2 ROWS SELECTED.
You can determine the name of the log files in a similar way:
SQL> SELECT GROUP#,MEMBER FROM V$LOGFILE;
The following is an example of the result that is displayed:
GROUP#MEMBER
-------------------------------
1 :pvs:$dbauserid.sid.DBS.LOG1.DBF
2 :pvs:$dbauserid.sid.DBS.LOG2.DBF
2 ROWS SELECTED.
2. Under the DBA user ID, ensure that the ORASID environment variable identifies the
Oracle Database, which is to be restored.
3. Use the SQL*Plus STARTUP command to start the Oracle database.
6.3 Recovery Manager
On BS2000/OSD, Recovery Manager does not support tapes. Disks are the only
backup media.
As a workaround, you could use the Recovery Manager output as a first level storage
to be 'migrated' by BS2000 subsystem HSMS (Hierarchical Storage Management
System) to tapes. However, it is the administrator's responsibility to care for
cooperation of the two systems.
Recovery Manager must use an Oracle Net Services connection. For this purpose you
can:
■ use a Bequeath Server (refer to Chapter 9, "Oracle Net Services")
■ create a password file, start a listener, and connect through Oracle Net Services
The following is an example of a Recovery Manager command:
/START-PROG $ORAC1120.RMAN
*target "dba1/dba1@i1" catalog "dba2/dba2@i2" cmdfile "b.dat" log "b.log"