Implementing Data Guard - Expert Consolidation in Oracle Database 12c - page 340

Note that the listener.ora configuration file needs to be modified once more when implementing the Data Guard
broker configuration. Make a corresponding similar change on server2's listener.ora file and reload both listeners
before continuing. The duplicate ... from active database command will restart the auxiliary instance a number of
times; without static listener registration this will certainly fail.
With all the supporting directories and other infrastructure in place you can now start the RMAN duplicate
command. Since the example assumes an identical directory structure the following RMAN commands can be used:
[oracle@server1 ~]$ . oraenv
ORACLE_SID = [CDBFSDCA] ?
The Oracle base remains unchanged with value /u01/app/oracle
[oracle@server1 ~]$ rman target sys@cdbfsdca auxiliary sys@cdbfsdcb
Recovery Manager: Release 12.1.0.1.0 - Production on Sun Sep 15 19:48:19 2013
Copyright (c) 1982, 2013, Oracle and/or its affiliates. All rights reserved.
target database Password:
connected to target database: CDBFSDCA (DBID=2052895639)
auxiliary database Password:
connected to auxiliary database (not started)
RMAN> startup clone nomount
[...]
RMAN> run {
allocate channel c1 device type disk;
allocate channel c2 device type disk;
allocate auxiliary channel a1 device type disk;
allocate auxiliary channel a2 device type disk;
duplicate target database for standby from active database;
}
RMAN> 2> 3> 4> 5> 6> 7>
allocated channel: c1
channel c1: SID=133 device type=DISK
[...]
input datafile copy RECID=10 STAMP=826229614 file name=/u01/oradata/CDBFSDCB/PDB1/sysaux01.dbf
datafile 10 switched to datafile copy
input datafile copy RECID=11 STAMP=826229615 file name=/u01/oradata/CDBFSDCB/PDB1/PDB1_users01.dbf
Finished Duplicate Db at 15.09.2013 20:13:37
released channel: c1
released channel: c2
released channel: a1
released channel: a2
RMAN>
Recovery Manager complete.
Don't forget to add standby redo logs on all databases in the configuration! You can query their location and size
from the v$log and v$logfile views on the primary database. Please ensure that you create standby redo logs on
all the databases in the Data Guard configuration. In the example, the following standby redo logs were created. The
primary database used three online redo log groups, each with a size matching the online redo logs (they would be
larger in a production environment).