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

F.4.5 Converting a Snapshot Standby Database into a Physical Standby Database

The transition figure that converting a snapshot standby database into a physical standby database on standby site is as follows.

Note

• This operation is executed only on the standby site. The operation on the primary site is not necessary.

1. Initial status.

   

2. 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 standby site.

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

   Confirm that the state of userApplication becomes “Maintenance".
   

3. Monitoring disruption of Oracle resource.

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

   # /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".)

   

4. Converting roll of Oracle Data Guard.

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

   See

   For further details, refer to the Oracle Database manual.

   1. Mount the standby database, if it is not mounted.

      SQL> SHUTDOWN IMMEDIATE
      SQL> STARTUP MOUNT

   2. Perform the conversion.

      SQL> ALTER DATABASE CONVERT TO PHYSICAL STANDBY;

   3. Restart the standby database mount or open.

      SQL> SHUTDOWN IMMEDIATE
      SQL> STARTUP MOUNT or STARTUP

   4. Start REDO Apply on the physical standby database.

      Issue the following SQL statement according to the REDOApply of the Oracle instance resource on the 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.

   After the roll is converted, it becomes the following. (The following example shows when operating in the state of MOUNTED.）

   

5. Restart Oracle resource monitoring.

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

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

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

   

6. Stop maintenance mode of PRIMECLUSTER.

   Stop the maintenance mode of PRIMECLUSTER on the operation node of standby site.

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

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