Database Reference
In-Depth Information
14.
Open the database.
15.
Add the temp file.
16.
Rename the database (optional).
Each of the prior steps is covered in detail in the next several sections. 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
.
Furthermore, the originating server and destination server have different mount point names. On the source
database 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 that these are the directories used on servers in my 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:
rman1_bonvb2js_1_1.bk
rman1_bqnvb2k5_1_1.bk
rman1_bsnvb2p3_1_1.bk
rman_ctl_c-3423216220-20130113-06.bk
In the prior output the file with the
c-3423216220
string in the name is the backup piece that contains the control
file. You'll have to inspect the output of your
LIST BACKUP
command to determine which backup piece contains the
control file. You'll need to reference that backup piece in step 8.
