Databases Reference
In-Depth Information
5. Reload the listener:
$ lsnrctl reload
6. Next, create an
init.ora
file for the cloned database. In case the same
database file paths cannot be used on the auxiliary host, either because it
is the same source host or because those paths are not reproducible on the
target, then proper values for
DB_FILE_NAME_CONVERT
and
LOG_FILE_NAME_
CONVERT
are required.
DB_NAME=CLONEDB
CONTROL_FILES=(/u02/oradata/CLONEDB/control01.ctl,
/u02/oradata/CLONEDB/control02.ctl,
/u02/oradata/CLONEDB/control03.ctl)
# Convert file names to allow for different directory structure.
DB_FILE_NAME_CONVERT=(/u02/oradata/SRCDB/,/u02/oradata/CLONEDB/)
LOG_FILE_NAME_CONVERT=(/u01/oradata/SRCDB/,/u01/oradata/CLONEDB/)
# block_size and compatible parameters must match those of the
source database
DB_BLOCK_SIZE=8192
COMPATIBLE=10.2.0.1.0
7. Connect to the cloned instance:
ORACLE_SID=CLONEDB; export ORACLE_SID
sqlplus /nolog
conn / as sysdba
8. Create an
SPFILE
based on the
init.ora
:
CREATE SPFILE FROM PFILE='/u01/app/oracle/admin/CLONEDB/pfile/
init.ora';
9. Start the database in
NOMOUNT
mode:
STARTUP FORCE NOMOUNT;
10. Connect to the
TARGET
,
CATALOG
, and
AUXILIARY
databases. In this code
snippet, the clone database process is performed using the catalog database,
but it is not required, it can be performed with or without a recovery catalog.
At the auxiliary site, using RMAN, three connections are open, one for the
Source
Database
(
SOURCEDB
), another for the
Catalog
database (
RCAT
),
and one more for the
cloned database
(
CLONEDB
):
ORACLE_SID=CLONEDB; export ORACLE_SID
rman TARGET sys/password@SRCDB CATALOG rman/rman@RCAT AUXILIARY /
Search WWH ::
Custom Search