HP Serviceguard Linux Oracle-Toolkit-A.05.01.00 User Guide (696983-001, June 2012)

ExampleDescriptionAttribute Name
Oracle configuration directory
$ASM_HOME/dbs.
When this parameter is
configured, it overrides the default
file location.
If both PFILE and SPFILE are
present and this parameter is not
specified, then HP Serviceguard
toolkit for Oracle makes use of
PFILE as the parameter file.
To make use of SPFILE in the
toolkit, do not configure this
parameter, and remove the default
PFILE from its default location.
noSet this value to no.LISTENER
If this attribute is set to no, you
must comment the
LISTENER_NAME and
oracle_listener_service
attributes. For example:
#LISTENER_NAME
The default value is yes.
This is the list of all the critical
Oracle processes for an ASM
MONITOR_PROCESSES
• ora_pmon_${SID_NAME}
• ora_dbw0_${SID_NAME}
instance that must be executing to
assume that the instance is up and
• ora_ckpt_${SID_NAME}
running. You can add more
instance processes.
• ora_smon_${SID_NAME}
• ora_lgwr_${SID_NAME}
• ora_reco_${SID_NAME}
yesThe Maintenance flag is used to
bring this toolkit into maintenance
MAINTENANCE_FLAG
mode. If set to yes then it enables
maintenance feature in the toolkit.
HP Serviceguard toolkit for Oracle
looks out for the oracle.debug
file in the Oracle package
directory where all the HP
Serviceguard toolkit for Oracle
files are located.
If the file exists and if maintenance
feature is enabled, then monitoring
is paused, the ASM or the
database instance might be
brought down for maintenance,
and package does not fail over to
the adoptive node even though the
instance is not running.
After the maintenance work,
ensure that the instance is running.
Then delete the oracle.debug
file in the package directory. This
enables the toolkit to continue
monitoring the database server
application or the ASM instance.
22 Using HP Serviceguard toolkit for Oracle