Databases Reference
In-Depth Information
9.
Start up the database in MOUNT mode.
10.
Make the control file aware of the location of the RMAN backups.
11.
Rename and restore the data files to reflect new directory locations.
12.
Recover the database.
13.
Set the new location for the online redo logs.
14.
Open the database.
15.
Add a tempfile.
16.
Rename the database (optional).
Each of the prior steps is covered in detail in the next several subsections. Steps 1 and 2 occur on the source
database server. All remaining steps are performed on the destination server. For this example, the source database is
named o12c, and the destination database will be named DEVDB.
In this example, the originating server and destination server have different mount point names. On the source
database, the location of the data files and control files are here:
/u01/dbfile/o12c
On the destination database, the data files and control files will be renamed and restored to this directory:
/ora01/dbfile/DEVDB
The destination database online redo logs will be placed in this directory:
/ora01/oraredo/DEVDB
The destination database archive redo log file location will be set as follows:
/ora01/arc/DEVDB
Keep in mind these are the directories used on servers in our test environment. You'll have to adjust these
directory names to reflect the directory structures on your database servers.
Step 1: Create an RMAN Backup on the Originating Database
When backing up a database, make sure you have the autobackup control file feature turned on. Also include the
archive redo logs as part of the backup, like so:
RMAN> backup database plus archivelog;
You can verify the names and locations of the backup pieces via the
list backup
command. For example, this is
what the backup pieces look like for the source database:
1nnht9ot_1_1
1onht9ov_1_1
1pnht9r1_1_1
c-3414586809-20120805-10
