Database Reference
In-Depth Information
Now, connect to RMAN, and run the prior script to restore the data files to the new locations:
$ rman target /
RMAN> @newname.sql
Here is a snippet of the output:
datafile 1 switched to datafile copy
input datafile copy RECID=5 STAMP=790357985 file name=/ora01/dbfile/DEVDB/system01.dbf
All the data files have been restored to the new database server. You can use the RMAN
REPORT SCHEMA
command
to verify that the files have been restored and are in the correct locations:
RMAN> report schema;
Here is some sample output:
RMAN-06139: WARNING: control file is not current for REPORT SCHEMA
Report of database schema for database with db_unique_name O12C
List of Permanent Datafiles
===========================
File Size(MB) Tablespace RB segs Datafile Name
---- -------- -------------------- ------- ------------------------
1 500 SYSTEM *** /ora01/dbfile/DEVDB/system01.dbf
2 500 SYSAUX *** /ora01/dbfile/DEVDB/sysaux01.dbf
3 800 UNDOTBS1 *** /ora01/dbfile/DEVDB/undotbs01.dbf
4 50 USERS *** /ora01/dbfile/DEVDB/users01.dbf
List of Temporary Files
=======================
File Size(MB) Tablespace Maxsize(MB) Tempfile Name
---- -------- -------------------- ----------- --------------------
1 500 TEMP 500 /u01/dbfile/O12C/temp01.dbf
From the prior output you can see that the database name and temporary tablespace data file still don't reflect
the destination database (
DEVDB
). These will be modified in subsequent steps.
Step 12. Recover the Database
Next, you need to apply any archive redo files that were generated during the backup. These should be included in
the backup because the
ARCHIVELOG ALL
clause was used to take the backup. Initiate the application of redo via the
RECOVER DATABASE
command:
RMAN> recover database;
RMAN will restore and apply as many archive redo logs as it has in the backup pieces and then may throw an
error when it reaches an archive redo log that doesn't exist; for example,
RMAN-06054: media recovery requesting unknown archived log for...
