Monday , July 4 2022

Removing Database And Broker Configuration In Environment

In today’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.

2. After REMOVE the configuration, we do some checks to find out how the system will work.

We query the status of the DG_BROKER_START parameter.

We question the existence of the DMON process.

We query the existence of the configuration files.

We are querying the values of the LOG_ARCHIVE_DEST_n parameters.

We are querying the values of the LOG_ARCHIVE_CONFIG parameters.

We are querying some information of databases in Environment.

We are questioning the SYNC status of Primary and Standby Databases.

3. We REMOVE from the Logical Standby Database Broker Configuration.

We are querying the value of the LOG_ARCHIVE_CONFIG parameter.

We are querying the value of the LOG_ARCHIVE_DEST_n parameter.

We question the value of the DMON process.

We query the value of the DG_BROKER_START parameter.

CONCLUSION

The REMOVE database is removed from the LOG_ARCHIVE_CONFIG parameter.

The values in the LOG_ARCHIVE_DEST_n parameter that provides Redo-Transport to the REMOVE database are deleted.

The DG_BROKER_START parameter remains at TRUE.

The DMON process continues to run.

Configuration files in the REMOVE database continue to exist in the relevant directories.

4. We REMOVE from the Broker Configuration with the Physical Standby Database PRESERVE DESTINATIONS syntax.

We query the broker configuration.

We are querying the value of the LOG_ARCHIVE_DEST_n parameter.

We are querying the value of the LOG_ARCHIVE_CONFIG parameter.

CONCLUSION

The REMOVE database is not removed from the LOG_ARCHIVE_CONFIG parameter.

The values in the LOG_ARCHIVE_DEST_n parameter that provide Redo-Transport to the REMOVE database are not deleted.

The DG_BROKER_START parameter remains at TRUE.

The DMON process continues to run.

Configuration files in the REMOVE database continue to exist in the relevant directories.

5. A Broker Configuration with all values from step one and step 2 is REMOVE without the PRESERVE DESTINATIONS systax.

Configuration details cannot be determined by DGMGRL

We query the value of the LOG_ARCHIVE_DEST_n parameter.

The value of the LOG_ARCHIVE_CONFIG parameter is queried.

We query the status of the DMON process.

We query the value of the DG_BROKER_START parameter.

It is questioned whether the Broker Configuration Files are in the relevant locations.

CONCLUSION

It can be seen that there is no data guard conf in the LOG_ARCHIVE_CONFIG parameter.

LOG_ARCHIVE_DEST_n parameters that provide Redo-Transport are blank.

The DG_BROKER_START parameter remains at TRUE.

The DMON process continues to run.

Configuration files in the REMOVE database continue to exist in the relevant directories.

6. What to do after the BROKER Configuration is REMOVE.

We set the DG_BROKER_START parameter to FALSE.

Configuration files are deleted from the respective directories.

 

Onur ARDAHANLI
Author: Onur ARDAHANLI

About Onur ARDAHANLI

Leave a Reply

Your email address will not be published. Required fields are marked *