HP Serviceguard Toolkit for Oracle on Linux User Guide Version A.12.00.00

Example:
• tkit/oracle/oracle/DB_SERVICE <service1>
• tkit/oracle/oracle/DB_SERVICE <service2>
• tkit/oracle/oracle/DB_SERVICE <service3>
Support for database hang detection
You can configure a separate service that will detect the database hang and take appropriate
action. Database hang is detected by connecting to the database and checking its status. If this
process takes an unusually long time or if the toolkit is unable to retrieve the database status, then
it is assumed that the database is hung. You can configure two attributes when you configure this
service:
1. TIMEOUT: This attribute defines how long the script must wait for the database hang check
to return success. If the database health cannot be determined within this time after connecting
to the database, then it is assumed that the database is hung. It can have any positive integer
as value. The default value for TIMEOUT is 30 (seconds). This must not be confused with the
TIME_OUT package attribute or the service_halt_timeout attribute.
2. ACTION: This attribute defines the action that must be taken if a database hang is detected.
Currently, this attribute can take one of the following values:
• log - Log a message: A message is logged to the package log every time a hang is
detected. If the MONITOR_INTERVAL attribute is set to 30 seconds, then a message is
logged to the package log file every 30 seconds.
• failure - Failover the package to adoptive node.
The default value for ACTION is failure.
The syntax of the service command is as follows:
service_cmd "$SGCONF/scripts/tkit/oracle/tkit_module.sh
oracle_hang_monitor <TIMEOUT> <ACTION>"
Following is an example in which the TIMEOUT is set to 40 seconds and the ACTION is set to
failure:
service_name db_hang_check
service_cmd "$SGCONF/scripts/tkit/oracle/tkit_module.sh oracle_hang_monitor 40 failure"
service_restart none
service_fail_fast_enabled no
service_halt_timeout 300
Support for Oracle database backup mode
During the oracle database instance package start or package failover on the other cluster node,
if the database is in the online backup mode based on your input through the package attribute
DISABLE_BACKUP_MODE, the toolkit gets the database out of the backup mode. The valid values
for this parameter are yes and no. By default, the value is set to no.
For example: tkit/oracle/oracle/DISABLE_BACKUP_MODE no.
When DISABLE_BACKUP_MODE parameter is set to yes and the database is in the backup mode,
the Oracle database instance package start or failover on other node will alter the database to
remove the backup mode before starting. Also, START_MODE parameter should be set to open.
If Oracle database recovery is needed, then package fails to start with a following message in the
package log:
Unable to get the database out of the backup mode. You must get the database out of the backup
mode before starting the package. The toolkit does not take any action on database recovery.
If DISABLE_BACKUP_MODE is set to no then this feature will not be enabled.
38 Supporting Oracle features