Wednesday , March 29 2023

Switchover Using DGMGRL

In today’s article we will learn to Switchover Using DGMGRL.

We can also do Switchover from DGMGRL. Switchover from DGMGRL is easier. It automatically executes all the commands we run using SQL.

Those that need to be closed from instances close themselves. In summary, the processing steps are much less and easier than SQL.

In Oracle 12c, whether Primary and Standby Database is ready for Switchover can be done with validate commands from DGMGRL. But 11g does not have these commands, as in SQL, the controls must be done manually.

If the checks are made and the result is successful, the Switchover process from DGMGRL is as follows.

1. We query the status of the Broker configuration from DGMGRL.

2.We check whether Primary and Standby Database are ready for Switchover with SQL commands.

3.We perform the Switchover operation from DGMGRL.

The reason for getting this error is that a static listener must be defined so that the broker can STARTUP the database after SHUTDOWN. Since this definition could not be made exactly correctly, it could not start automatically.

4. We have a New Physical Standby Database startup, which cannot start automatically due to the Static Listener not being set correctly.

5.We start the checks.

a. We query the status of instances.

b. After the switchover, we question whether EskiPhysical Standby is Primary.

c. We query whether the Redo Apply processes have started.

ç. We check if there is Redo Transport and Apply LAG in the Standby Databases.

d.With this method, we also check whether the Log Switch operation is done properly and whether there are Redo and Transport LAGs afterwards.

The reason for adding the first_time condition to the WHERE condition in the query is because the databases eat RESETLOGS due to previous tests and therefore SEQUENCE#’s are reset.





Author: Onur ARDAHANLI


Leave a Reply

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