Databases Reference
In-Depth Information
SQL> connect / as sysdba
Connected to an idle instance.
SQL> startup nomount pfile=$ORACLE_HOME/dbs/initorcl1.ora
ORACLE instance started.
Total System Global Area 238034944 bytes
Fixed Size 2258944 bytes
Variable Size 180357120 bytes
Database Buffers 50331648 bytes
Redo Buffers 5087232 bytes
SQL>
SQL> exit
The
startup
command we executed starts the auxiliary instance and mounts the new control file. Once you
create a new Oracle instance as shown here, the listener utility will automatically register the new database.
7.
Start RMAN, and connect to the target database, after making sure you first set the
ORACLE_SID environmental variable to the source database,
orcl
. Note that the target
database can be mounted or open.
[oracle@virtual1 dbs]$ rman target sys/Ninamma11@orcl auxiliary /
Recovery Manager: Release 12.1.0.0.2 - Beta on Tue Nov 16 14:55:37 2012
Copyright (c) 1982, 2012, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1316762630)
connected to auxiliary database: ORCL1 (not mounted)
RMAN>
This has been an example showing how to perform a backup-based duplication with a target connection.
We therefore must connect to the source database as the target. We must also connect to the auxiliary instance as
auxiliary, but a recovery catalog is purely optional, and we aren't using one here.
â–
if you're duplicating a database to the same host, as is the case in this example, you don't have to use a
password file. You can simply choose to use operating system authentication to connect to the auxiliary instance. if you
must access a database from a different host, on the other hand, you must use a password file for both the target and
auxiliary instances, and they must use the same sysdba password. You must use an oracle net service name to connect
to the auxiliary instance.
Note
Issue the
duplicate target database
command to start the database duplication (since
the Oracle 11.2 release, the word
target
is optional—that is, you can just issue the following
command instead:
duplicate database to orcl1
).
8.
