Databases Reference
In-Depth Information
7.
Recover the file:
RMAN> recover datafile 6;
Starting recover at 18-AUG-12
using channel ORA_DISK_1
starting media recovery
media recovery complete, elapsed time: 00:00:00
Finished recover at 18-AUG-12
8.
Make it online:
RMAN> alter database datafile 6 online;
Statement processed
9.
Confirm that the copied file, not the older file, is part of the database now:
RMAN> report schema;
Report of database schema for database with db_unique_name IDB1
List of Permanent Datafiles
===========================
File Size(MB) Tablespace RB segs Datafile Name
---- -------- -------------------- ------- ------------------------
1 810 SYSTEM *** +DATA/idb1/datafile/system.282.790482827
2 340 EXAMPLE *** +DATA/idb1/datafile/example.290.790482945
3 970 SYSAUX *** +DATA/idb1/datafile/sysaux.281.790482773
4 125 UNDOTBS1 *** +DATA/idb1/datafile/undotbs1.284.790482893
6 31 USERS *** /u01/oradata/0rniv31f
List of Temporary Files
=======================
File Size(MB) Tablespace Maxsize(MB) Tempfile Name
---- -------- -------------------- ----------- --------------------
1 106 TEMP 32767 +DATA/idb1/tempfile/temp.289.790482937
File 6 is shown as the new location.
How It Works
RMAN's
convert
command works in much the same way as the
backup as copy
command, but with an important
difference. Convert merely copies the file; it does not record the existence of the file in the RMAN repository, as you
saw in the solution section. Therefore, you had to catalog the copied file to ensure its proper recording. The catalog
command looks at the header of the file and from there it knows the type of file: data file, archived log, etc. The catalog
command does not need to be told what type of file it is.
