Database Reference
In-Depth Information
e xeRCiSe 7.1
(continued)
Recovery Manager: Release 12.1.0.1.0 -
Production on Sat Jan 4 20:01:34 2014
Copyright (c) 1982, 2013, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1194923408)
connected to auxiliary database: NEWORCL (not mounted)
12.
You are now ready to start the database duplication. Issue the
DUPLICATE DATABASE
command, as shown here:
duplicate target database to neworcl nofilenamecheck
spfile set control_files=
'c:\oracle\oradata\neworcl\control01.ctl',
'c:\oracle\oradata\neworcl\control02.ctl'
set db_file_name_convert 'c:\oracle\oradata\orcl',
'c:\oracle\oradata\neworcl'
set log_file_name_convert 'c:\oracle\oradata\orcl',
'c:\oracle\oradata\neworcl';
This command does the following:
It starts the duplication process.
■
The
SPFILE
parameter causes the target database spfile to be copied to the dupli-
cate database. The duplicate database will use this spfile
■
The
SET
commands (
SET CONTROL FILES
,
SET DB_FILE_NAME_CONVERT
, and
SET
LOG_FILE_NAME_CONVERT
) modify or add parameters to the spfile being copied to
the duplicate database.
■
This
DUPLICATE
command will result in a great deal of output, which we have decided
not to include here because it seems a great waste of a perfectly good tree. Here is
the output that you hopefully will see at the end of the database duplication:
database opened
Finished Duplicate Db at 04-OCT-13
13.
Connect to the duplicated database to verify that it is open:
C:\oracle\product\12.1.0\db_1\database>set oracle_sid=neworcl
C:\oracle\product\12.1.0\db_1\database>sqlplus sys/Robert as sysdba
SQL*Plus: Release 12.1.0.1.0 Production on Sat Jan 4 20:05:34 2014
Copyright (c) 1982, 2013, Oracle. All rights reserved.
Connected to:
Search WWH ::
Custom Search