I have taken for granted to create Data Guard Configuration the same way most of the time that I don’t know what goes wrong when done differently.
oracle@racnode-dc1-1:hawk1:/home/oracle $ sqlplus / as sysdba SQL*Plus: Release 12.1.0.2.0 Production on Mon Feb 19 23:41:49 2018 Copyright (c) 1982, 2014, Oracle. All rights reserved. Connected to: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP, Advanced Analytics and Real Application Testing options 23:41:49 SYS @ hawk1:>show parameter db%name NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ db_file_name_convert string db_name string hawk db_unique_name string hawk pdb_file_name_convert string 23:42:04 SYS @ hawk1:>alter system set dg_broker_start=true sid='*' scope=memory; System altered. 23:42:40 SYS @ hawk1:> +++ CREATE CONFIGURATION USING UPPER CASE WITHOUT QUOTES oracle@racnode-dc1-1:hawk1:/home/oracle $ dgmgrl / DGMGRL for Linux: Version 12.1.0.2.0 - 64bit Production Copyright (c) 2000, 2013, Oracle. All rights reserved. Welcome to DGMGRL, type "help" for information. Connected as SYSDG. --- NO QUOTES USE AND ALL UPPERCASE - EASIEST METHOD --- Broker convert database to match that of db_unique_name DGMGRL> CREATE CONFIGURATION DG_CONFIG AS PRIMARY DATABASE IS HAWK CONNECT IDENTIFIER IS HAWK; Configuration "dg_config" created with primary database "hawk" DGMGRL> show configuration Configuration - dg_config Protection Mode: MaxPerformance Members: hawk - Primary database Fast-Start Failover: DISABLED Configuration Status: DISABLED DGMGRL> show database hawk Database - hawk Role: PRIMARY Intended State: OFFLINE Instance(s): hawk1 hawk2 Database Status: DISABLED DGMGRL> remove configuration Removed configuration --- CONFIGURATION IS UPPERCASE --- Does it look better in uppercase? DGMGRL> CREATE CONFIGURATION 'DG_CONFIG' AS PRIMARY DATABASE IS 'hawk' CONNECT IDENTIFIER IS HAWK; Configuration "DG_CONFIG" created with primary database "hawk" DGMGRL> show configuration Configuration - DG_CONFIG Protection Mode: MaxPerformance Members: hawk - Primary database Fast-Start Failover: DISABLED Configuration Status: DISABLED DGMGRL> show database hawk Database - hawk Role: PRIMARY Intended State: OFFLINE Instance(s): hawk1 hawk2 Database Status: DISABLED DGMGRL> remove configuration Removed configuration +++ ISSUES OCCUR WHEN USING UPPERCASE WITH QUOTES FOR DATABASE +++ Not sure if this will work as I have not tested end to end. Why create it this way to begin with? DGMGRL> CREATE CONFIGURATION 'DG_CONFIG' AS PRIMARY DATABASE IS 'HAWK' CONNECT IDENTIFIER IS HAWK; Configuration "DG_CONFIG" created with primary database "HAWK" DGMGRL> show configuration Configuration - DG_CONFIG Protection Mode: MaxPerformance Members: HAWK - Primary database Fast-Start Failover: DISABLED Configuration Status: DISABLED DGMGRL> show database hawk Object "hawk" was not found DGMGRL> show database HAWK Object "hawk" was not found DGMGRL> show database 'HAWK'; Database - HAWK Role: PRIMARY Intended State: OFFLINE Instance(s): hawk1 hawk2 Database Status: DISABLED DGMGRL>
REFERENCE:
CREATE CONFIGURATION configuration_name AS PRIMARY DATABASE IS database-name CONNECT IDENTIFIER IS connect-identifier;
database-name
The name that will be used by the broker to refer to the primary database.
It must match (case-insensitive) the value of the primary database DB_UNIQUE_NAME initialization parameter.