Databases Reference
In-Depth Information
db_create_file_dest
: specifies the default location for OMF managed data files
•
db_create_online_log_dest_n
: specifies the default location for OMF-based control files and
online redo log files
•
db_recovery_file_dest
: specifies the default location for the fast recovery area
You can't set the
db_file_name_convert
and the
log_file_name_convert
parameters for OMF files. You must
also not set the
control_files
parameter if you want the duplicate database's control files in an OMF format.
•
How It Works
You can include the
db_file_name_convert
command when duplicating a database or specify the parameter in the
initialization parameter file for the auxiliary instance. You can use the
db_file_name_convert
parameter to generate
file names for both data files and tempfiles.
Unlike the
db_file_name_convert
command, you can't specify the
log_file_name_convert
command in
a
duplicate database
clause—you can specify the parameter only in the auxiliary instance's initialization
parameter file.
Creating a Duplicate Database from RMAN Backups
Problem
You want to use RMAN to create a duplicate database from RMAN backups.
Solution
In this sequence of steps to create a duplicate database using RMAN backups, the target database is named
orcl
, and
the duplicate database, also known as the
auxiliary database
i
n RMAN parlance, is named
orcl1
. Here are the steps to
duplicate a database to the same server.
1.
Back up the target database as follows:
RMAN> connect target /
RMAN> backup database plus archivelog;
You'll use these backups as the source for the database duplication later. Of course, if you already have made
backups of the source database, you can skip this step.
2.
Use a dedicated listener configuration for RMAN by making the following additions to
your listener.ora file:
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = orcl1)
(ORACLE_HOME = /u01/app/oracle/product/12.01.1)
(SID_NAME =orcl1)
)
)
