PRIMECLUSTER Wizard for Oracle (PRIMEQUEST) 4.3 Configuration and Administration Guide

F.4.2 Switch of Primary Database and Physical Standby Database

The transition figure of the switch of primary database and physical standby database is as follows.

1. Initial status.

   

2. Confirm if there is redo gap on a physical standby database.

   Confirm whether the sequence number is corresponding to the primary site and the standby site before and after the log switch. If the sequence number do not correspond, resolve a redo gap.
   

   See

   For further details, refer to the Oracle Database manual.

3. Start maintenance mode of PRIMECLUSTER.

   To prevent the failover that userApplication does not intend, start the maintenance mode of PRIMECLUSTER on the operation node of both sites.

   # /opt/SMAW/SMAWRrms/bin/hvutil -M on

   Confirm that the state of userApplication becomes “Maintenance".

   

4. Monitoring disruption of Oracle resource.

   To kill the session to Oracle, stop monitoring the Oracle instance and Listener resources on the both nodes of both sites.

   # /opt/FJSVclora/sbin/hvoradisable -a <userApplication>

   Confirm that stop of monitoring have been successfully done.
   (Refer to note of "4.1 hvoradisable - Discontinue Monitoring Resources".)

   

5. Switch roll of Oracle Data Guard (Switchover)

   The procedure that switch roll of Oracle Data Guard is as follows.

   See

   For further details, refer to the Oracle Database manual.

   1. Verify it is possible to perform a switchover.
      Issue the following SQL statement on a primary database.

      SQL> ALTER DATABASE SWITCHOVER TO <db_unique_name of target standby database> VERIFY;

      If this operation had been successful, a database altered message would have been returned. Go to the next step.
      If Oracle database error was returned, resolve the error. After issue the above SQL statement again.

   2. Initiate the switchover.
      Issue the following SQL statement on a primary database to initiate the switchover.

      SQL> ALTER DATABASE SWITCHOVER TO <db_unique_name of target standby database>;

      The database of the new standby site stops.
      The database roll of new primary site becomes "PRIMARY".

      

   3. Open the new primary database.
      Issue the following SQL statement on a new primary database.

      SQL> ALTER DATABASE OPEN;

      

   4. Mount a new physical standby database.

      Issue the following SQL statement on a new standby database.

      SQL> STARTUP MOUNT;

      When a new standby database is a physical standby database of Oracle Active Data Guard, open the database to "READ ONLY" by issuing the following SQL statement.

      SQL> STARTUP;

      

   5. Start REDO Apply on the new physical standby database.
      Issue the following SQL statement according to the REDOApply of the Oracle instance resource on the new standby database.

      • NormalApply, RealTimeQueryN

        SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING ARCHIVED LOGFILE DISCONNECT;

      • RealTimeApply, RealTimeQueryR

        SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT;

      • NormalApply, ReadOnlyOPEN
        No procedure.

6. Restart Oracle resource monitoring.

   Start monitoring the Oracle instance and Listener resources on the both nodes of both sites.

   # /opt/FJSVclora/sbin/hvoraenable -a <userApplication>

   Confirm that restart of monitoring have been successfully done.
   (Refer to note of "4.2 hvoraenable - Restart Monitoring Resources".)

   

7. Stop maintenance mode of PRIMECLUSTER.

   Stop the maintenance mode of PRIMECLUSTER on the operation node of both sites.

   # /opt/SMAW/SMAWRrms/bin/hvutil -M off

   Confirme the state of userApplication becomes "Online" or "Offline".