HP Serviceguard Toolkit for Oracle Version A.05.01.01 on Linux User Guide (December, 2012)

Table 3 Lists the attributes that you can edit (continued)
ExampleDescriptionAttribute
2This parameter defines the number
of attempts to be made to restart the
LISTERNER_RESTART
listeners when a listener failure is
detected.
If the listener does not restart after
LISTENER_RESTART number of
consecutive attempts, the package
fails over. If the listener restart is
successful, then the next time listener
fails, the toolkit again tries
LISTENER_RESTART number of
times to restart the listener.
You can add more than one listener
restart value by adding to the array
variable LISTENER_RESTART.
${ORACLE_HOME}/dbs/
init${SID_NAME}.ora
The Oracle database parameter file.
If this attribute is not specified,
Oracle picks this up from the Oracle
PFILE
configuration directory
$ORACLE_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 the Oracle toolkit
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. The default value is
${ORACLE_HOME}/dbs/
init${SID_NAME}.ora.
This is the list of all the critical
Oracle processes for an instance
MONITOR_PROCESSES
• ora_pmon_${SID_NAME}
• ora_dbw0_${SID_NAME}
that must be executing to assume
that the instance is up and running.
• ora_ckpt_${SID_NAME}
You can add more instance
• ora_smon_${SID_NAME}
processes. The processes mentioned
will be monitored by default.
• 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 it enables
maintenance feature in the toolkit.
The HP Serviceguard toolkit for
Oracle looks out for the
oracle.debug file in the Oracle
package directory.
If the file exists and if the
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.
Configuring legacy and modular Oracle ASM instance and Database instance toolkit packages 19