NOTE: If you are using VxVM, create appropriate disk groups as required.

If you are using CFS mounted file systems, you can have ${ORACLE_HOME}/dbs and database reside in the same CFS file system. You can also have multiple Oracle databases corresponding to multiple Oracle packages residing in the same CFS file system. However, it is recommended to have different CFS file systems for different Oracle packages.

Setting Up the Toolkit

Toolkit Overview

It is assumed that users have used swinstall to properly install both Serviceguard and the Enterprise Cluster Master Toolkit (referred to as the ECMT), which includes the scripts for Oracle.

After installing the toolkit, six scripts and a README file will be in the/opt/cmcluster/toolkit/ Oracle directory. Two more scripts and one file will be installed which will be used only for modular packages. The two scripts will be in the /etc/cmcluster/scripts/ecmt/Oracle directory and the third file will be installed in the /etc/cmcluster/modules/ecmt/Oracle directory.

For legacy packages, there will be one toolkit configuration script (haOracle.conf ) and nine functional scripts (toolkit.sh , haoracle.sh, haoracle_sql.sh, haoracle.mon, halistener.mon, hadbhang.mon, hagetdbstatus.sh, hatimeoutdbhang.sh and SGAlert.sh)that work with each other to integrate Oracle database with the Serviceguard package control script.

Table 2 Legacy Package Scripts

Script Name

Description

haoracle.conf (toolkit configuration file) This script contains a list of pre-defined variables that the user must customize for use with a particular database instance. This is a configuration file which is read by the toolkit script, haoracle.sh. Table 3 (page 14) shows a list of variables in haoracle.conf which need to be set for the database package.

Main Script (haoracle.sh )

This script contains a list of internally used variables and functions that support

 

the starting and stopping of an Oracle database or ASM instance. This script

 

will be called by toolkit.sh to perform the following:

 

• On package startup, it starts the database or ASM instance, a listener

 

process in case of a database instance as well as launches monitor

 

processes.

 

• On package halt, it stops the database or ASM instance, the listener process

 

in case of a database instance, and monitor process.

 

• Oracle instance start/stop script (haoracle_sql.sh) This script contains

 

functions for starting and stopping Oracle instances and the listeners. This

 

script is invoked by the main script (haoracle.sh) to start up and shut

 

down Oracle.

 

 

Monitor Script (haoracle.mon)

This script contains a list of internally used variables and functions for

 

monitoring an Oracle server instance. This script will be called by

 

haoracle.sh. By default, the following processes are monitored:

 

ora_pmon_$SID_NAME, ora_smon__$SID_NAME, ora_lgwr_$SID_NAME,

 

ora_dbwr_$SID_NAME, ora_ckpt_$SID_NAME, and ora_reco_$SID_NAME

 

($SID_NAME is the session id name of the Oracle instance). These process

 

names are contained in the variable MONITOR_PROCESSES.

 

To include other processes to be monitored, the user needs to add the names

 

of the processes to MONITOR_PROCESSES array in the toolkit configuration

 

file (haOracle.conf). For example, if Oracle archiver is enabled, then

 

archiver process name can be added to theMONITOR_PROCESSES array

 

(ora_arc0_${SID_NAME}).

Support For Oracle Database without ASM 13