Backing Up Oracle - Computing at Cornell

We started the database in nomount mode with a startup nomount
We invoked RMAN and performed a report schema to list the file id’s, the
size and the corresponding file names
We increased the space of file system /u03/oradata - the df -k
/u03/oradata lists the amount of free KB in the file system, the output from
the RMAN report schema lists the KB allocated for a single datafile.
We created a RMAN command file including the options set newname for
the datafiles originally located on /u02/oradata/oslo.
In this example:
- shutdown abort and startup nomont are included in the script because
we had to run it several times. This way, it is guaranteed that the status
of the instance (STARTED) is correct.
- set newname is used for the restore and for the switch command.
- restore restores all datafiles; file 4, 5, and 7 are renamed during the
restore.
- alter database mount is required because of the following recover
command.
- switch datafile all renames datafiles 4, 5, and 7 in the control files —
it is working like an alter database oslo rename file ‘xxx’ to ‘yyy’.
- recover database applies redo log records.
- alter database open finally makes the database available.
Chapter 8. Recovering Oracle Databases on UNIX 111