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

*.db_domain=''
*.db_name='CDB1'
*.db_recovery_file_dest='+RECO'
*.db_recovery_file_dest_size=4800m
*.db_unique_name='CDB1DCB'
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=CDB1DCBXDB)'
*.enable_pluggable_database=true
*.open_cursors=300
*.pga_aggregate_target=384m
*.processes=300
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=1152m
*.undo_tablespace='UNDOTBS1'
As it was the case earlier, you need to ensure that the directories referenced in the parameter file exist on disk.
You should also update the tnsnames.ora file to include the new databases, please refer to the above section for an
example.
With the infrastructure in place it is time to start the auxiliary and initiate the duplication. Luckily with Oracle
Managed Files you do not need to worry about file name conversions! Consider this example where the primary
database CDB1DCA is duplicated to the standby CDB1DCB:
[oracle@server1 dbs]$ rman target sys/xxx@cdb1dca auxiliary sys/xxx@cdb1dcb
Recovery Manager: Release 12.1.0.1.0 - Production on Sun Sep 15 21:43:19 2013
Copyright (c) 1982, 2013, Oracle and/or its affiliates. All rights reserved.
connected to target database: CDB1 (DBID=799950173)
connected to auxiliary database: CDB1 (not mounted)
RMAN> duplicate target database for standby from active database;
Starting Duplicate Db at 15-SEP-13
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=123 device type=DISK
allocated channel: ORA_AUX_DISK_2
channel ORA_AUX_DISK_2: SID=242 device type=DISK
allocated channel: ORA_AUX_DISK_3
channel ORA_AUX_DISK_3: SID=362 device type=DISK
contents of Memory Script:
{
[...]
Finished Duplicate Db at 15-SEP-13