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

F.3.1 Oracle database Control through PRIMECLUSTER Wizard for Oracle

This section describes startup, shutdown and monitoring of Oracle resources in standby operation using Oracle Data Guard/Oracle Active Data Guard.

Oracle instance Startup

Startup procedure of an Oracle instance is as follows:

1. su - <Oracle user>

2. sqlplus /nolog

3. connect / as sysdba

4. startup nomount or startup mount

5. alter database mount; (if "startup nomount" was executed at step "4")

6. The procedure according to the database role is executed.

   • Primary Database

     ALTER DATABASE OPEN;

   • Physical Standby Database

     The procedure according to the REDOApply of the Oracle instance resource is executed.

     • ReceiveOnly

       No procedure.

     • NormalApply

       ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING ARCHIVED LOGFILE DISCONNECT;

     • RealTimeApply

       ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT;

     • ReadOnlyOPEN

       ALTER DATABASE OPEN;

     • RealTimeQueryN

       ALTER DATABASE OPEN;
       ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING ARCHIVED LOGFILE DISCONNECT;

     • RealTimeQueryR

       ALTER DATABASE OPEN;
       ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT;

   • Logical Standby Database

     The procedure according to the REDOApply of the Oracle instance resource is executed.

     • ReceiveOnly, ReadOnlyOPEN, RealTimeQueryN, RealTimeQueryR

       ALTER DATABASE OPEN;

     • NormalApply

       ALTER DATABASE OPEN;
       ALTER DATABASE START LOGICAL STANDBY APPLY;

     • RealTimeApply

       ALTER DATABASE OPEN;
       ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;

   • Snapshot Standby Database

     ALTER DATABASE OPEN;

     
     

Oracle instance Shutdown

Shutdown procedure of an Oracle instance is as follows:

• Shutdown procedure of an Oracle instance by user operation is as follows:

  1. su - <Oracle user>

  2. sqlplus /nolog

  3. connect / as sysdba

  4. When the roll is PHYSICAL STANDBY or LOGICAL STANDBY, stop REDO apply.

     • Physical Standby Database

       ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

     • Logical Standby Database

       ALTER DATABASE ABORT LOGICAL STANDBY APPLY;

  5. shutdown <immediate / abort / transactional> (Setup with StopModeStop)

     Default : immediate

  6. If Oracle instance is not stopped at step "5" (except for abort), use shutdown abort.

  7. If Oracle instance is not stopped at step "5" or "6", shut it down forcibly by sending SIGKILL to the background process.

     
     

• Shutdown procedure of an Oracle instance by resource failure or failover is as follows:

  1. su - <Oracle user>

  2. sqlplus /nolog

  3. connect / as sysdba

  4. shutdown <immediate / abort> (Setup with StopModeFail)

     Default : abort

  5. If Oracle instance is not stopped at step "4" (except for abort), use shutdown abort.

  6. If Oracle instance is not stopped at step "4" or "5", shut it down forcibly by sending SIGKILL to the background process.

Oracle instance Monitoring

Monitoring procedure of an Oracle instance is as follows:

1. Check the Oracle background processes (PMON, SMON) every 30 seconds (static).
   If the processes status can be confirmed after Oracle instance gets activated, go to the step "2".

2. su - <Oracle user>

3. Local connection to the Oracle instance as the SYSTEM user or SYSDBA privilege.

4. When the roll is PRIMARY, LOGICAL STANDBY or SNAPSHOT STANDBY, check the status of the Oracle instance is “OPEN".
   When the roll is PHYSICAL STANDBY, check the status of the Oracle instance is "MOUNTED" or “OPEN".

5. Check if the Oracle background processes (PMON, SMON, DBWn, LGWR, CKPT) are alive.
   The monitoring interval can be changed at the setting of "Interval" and its default value is 30 seconds.

6. When the roll is PRIMARY, check if SQL (INSERT, UPDATE, DELETE and COMMIT) can be properly executed using the monitoring table on the SYSTEM user's default table space.
   The monitoring with SQL is executed in accordance with the setting of "Interval". The elapsed time from the last monitoring is checked. Only when 60 seconds or more pass, the monitoring with SQL is executed.

7. Oracle instance is reconnected once every 24 hours.

   
   

In the standby node, step 1 is executed to confirm that the Oracle background processes (PMON, SMON) do not exist

Listener Startup/Shutdown/Monitoring

Listener Startup/Shutdown/Monitoring is same as does not use Oracle Data Guard.
For details, see "3.1 Oracle database Control through PRIMECLUSTER Wizard for Oracle".

Oracle ASM instance Startup/Shutdown/Monitoring

Oracle ASM instance Startup/Shutdown/Monitoring is same as does not use Oracle Data Guard.
For details, see "3.1 Oracle database Control through PRIMECLUSTER Wizard for Oracle".