Install guide

There has been some debate over what constitutes a running instance and RGManager uses a list of
Oracle background processes (daemons in unix) to test for their existence. Historically, PMON and
SMON are the most frequently selected and they are a good set. PMON is the Process Monitor part of
the instance, and mostly cleans out latches and locks left by dead processes. It does dead process
detection, including the death of critical background process like LGWR (redo log writer), DBWR
(database writer), including SMON (system monitor). It is SMON’s job to make sure the instance is in a
healthy state. If SMON crashes for some reason, then PMON will kill the instance. T he presence of both
of these is a reasonable test.
5.3.1.2. LSNR_PROCNAME
The SQL*Net Network Listener must be running for clients running on other machines to connect to the
instance. The database can be accessed on the server node with the use of a Listener. Some instances
that don’t need client access (like batch ETL, or extremely security sensitive instances), do not have to
run a Listener. Most conventional databases with a mid-tier connection pool need a listener, so
RGManager ensures that the Listener is up and running. T he lack of a Listener will look like a dead
database to the mid-tier.
5.3.2. Network VIP for Oracle Listeners
The Oracle SQL*Net Listener service must listen on a common IP address that must be accessible from
either host, and this is accomplished using a Virtual IP, or VIP.
# ip addr add 192.168.1.20/24 dev eth0
The VIP is managed and relocated by rgm anager, and must be in the same submit as the public, or
front-side physical network interfaces. The front-side network is the network the Listener uses, and
clients will also have access.
<rm log_level="7">
<service dom ain="OracleHA" autostart=”1 exclusive=”1 name=oracle11g
recovery=relocate”>
<oracledb home="/ff/11g/db" name="ed" type="11g" user="jneedham "
vhost="192.168.1.60"/>
<ip address="192.168.1.60" />
<fs device...
<rm/>
Alternatively, you can use a hostname for the virtual IP:
edb home="/ff/11g/db" name="ed" type="11g" user="jneedham " vhost="hacf-vip"/>
<ip address="hacf-vip" />
The vhost argument must match the IP address clause in the service domain definition, and the
/etc/hosts file must contain all the required addresses:
Chapter 5. Cold Failover Cluster Configuration
39