Databases Reference
In-Depth Information
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "ORCL1" RESETLOGS ARCHIVELOG
...
contents of Memory Script:
{
set newname for tempfile 1 to
"/u05/app/oracle/oradata/orcl1/temp01.dbf";
switch clone tempfile all;
switch clone datafile all;
}
executing Memory Script
datafile 2 switched to datafile copy
input datafile copy RECID=7 STAMP=797777727 file
name=/u05/app/oracle/oradata/orcl1/example01.dbf
...
sql statement: alter tablespace USERS online
Finished Duplicate Db at 27-NOV-12
RMAN>
How It Works
Make sure you follow these guidelines for network-enabled database duplication:
•
Both the source and destination databases must be known to Oracle Net.
•
The source database can be mounted or open.
•
If the source database is mounted, you must have shut it down cleanly prior to starting it up in
mount mode.
•
If the source database is open, it must be running in archivelog mode.
•
You can continue to use the source database normally while the database duplication is going
on, but be aware that there's an overhead cost of CPU and network bandwidth consumption
for sending the data.
You start the active database duplication process by using the
from active database
clause of the RMAN
duplicate
command. The inter-instance network connection is used to copy the source database files to the specified
destination on the auxiliary instance. Since we didn't specify backup sets explicitly in the
duplicate database
command, RMAN copies the source data files over to the destiantion server as RMAN image copies. At the end of the
data file copying process, RMAN uses a “memory script” to complete the recovery before opening the new duplicate
database. RMAN decides the end time for the duplication based on when it completes the copying of the online
data files.
You must use a password file during active database duplication, unlike in the case of backup-based
duplication, where a password file isn't necessary. The password file makes it possible to connect to the auxiliary
instance with the same SYSDBA password as the source database. You must use the same SYSDBA password
for both the source and the auxiliary database. Alternatively, you can specify the
password file
option within
the
duplicate database
command. When you do this, RMAN copies the source database password file to the
destination server.
