{"id":46597,"date":"2022-05-26T11:23:17","date_gmt":"2022-05-26T11:23:17","guid":{"rendered":"https:\/\/dbtut.com\/?p=46597"},"modified":"2022-05-26T11:27:23","modified_gmt":"2022-05-26T11:27:23","slug":"removing-database-and-broker-configuration-in-environment","status":"publish","type":"post","link":"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/","title":{"rendered":"Removing Database And Broker Configuration In Environment"},"content":{"rendered":"<p>In today&#8217;s article, I will tell you about Data Guard Broker-Removing Database And Broker Configuration In Environment.<\/p>\n<p>We may want to REMOVE one, several or the entire Broker Configuration in the Broker Environment. The operation steps are as follows.<\/p>\n<p>1. Before REMOVE, we query the Databases in Configuration and Environment separately.<\/p>\n<pre class=\"lang:default decode:true \">DGMGRL&gt; show configuration\r\n\r\nConfiguration - Broker _Configuration\r\n\r\n  Protection Mode: MaxPerformance\r\n  Databases:\r\n    primary - Primary database\r\n    standby - Physical standby database\r\n    logical - Logical standby database\r\n\r\nFast-Start Failover: DISABLED\r\n\r\nConfiguration Status:\r\nSUCCESS\r\n\r\n\r\nDGMGRL&gt; show database primary\r\n\r\nDatabase - primary\r\n\r\n  Role:            PRIMARY\r\n  Intended State:  TRANSPORT-ON\r\n  Instance(s):\r\n    primary1\r\n    primary2\r\n\r\nDatabase Status:\r\nSUCCESS\r\n\r\n\r\nDGMGRL&gt; show database standby\r\n\r\nDatabase - standby\r\n\r\n  Role:            PHYSICAL STANDBY\r\n  Intended State:  APPLY-ON\r\n  Transport Lag:   0 seconds (computed 0 seconds ago)\r\n  Apply Lag:       0 seconds (computed 0 seconds ago)\r\n  Apply Rate:      640.00 KByte\/s\r\n  Real Time Query: ON\r\n  Instance(s):\r\n    primary1 (apply instance)\r\n    primary2\r\n\r\nDatabase Status:\r\nSUCCESS\r\n\r\n\r\nDGMGRL&gt; show database logical\r\n\r\nDatabase - logical\r\n\r\n  Role:            LOGICAL STANDBY\r\n  Intended State:  APPLY-ON\r\n  Transport Lag:   0 seconds (computed 0 seconds ago)\r\n  Apply Lag:       0 seconds (computed 0 seconds ago)\r\n  Apply Rate:      0 Byte\/s\r\n  Instance(s):\r\n    primary1\r\n    primary2 (apply instance)\r\n\r\nDatabase Status:\r\nSUCCESS\r\n<\/pre>\n<p>2. After REMOVE the configuration, we do some checks to find out how the system will work.<\/p>\n<p>We query the status of the DG_BROKER_START parameter.<\/p>\n<pre class=\"lang:default decode:true \">[Primary-1] SQL&gt; show parameter dg_broker_start\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\ndg_broker_start                      boolean     TRUE\r\n<\/pre>\n<p>We question the existence of the DMON process.<\/p>\n<pre class=\"lang:default decode:true \">[oracle@primary1 ~]$ ps -ef | grep ora_dmon | grep -v grep\r\noracle   14329     1  0 Jan14 ?        00:00:06 ora_dmon_primary1\r\n<\/pre>\n<p>We query the existence of the configuration files.<\/p>\n<pre class=\"lang:default decode:true \">ASMCMD&gt; pwd\r\n+data\/primary\/BROKER_CONF_FILE\r\nASMCMD&gt; ls\r\ndr1primary.dat\r\n\r\nASMCMD&gt; pwd\r\n+data\/standby\/BROKER_CONF_FILE\r\nASMCMD&gt; ls\r\ndr1standby.dat\r\n\r\nASMCMD&gt; pwd\r\n+data\/logical\/BROKER_CONF_FILE\r\nASMCMD&gt; ls\r\ndr1logical.dat\r\n\r\nASMCMD&gt; pwd\r\n+fra\/primary\/BROKER_CONF_FILE\r\nASMCMD&gt; ls\r\ndr2primary.dat\r\n\r\nASMCMD&gt; pwd\r\n+fra\/standby\/BROKER_CONF_FILE\r\nASMCMD&gt; ls\r\ndr2standby.dat\r\n\r\nASMCMD&gt; pwd\r\n+fra\/logical\/BROKER_CONF_FILE\r\nASMCMD&gt; ls\r\ndr2logical.dat\r\n<\/pre>\n<p>We are querying the values of the LOG_ARCHIVE_DEST_n parameters.<\/p>\n<pre class=\"lang:default decode:true \">[Primary-1] SQL&gt; column name format a30\r\n[Primary-1] SQL&gt; column value format a94\r\n[Primary-1] SQL&gt; set linesize 9000\r\n[Primary-1] SQL&gt; select name, value from v$parameter where lower(name) like '%log_archive_dest%' and lower(name) not like '%log_archive_dest_state%' and value is not null;\r\n\r\nNAME                           VALUE\r\n------------------------------ ----------------------------------------------------------------------------------------------\r\nlog_archive_dest_1             LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=primary\r\nlog_archive_dest_2             service=\"standby\", LGWR ASYNC  delay=0 optional compression=disable max_failure=0 max_\r\n                               connections=1 reopen=300 db_unique_name=\"standby\" net_timeout=30, valid_for=(all_logfiles,prim\r\n                               ary_role)\r\n\r\nlog_archive_dest_3             service=\"logical\", LGWR ASYNC NOAFFIRM delay=0 optional compression=disable max_failure=0 max_\r\n                               connections=1 reopen=300 db_unique_name=\"logical\" net_timeout=30, valid_for=(all_logfiles,prim\r\n                               ary_role)\r\n<\/pre>\n<pre class=\"lang:default decode:true \">[Physical-1] SQL&gt; set linesize 9000\r\n[Physical-1] SQL&gt; column name format a30\r\n[Physical-1] SQL&gt; column value format a94\r\n[Physical-1] SQL&gt; select name, value from v$parameter where lower(name) like '%log_archive_dest%' and lower(name) not like '%log_archive_dest_state%' and value is not null;\r\n\r\nNAME                           VALUE\r\n------------------------------ ----------------------------------------------------------------------------------------------\r\nlog_archive_dest_1             LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=standby\r\n<\/pre>\n<pre class=\"lang:default decode:true \">[Logical-1] SQL&gt; column name format a30\r\n[Logical-1] SQL&gt; column value format a94\r\n[Logical-1] SQL&gt; set linesize 9000\r\n[Logical-1] SQL&gt; select name, value from v$parameter where lower(name) like '%log_archive_dest%' and lower(name) not like '%log_archive_dest_state%' and value is not null;\r\n\r\nNAME                           VALUE\r\n------------------------------ ----------------------------------------------------------------------------------------------\r\nlog_archive_dest_1             LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=logical\r\n<\/pre>\n<p>We are querying the values of the LOG_ARCHIVE_CONFIG parameters.<\/p>\n<pre class=\"lang:default decode:true \">[Primary-1] SQL&gt; show parameter log_archive_config\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\nlog_archive_config                   string      dg_config=(primary,standby,logical)\r\n<\/pre>\n<pre class=\"lang:default decode:true \">[Physical-1] SQL&gt; show parameter log_archive_config\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\nlog_archive_config                   string      dg_config=(standby,primary,logical)\r\n<\/pre>\n<pre class=\"lang:default decode:true \">[Logical-1] SQL&gt; show parameter log_archive_config\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\nlog_archive_config                   string      dg_config=(logical,primary,standby)\r\n<\/pre>\n<p>We are querying some information of databases in Environment.<\/p>\n<pre class=\"lang:default decode:true \">[Primary-1] SQL&gt; select d.open_mode, d.database_role, a.database_mode, a.recovery_mode, a.protection_mode from v$archive_dest_status a, v$database d where a.database_mode &lt;&gt; 'UNKNOWN';\r\n\r\nOPEN_MODE            DATABASE_ROLE    DATABASE_MODE   RECOVERY_MODE        PROTECTION_MODE\r\n-------------------- ---------------- --------------- ----------------------- --------------------\r\nREAD WRITE           PRIMARY          OPEN            IDLE        MAXIMUM PERFORMANCE\r\nREAD WRITE           PRIMARY          MOUNTED-STANDBY MANAGED REAL TIME APPLY MAXIMUM PERFORMANCE\r\nREAD WRITE           PRIMARY          OPEN            LOGICAL REAL TIME APPLY MAXIMUM PERFORMANCE\r\n<\/pre>\n<p>We are questioning the SYNC status of Primary and Standby Databases.<\/p>\n<pre class=\"lang:default decode:true \">[Primary-1] SQL&gt; select max(sequence#),thread# from v$archived_log group by thread#;\r\n\r\nMAX(SEQUENCE#)    THREAD#\r\n-------------- ----------\r\n           555          1\r\n           313          2\r\n<\/pre>\n<pre class=\"lang:default decode:true \">[Physical-1] SQL&gt; select max(sequence#),thread# from v$archived_log group by thread#;\r\n\r\nMAX(SEQUENCE#)    THREAD#\r\n-------------- ----------\r\n           555          1\r\n           313          2\r\n<\/pre>\n<pre class=\"lang:default decode:true \">[Logical-1] SQL&gt; SELECT max(sequence#),thread#,applied FROM dba_logstdby_log group by thread#, applied;\r\n\r\nMAX(SEQUENCE#)    THREAD# APPLIED\r\n-------------- ---------- --------\r\n           555          1 YES\r\n           313          2 YES\r\n<\/pre>\n<p>3. We REMOVE from the Logical Standby Database Broker Configuration.<\/p>\n<pre class=\"lang:default decode:true \">DGMGRL&gt; remove database \"logical\"\r\nRemoved database \"logical\" from the configuration\r\n\r\nDGMGRL&gt; show configuration\r\n\r\nConfiguration - Broker _Configuration\r\n\r\n  Protection Mode: MaxPerformance\r\n  Databases:\r\n    primary - Primary database\r\n    standby - Physical standby database\r\n\r\nFast-Start Failover: DISABLED\r\n\r\nConfiguration Status:\r\nSUCCESS\r\n<\/pre>\n<p>We are querying the value of the LOG_ARCHIVE_CONFIG parameter.<\/p>\n<pre class=\"lang:default decode:true \">[Primary-1] SQL&gt; show parameter log_archive_config\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\nlog_archive_config                   string      dg_config=(primary,standby)\r\n<\/pre>\n<pre class=\"lang:default decode:true \">[Physical-1] SQL&gt; show parameter log_archive_config\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\nlog_archive_config                   string      dg_config=(standby,primary)\r\n<\/pre>\n<pre class=\"lang:default decode:true \">[Logical-1] SQL&gt; show parameter log_archive_config\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\nlog_archive_config                   string      dg_config=(logical)\r\n<\/pre>\n<p>We are querying the value of the LOG_ARCHIVE_DEST_n parameter.<\/p>\n<pre class=\"lang:default decode:true \">[Primary-1] SQL&gt; column name format a30\r\n[Primary-1] SQL&gt; column value format a94\r\n[Primary-1] SQL&gt; set linesize 9000\r\n[Primary-1] SQL&gt; select name, value from v$parameter where lower(name) like '%log_archive_dest%' and lower(name) not like '%log_archive_dest_state%' and value is not null;\r\n\r\nNAME                           VALUE\r\n------------------------------ ----------------------------------------------------------------------------------------------\r\nlog_archive_dest_1             LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=primary\r\nlog_archive_dest_2             service=\"standby\", LGWR ASYNC NOAFFIRM delay=0 optional compression=disable max_failure=0 max_\r\n                               connections=1 reopen=300 db_unique_name=\"standby\" net_timeout=30, valid_for=(all_logfiles,prim\r\n                               ary_role)\r\n<\/pre>\n<pre class=\"lang:default decode:true \">[Physical-1] SQL&gt; column name format a30\r\n[Physical-1] SQL&gt; column value format a94\r\n[Physical-1] SQL&gt; set linesize 9000\r\n[Physical-1] SQL&gt; select name, value from v$parameter where lower(name) like '%log_archive_dest%' and lower(name) not like '%log_archive_dest_state%' and value is not null;\r\n\r\nNAME                           VALUE\r\n------------------------------ ----------------------------------------------------------------------------------------------\r\nlog_archive_dest_1             LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=standby\r\n<\/pre>\n<pre class=\"lang:default decode:true \">[Logical-1] SQL&gt; column name format a30\r\n[Logical-1] SQL&gt; column value format a94\r\n[Logical-1] SQL&gt; set linesize 9000\r\n[Logical-1] SQL&gt; select name, value from v$parameter where lower(name) like '%log_archive_dest%' and lower(name) not like '%log_archive_dest_state%' and value is not null;\r\n\r\nNAME                           VALUE\r\n------------------------------ ----------------------------------------------------------------------------------------------\r\nlog_archive_dest_1             LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=logical\r\n<\/pre>\n<p>We question the value of the DMON process.<\/p>\n<pre class=\"lang:default decode:true \">[oracle@logical1 ~]$ ps -ef |grep ora_dmon |grep -v grep\r\noracle    4812     1  0 Jan14 ?        00:00:03 ora_dmon_primary1\r\n<\/pre>\n<p>We query the value of the DG_BROKER_START parameter.<\/p>\n<pre class=\"lang:default decode:true \">[Logical-1] SQL&gt; show parameter dg_broker_start\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\ndg_broker_start                      boolean     TRUE\r\n<\/pre>\n<h5>CONCLUSION<\/h5>\n<p>The REMOVE database is removed from the LOG_ARCHIVE_CONFIG parameter.<\/p>\n<p>The values in the LOG_ARCHIVE_DEST_n parameter that provides Redo-Transport to the REMOVE database are deleted.<\/p>\n<p>The DG_BROKER_START parameter remains at TRUE.<\/p>\n<p>The DMON process continues to run.<\/p>\n<p>Configuration files in the REMOVE database continue to exist in the relevant directories.<\/p>\n<p>4. We REMOVE from the Broker Configuration with the Physical Standby Database PRESERVE DESTINATIONS syntax.<\/p>\n<pre class=\"lang:default decode:true \">DGMGRL&gt; remove database \"standby\" preserve destinations;\r\nRemoved database \"standby\" from the configuration\r\n<\/pre>\n<p>We query the broker configuration.<\/p>\n<pre class=\"lang:default decode:true \">DGMGRL&gt; show configuration\r\n\r\nConfiguration - Broker _Configuration\r\n\r\n  Protection Mode: MaxPerformance\r\n  Databases:\r\n    primary - Primary database\r\n\r\nFast-Start Failover: DISABLED\r\n\r\nConfiguration Status:\r\nSUCCESS\r\n<\/pre>\n<p>We are querying the value of the LOG_ARCHIVE_DEST_n parameter.<\/p>\n<pre class=\"lang:default decode:true \">[Primary-1] SQL&gt; column name format a30\r\n[Primary-1] SQL&gt; column value format a94\r\n[Primary-1] SQL&gt; set linesize 9000\r\n[Primary-1] SQL&gt; select name, value from v$parameter where lower(name) like '%log_archive_dest%' and lower(name) not like '%log_archive_dest_state%' and value is not null;\r\n\r\nNAME                           VALUE\r\n------------------------------ ----------------------------------------------------------------------------------------------\r\nlog_archive_dest_1             LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=primary\r\nlog_archive_dest_2             service=\"standby\", LGWR ASYNC NOAFFIRM delay=0 optional compression=disable max_failure=0 max_\r\n                               connections=1 reopen=300 db_unique_name=\"standby\" net_timeout=30, valid_for=(all_logfiles,prim\r\n                               ary_role)\r\n<\/pre>\n<p>We are querying the value of the LOG_ARCHIVE_CONFIG parameter.<\/p>\n<pre class=\"lang:default decode:true \">[Primary-1] SQL&gt; show parameter log_archive_config\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\nlog_archive_config                   string      dg_config=(primary,standby)\r\n<\/pre>\n<pre class=\"lang:default decode:true \">[Physical-1] SQL&gt; show parameter log_archive_config\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\nlog_archive_config                   string      dg_config=(standby,primary)\r\n<\/pre>\n<h5>CONCLUSION<\/h5>\n<p>The REMOVE database is not removed from the LOG_ARCHIVE_CONFIG parameter.<\/p>\n<p>The values in the LOG_ARCHIVE_DEST_n parameter that provide Redo-Transport to the REMOVE database are not deleted.<\/p>\n<p>The DG_BROKER_START parameter remains at TRUE.<\/p>\n<p>The DMON process continues to run.<\/p>\n<p>Configuration files in the REMOVE database continue to exist in the relevant directories.<\/p>\n<p>5. A Broker Configuration with all values from step one and step 2 is REMOVE without the PRESERVE DESTINATIONS systax.<\/p>\n<pre class=\"lang:default decode:true \">DGMGRL&gt; remove configuration\r\nRemoved configuration\r\nDGMGRL&gt; show configuration\r\nORA-16532: Data Guard broker configuration does not exist\r\n<\/pre>\n<p>Configuration details cannot be determined by DGMGRL<\/p>\n<p>We query the value of the LOG_ARCHIVE_DEST_n parameter.<\/p>\n<pre class=\"lang:default decode:true \">[Primary-1] SQL&gt; column name format a30\r\n[Primary-1] SQL&gt; column value format a94\r\n[Primary-1] SQL&gt; set linesize 9000\r\n[Primary-1] SQL&gt; select name, value from v$parameter where lower(name) like '%log_archive_dest%' and lower(name) not like '%log_archive_dest_state%' and value is not null;\r\nNAME                           VALUE\r\n------------------------------ ----------------------------------------------------------------------------------------------\r\nlog_archive_dest_1             LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=primary\r\n<\/pre>\n<p>The value of the LOG_ARCHIVE_CONFIG parameter is queried.<\/p>\n<pre class=\"lang:default decode:true \">[Primary-1] SQL&gt; show parameter log_archive_config\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\nlog_archive_config                   string      nodg_config\r\n<\/pre>\n<p>We query the status of the DMON process.<\/p>\n<pre class=\"lang:default decode:true \">[oracle@primary1 ~]$ ps -ef | grep ora_dmon |grep -v grep\r\noracle   29544     1  0 21:02 ?        00:00:00 ora_dmon_primary1\r\n<\/pre>\n<p>We query the value of the DG_BROKER_START parameter.<\/p>\n<pre class=\"lang:default decode:true \">[Primary-1] SQL&gt; show parameter dg_broker\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\ndg_broker_config_file1               string      +data\/PRIMARY\/BROKER_CONF_FILE\/dr1primary.dat\r\ndg_broker_config_file2               string      +FRA\/PRIMARY\/BROKER_CONF_FILE\/dr2primary.dat\r\ndg_broker_start                      boolean     TRUE\r\n<\/pre>\n<p>It is questioned whether the Broker Configuration Files are in the relevant locations.<\/p>\n<pre class=\"lang:default decode:true \">[grid@primary1 ~]$ asmcmd\r\nASMCMD&gt; ls\r\nDATA\/\r\nFRA\/\r\nOCR_VOTE\/\r\nASMCMD&gt; cd +data\r\nASMCMD&gt; ls\r\nPRIMARY\/\r\nASMCMD&gt; cd primary\r\nASMCMD&gt; ls\r\nBROKER_CONF_FILE\/\r\nCHANGETRACKING\/\r\nCONTROLFILE\/\r\nDATAFILE\/\r\nDATAGUARDCONFIG\/\r\nONLINELOG\/\r\nPARAMETERFILE\/\r\nTEMPFILE\/\r\nspfileprimary.ora\r\nASMCMD&gt; cd BROKER_CONF_FILE\r\nASMCMD&gt; ls\r\ndr1primary.dat\r\n<\/pre>\n<h5>CONCLUSION<\/h5>\n<p>It can be seen that there is no data guard conf in the LOG_ARCHIVE_CONFIG parameter.<\/p>\n<p>LOG_ARCHIVE_DEST_n parameters that provide Redo-Transport are blank.<\/p>\n<p>The DG_BROKER_START parameter remains at TRUE.<\/p>\n<p>The DMON process continues to run.<\/p>\n<p>Configuration files in the REMOVE database continue to exist in the relevant directories.<\/p>\n<p>6. What to do after the BROKER Configuration is REMOVE.<\/p>\n<p>We set the DG_BROKER_START parameter to FALSE.<\/p>\n<pre class=\"lang:default decode:true \">[Primary-1] SQL&gt; alter system set dg_broker_start=FALSE scope=both sid='*';\r\n\r\nSystem altered.\r\n\r\n[Primary-1] SQL&gt; show parameter dg_broker\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\ndg_broker_config_file1               string      +data\/PRIMARY\/BROKER_CONF_FILE\r\n                                                 \/dr1primary.dat\r\ndg_broker_config_file2               string      +FRA\/PRIMARY\/BROKER_CONF_FILE\/\r\n                                                 dr2primary.dat\r\ndg_broker_start                      boolean     FALSE\r\n<\/pre>\n<p>Configuration files are deleted from the respective directories.<\/p>\n<p>&nbsp;<\/p>\n<div class=\"pvc_clear\"><\/div>\n<p id=\"pvc_stats_46597\" class=\"pvc_stats all  \" data-element-id=\"46597\" style=\"\"><i class=\"pvc-stats-icon medium\" aria-hidden=\"true\"><svg aria-hidden=\"true\" focusable=\"false\" data-prefix=\"far\" data-icon=\"chart-bar\" role=\"img\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 512 512\" class=\"svg-inline--fa fa-chart-bar fa-w-16 fa-2x\"><path fill=\"currentColor\" d=\"M396.8 352h22.4c6.4 0 12.8-6.4 12.8-12.8V108.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v230.4c0 6.4 6.4 12.8 12.8 12.8zm-192 0h22.4c6.4 0 12.8-6.4 12.8-12.8V140.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v198.4c0 6.4 6.4 12.8 12.8 12.8zm96 0h22.4c6.4 0 12.8-6.4 12.8-12.8V204.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v134.4c0 6.4 6.4 12.8 12.8 12.8zM496 400H48V80c0-8.84-7.16-16-16-16H16C7.16 64 0 71.16 0 80v336c0 17.67 14.33 32 32 32h464c8.84 0 16-7.16 16-16v-16c0-8.84-7.16-16-16-16zm-387.2-48h22.4c6.4 0 12.8-6.4 12.8-12.8v-70.4c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v70.4c0 6.4 6.4 12.8 12.8 12.8z\" class=\"\"><\/path><\/svg><\/i> <img loading=\"lazy\" decoding=\"async\" width=\"16\" height=\"16\" alt=\"Loading\" src=\"https:\/\/dbtut.com\/wp-content\/plugins\/page-views-count\/ajax-loader-2x.gif\" border=0 \/><\/p>\n<div class=\"pvc_clear\"><\/div>\n","protected":false},"excerpt":{"rendered":"<p>In today&#8217;s article, I will tell you about Data Guard Broker-Removing Database And Broker Configuration In Environment. We may want to REMOVE one, several or the entire Broker Configuration in the Broker Environment. The operation steps are as follows. 1. Before REMOVE, we query the Databases in Configuration and Environment separately. DGMGRL&gt; show configuration Configuration &hellip;<\/p>\n<div class=\"pvc_clear\"><\/div>\n<p id=\"pvc_stats_46597\" class=\"pvc_stats all  \" data-element-id=\"46597\" style=\"\"><i class=\"pvc-stats-icon medium\" aria-hidden=\"true\"><svg aria-hidden=\"true\" focusable=\"false\" data-prefix=\"far\" data-icon=\"chart-bar\" role=\"img\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 512 512\" class=\"svg-inline--fa fa-chart-bar fa-w-16 fa-2x\"><path fill=\"currentColor\" d=\"M396.8 352h22.4c6.4 0 12.8-6.4 12.8-12.8V108.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v230.4c0 6.4 6.4 12.8 12.8 12.8zm-192 0h22.4c6.4 0 12.8-6.4 12.8-12.8V140.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v198.4c0 6.4 6.4 12.8 12.8 12.8zm96 0h22.4c6.4 0 12.8-6.4 12.8-12.8V204.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v134.4c0 6.4 6.4 12.8 12.8 12.8zM496 400H48V80c0-8.84-7.16-16-16-16H16C7.16 64 0 71.16 0 80v336c0 17.67 14.33 32 32 32h464c8.84 0 16-7.16 16-16v-16c0-8.84-7.16-16-16-16zm-387.2-48h22.4c6.4 0 12.8-6.4 12.8-12.8v-70.4c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v70.4c0 6.4 6.4 12.8 12.8 12.8z\" class=\"\"><\/path><\/svg><\/i> <img loading=\"lazy\" decoding=\"async\" width=\"16\" height=\"16\" alt=\"Loading\" src=\"https:\/\/dbtut.com\/wp-content\/plugins\/page-views-count\/ajax-loader-2x.gif\" border=0 \/><\/p>\n<div class=\"pvc_clear\"><\/div>\n","protected":false},"author":484,"featured_media":46672,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[4],"tags":[],"class_list":["post-46597","post","type-post","status-publish","format-standard","has-post-thumbnail","","category-oracle"],"aioseo_notices":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v24.9 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Removing Database And Broker Configuration In Environment - Database Tutorials<\/title>\n<meta name=\"description\" content=\"In today&#039;s article, I will tell you about Data Guard Broker-Removing Database And Broker Configuration In Environment.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Removing Database And Broker Configuration In Environment - Database Tutorials\" \/>\n<meta property=\"og:description\" content=\"In today&#039;s article, I will tell you about Data Guard Broker-Removing Database And Broker Configuration In Environment.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/\" \/>\n<meta property=\"og:site_name\" content=\"Database Tutorials\" \/>\n<meta property=\"article:published_time\" content=\"2022-05-26T11:23:17+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-05-26T11:27:23+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/05\/Ekran-Alintisi-18.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"813\" \/>\n\t<meta property=\"og:image:height\" content=\"341\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Onur ARDAHANLI\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Onur ARDAHANLI\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/\"},\"author\":{\"name\":\"Onur ARDAHANLI\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6\"},\"headline\":\"Removing Database And Broker Configuration In Environment\",\"datePublished\":\"2022-05-26T11:23:17+00:00\",\"dateModified\":\"2022-05-26T11:27:23+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/\"},\"wordCount\":509,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/dbtut.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/05\/Ekran-Alintisi-18.jpg\",\"articleSection\":[\"ORACLE\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/\",\"url\":\"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/\",\"name\":\"Removing Database And Broker Configuration In Environment - Database Tutorials\",\"isPartOf\":{\"@id\":\"https:\/\/dbtut.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/05\/Ekran-Alintisi-18.jpg\",\"datePublished\":\"2022-05-26T11:23:17+00:00\",\"dateModified\":\"2022-05-26T11:27:23+00:00\",\"description\":\"In today's article, I will tell you about Data Guard Broker-Removing Database And Broker Configuration In Environment.\",\"breadcrumb\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/#primaryimage\",\"url\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/05\/Ekran-Alintisi-18.jpg\",\"contentUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/05\/Ekran-Alintisi-18.jpg\",\"width\":813,\"height\":341},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/dbtut.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Removing Database And Broker Configuration In Environment\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/dbtut.com\/#website\",\"url\":\"https:\/\/dbtut.com\/\",\"name\":\"Database Tutorials\",\"description\":\"MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux\",\"publisher\":{\"@id\":\"https:\/\/dbtut.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/dbtut.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/dbtut.com\/#organization\",\"name\":\"dbtut\",\"url\":\"https:\/\/dbtut.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg\",\"contentUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg\",\"width\":223,\"height\":36,\"caption\":\"dbtut\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6\",\"name\":\"Onur ARDAHANLI\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/ecd20c3e1374ced4e1aefc82101cce4cd437be8fd957d1be3d106668b8a1b990?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/ecd20c3e1374ced4e1aefc82101cce4cd437be8fd957d1be3d106668b8a1b990?s=96&d=mm&r=g\",\"caption\":\"Onur ARDAHANLI\"},\"url\":\"https:\/\/dbtut.com\/index.php\/author\/onurardahanli\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Removing Database And Broker Configuration In Environment - Database Tutorials","description":"In today's article, I will tell you about Data Guard Broker-Removing Database And Broker Configuration In Environment.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/","og_locale":"en_US","og_type":"article","og_title":"Removing Database And Broker Configuration In Environment - Database Tutorials","og_description":"In today's article, I will tell you about Data Guard Broker-Removing Database And Broker Configuration In Environment.","og_url":"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/","og_site_name":"Database Tutorials","article_published_time":"2022-05-26T11:23:17+00:00","article_modified_time":"2022-05-26T11:27:23+00:00","og_image":[{"width":813,"height":341,"url":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/05\/Ekran-Alintisi-18.jpg","type":"image\/jpeg"}],"author":"Onur ARDAHANLI","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Onur ARDAHANLI","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/#article","isPartOf":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/"},"author":{"name":"Onur ARDAHANLI","@id":"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6"},"headline":"Removing Database And Broker Configuration In Environment","datePublished":"2022-05-26T11:23:17+00:00","dateModified":"2022-05-26T11:27:23+00:00","mainEntityOfPage":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/"},"wordCount":509,"commentCount":0,"publisher":{"@id":"https:\/\/dbtut.com\/#organization"},"image":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/#primaryimage"},"thumbnailUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/05\/Ekran-Alintisi-18.jpg","articleSection":["ORACLE"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/","url":"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/","name":"Removing Database And Broker Configuration In Environment - Database Tutorials","isPartOf":{"@id":"https:\/\/dbtut.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/#primaryimage"},"image":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/#primaryimage"},"thumbnailUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/05\/Ekran-Alintisi-18.jpg","datePublished":"2022-05-26T11:23:17+00:00","dateModified":"2022-05-26T11:27:23+00:00","description":"In today's article, I will tell you about Data Guard Broker-Removing Database And Broker Configuration In Environment.","breadcrumb":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/#primaryimage","url":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/05\/Ekran-Alintisi-18.jpg","contentUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/05\/Ekran-Alintisi-18.jpg","width":813,"height":341},{"@type":"BreadcrumbList","@id":"https:\/\/dbtut.com\/index.php\/2022\/05\/26\/removing-database-and-broker-configuration-in-environment\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/dbtut.com\/"},{"@type":"ListItem","position":2,"name":"Removing Database And Broker Configuration In Environment"}]},{"@type":"WebSite","@id":"https:\/\/dbtut.com\/#website","url":"https:\/\/dbtut.com\/","name":"Database Tutorials","description":"MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux","publisher":{"@id":"https:\/\/dbtut.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/dbtut.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/dbtut.com\/#organization","name":"dbtut","url":"https:\/\/dbtut.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/#\/schema\/logo\/image\/","url":"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg","contentUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg","width":223,"height":36,"caption":"dbtut"},"image":{"@id":"https:\/\/dbtut.com\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6","name":"Onur ARDAHANLI","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/ecd20c3e1374ced4e1aefc82101cce4cd437be8fd957d1be3d106668b8a1b990?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/ecd20c3e1374ced4e1aefc82101cce4cd437be8fd957d1be3d106668b8a1b990?s=96&d=mm&r=g","caption":"Onur ARDAHANLI"},"url":"https:\/\/dbtut.com\/index.php\/author\/onurardahanli\/"}]}},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts\/46597","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/users\/484"}],"replies":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/comments?post=46597"}],"version-history":[{"count":0,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts\/46597\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/media\/46672"}],"wp:attachment":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/media?parent=46597"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/categories?post=46597"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/tags?post=46597"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}