In the Oracle Data Guard/Oracle Active Data Guard environment, you can operate Oracle database on the primary site and standby site as a standby operation or a scalable operation on a PRIMECLUSTER system.
This software provides the following features:
Feature | Description |
|---|---|
Environment Setup | Environment setup tool to enable clustering of Oracle database |
Monitoring | Daemon processes to monitor Oracle instance, Listener and detect their failures |
Start and Stop Control | Scripts used for startup and stop of Oracle instances, Listeners |
Setup and Operation Commands | Commands used for setup and operations |
Environment Setup
RMS Wizard allows you to set up the REDOApply setting in the standby database. For details, refer to "G.2 Oracle Environment Setting".
Monitoring
PRIMECLUSTER Wizard for Oracle provides daemon processes to monitor Oracle instances and Listeners and detect their failures. If errors are detected in monitoring, Oracle instances and Listeners are restarted and a failover occurs automatically. For details, refer to "G.3 Operation".
Monitoring Oracle instances
The daemon processes monitor Oracle instances in the following way.
Primary Site (Role is "PRIMARY")
The Monitoring of the primary site is same as does not use Oracle Data Guard of "1.1 Feature outline".
Monitoring Processes
The daemon process connects to the Oracle instance as the SYSTEM user and cyclically monitors Oracle background processes (PMON, SMON, DBWn, LGWR and CKPT).
Monitoring a table
The daemon process creates a table for monitoring and cyclically manipulates data on the table with SQL statements (INSERT, UPDATE, DELETE and COMMIT). It checks the SQL execution result to monitor Oracle instances. Therefore, it means that not only the background process failures but also logical failures can be detected.
Standby Site(Role is "PHYSICAL STANDBY" or "LOGICAL STANDBY" or "SNAPSHOT STANDBY")
The daemon process connects to the Oracle instance using SYSDBA privilege ("/ as sysdba") and cyclically monitors Oracle background processes (PMON, SMON, DBWn, LGWR and CKPT).
Monitoring Listener
The daemon process monitors a Listener process in the following way. The Monitoring of the primary site and the standby site is same as does not use Oracle Data Guard of "1.1 Feature outline".
Process Monitoring
The daemon process cyclically monitors Listener process.
Tnsping command
In the standby operation, the daemon process cyclically executes the tnsping command to check that Oracle Net Services are running.
In the scalable operation with Oracle RAC, Oracle Net Services are not monitored by using the tnsping command.
Monitoring Oracle Clusterware
The monitoring of the primary site and the standby site is same as does not use Oracle Data Guard of "1.1 Feature outline".
Oracle Clusterware is not monitored.
Monitoring CDB and PDB
The monitoring of the CDB is the same as "Monitoring Oracle instances".
The monitoring of the PDB is the management table of PDB on the CDB is checked. When fault of PDBs is detected, the message is output to syslog. The restart and the failover due to fault of PDBs is not executed.
For details, see "G.3 Operation".
Startup and stop control
PRIMECLUSTER Wizard for Oracle provides scripts to start up and stop Oracle instances, Listeners and Oracle Clusterware automatically, according to the state transition of userApplication. For details, see "3.1 Oracle database Control through PRIMECLUSTER Wizard for Oracle".
Starting and Stopping Oracle instances
Primary Site (Role is "PRIMARY")
Start and Stop Control of the primary site and the standby site is same as does not use Oracle Data Guard of "1.1 Feature outline".
Start Oracle instance to the OPEN state.
When stopping, the scripts stop the instance in the IMMEDIATE mode. If it fails, the script immediately tries in the ABORT.
Standby Site (Role is "PHYSICAL STANDBY" or "LOGICAL STANDBY" or "SNAPSHOT STANDBY")
Start Oracle instance to the MOUNTED state or the OPEN state, and start apply services. Apply services is not monitored, and redo transport services are not controlled.
When stopping, the scripts stop the instance in the IMMEDIATE mode. If it fails, the script immediately tries in the ABORT. Also apply services is stopped.
Starting and Stopping Listeners
Start and Stop of the primary site and the standby site is same as does not use Oracle Data Guard of "1.1 Feature outline".
The script starts up and stops the Listener with "lsnrctl start/stop" command, checking the state.
Starting and Stopping Oracle Clusterware
Start and Stop of the primary site and the standby site is same as does not use Oracle Data Guard of "1.1 Feature outline".
Oracle Clusterware is started and stopped using the crsctl command.
Starting and Stopping CDB and PDB
The Starting and the stopping of the CDB are the same as "Starting and Stopping Oracle instances".
When the CDB started to the MOUNTED state, the PDBs are not started. When the CDB started to the OPEN state, all the PDBs on the CDB are started. For details, see "G.3 Operation".
Setup and Operation Commands
PRIMECLUSTER Wizard for Oracle provides auxiliary commands for setup and operation. For details, see "Chapter 4 Command".
For details about the operating environment using Oracle Data Guard, see "1.2 Operating Environment".
