Install guide

5.3. RGManager Configuration

Note

At this point in the process, we have installed Oracle on a shared volume disk (i.e. SAN).

The Resource manager is required only in the HA configuration and is responsible for ensuring that the

selected node is capable of supporting an Oracle instance. T he manager must ensure that network

connectivity (provided by a Virtual IP address) is available, and mount the appropriate shared file

systems that contain the Oracle database and the Oracle product installation and finally start the Oracle

instance.

RGManager is capable of terminating Oracle services, dismantling the file systems and network so that

the other node may safely start the Oracle services. There is a sample script, oracledb.sh, found in

/usr/share/cluster. The customer must always modify this script so that RGManager can identify

the Oracle services that require cluster management. Oracle environment variables, such as

ORACLE_HOME and ORACLE_SID are critical to this identification. Oracle will likely use several file

system mount points, and all mounts that are required to successfully run the database must be made

known to RGManager.

RGManager is not enabled to start upon RHEL boot, so it must be enabled for the appropriate run level

(typically 3):

$ sudo chkconfig –level 3 rgmanager on

5.3.1. Customizing oracledb.sh Environment Variables

Here are some notes from the script’s preamble:

# (1) You can comment out the LOCKFILE declaration below. This will prevent

# the need for this script to access anything outside of the ORACLE_HOME

# path.

# (2) You MUST custom ize ORACLE_USER, ORACLE_HOME, ORACLE_SID, and

# ORACLE_HOSTNAME to match your installation if not running from within

# rgm anager.

# (3) Do NOT place this script in shared storage; place it in ORACLE_USER's

# hom e directory in non-clustered environm ents and /usr/share/cluster

# in rgmanager/Red Hat cluster environm ents.

The original script supported Oracle’s attempt at an application server (iAS), which has been replaced

by a real product, Weblogix. It is also not common to co-locate the connection pool on the database

server.

The script also attempts to start up the OEM (Oracle Enterprise Manger) console. The console is also

not generally run on server, but runs on some random Windows box, and the OEM agents are

configured on the server. If you happen to be using an older version of RHEL, the oracledb.sh script

might need to have all of this disabled, including references to these obsolete services in the start_db,

stop_db and get_db_status functions in the script.

5.3.1.1. DB_PROCNAMES

Red Hat Enterprise Linux 5 Configuration Example - Oracle HA on Cluster Suite