重建 DGMGRL Dataguard Broker Configuration

Step By Step How to Recreate Dataguard Broker Configuration (Doc ID 808783.1)

​编辑To Bottom

---

In this Document Goal Solution References APPLIES TO: Oracle Database Cloud Schema Service - Version N/A and later Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later Oracle Database Exadata Express Cloud Service - Version N/A and later Oracle Cloud Infrastructure - Database Service - Version N/A and later Oracle Database Backup Service - Version N/A and later Information in this document applies to any platform. *** Reviewed for Relevance 16-Jul-2015 ***   GOAL Step By Step How to Recreate Dataguard Broker Configuration on Windows and Unix. Parameters used dg_broker_start dg_broker_config_file1 dg_broker_config_file2 SOLUTION Step 1. Stop broker in both of primary and standby databases (in all instances in case of RAC): SQL>ALTER SYSTEM SET DG_BROKER_START=FALSE; Step 2. Drop old broker configuration files from both primary and standby: Check the location of files using : "show parameter dg_broker_config_file" By default the broker configuration files will be in "$ORACLE_HOME/dbs" in Unix and "$ORACLE_HOME/database" in Windows. SQL> show parameter dg_broker_config_file NAME                   TYPE   VALUE ---------------------- ------ ---------------------------------------- dg_broker_config_file1 string \<PATH>\<FILE_NAME>.dat dg_broker_config_file2 string \<PATH>\<FILE_NAME>.dat Drop the files using ASMCMD if files are on ASM: ASMCMD> cd /<PATH>/ ASMCMD> rm <FILE_NAME>.dat ASMCMD> rm <FILE_NAME>.dat Drop the files using : Unix $cd $ORACLE_HOME/dbs $ rm <FILE_NAME>.dat $ rm <FILE_NAME>.dat Windows c:\>cd $ORACLE_HOME/database <PATH>> del <FILE_NAME>.dat <PATH>> del <FILE_NAME>.dat Step 3. Start broker in both of primary and standby (in all instances in case of RAC): SQL>ALTER SYSTEM SET DG_BROKER_START=TRUE; Step 4. Connect to DGMGRL on primary: (from instance one in case of RAC)  $dgmgrl DGMGRL for Linux: Version 10.2.0.3.0 - Production Copyright (c) 2000, 2005, Oracle. All rights reserved. Welcome to DGMGRL, type "help" for information. DGMGRL> CONNECT sys/<password>; Connected. Step 5. Create configuration on primary: DGMGRL> CREATE CONFIGURATION '<CONFIGURATION_NAME>' AS PRIMARY DATABASE IS '<PRIMARY_DATABASE_NAME>' CONNECT IDENTIFIER IS <CONNECT_IDENTIFIER>; Configuration "<CONFIGURATION_NAME>" created with primary database "<PRIMARY_DATABASE_NAME>" Step 6. Add standby in the configuration: DGMGRL> ADD DATABASE '<STANDBY_DATABASE_NAME>' AS CONNECT IDENTIFIER IS <CONNECT_IDENTIFIER> MAINTAINED AS PHYSICAL; Database "<STANDBY DATABASE NAME>" added Step 7. Enable Configuration: DGMGRL> ENABLE CONFIGURATION; Enabled. Use the SHOW command to verify that the configuration and its databases were successfully enabled and brought online: DGMGRL> SHOW CONFIGURATION; Configuration Name: <CONFIGURATION_NAME>  Enabled: YES Protection Mode: MaxPerformance Fast-Start Failover: DISABLED Databases: <PRIMARY> - Primary database <STANDBY> - Physical standby database Current status for "<CONFIGURATION_NAME>" SUCCESS Note : For 12c DB Redo log shipping should Not be configured at the Primary and Standby while configuring Broker so you need to set log_archive_dest_n to Null at Primary and Standby. Else will get the below error while Adding the DB in Broker Error: ORA-16698: LOG_ARCHIVE_DEST_n parameter set for object to be added" Refer the below Doc for the steps to resolve ORA-16698 Create Configuration Failing with ORA-16698 (Doc ID 1582179.1)