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

Table 5 List of Attributes Supported for Online Toolkit Package Modification (continued)
DescriptionAttribute
during online modification. Database service must be
configured and running during online modification, so that
toolkit package can use the start or stop control on user
defined database services.
Oracle Toolkit supports the online modification of this
attribute. This parameter is used to disable the Oracle
DISABLE_BACKUP_MODE
database from the backup mode. The valid values for this
parameter are yes and no. By default, the value is set to
no. This means, if the database is in the backup mode
after package failover or restart, the Oracle toolkit package
fails to start. You have to manually get the database out
of the backup mode and then start the package.
When the value of DISABLE_BACKUP_MODE is set to yes
and the database is in the backup mode after failover or
restart, the Oracle toolkit package will alter the database
to remove the backup mode and start the database. The
database is altered to remove the backup mode only if
START_MODE is set to open.
Oracle Toolkit supports online modification of this attribute.
This parameter is used to provide email addresses for the
email_id
toolkit alert notification recipients. Each email_id
parameter can have one of the following values:
• A complete email address
• An alias
• A distribution list
You can list multiple recipients by repeating the email_id
field and address. Toolkit sends an alert email on listener
and package failure. If configured, the alert mail is sent
for Oracle database hang detection. For example:
$SGCONF/scripts/tkit/oracle/tkit_module.sh
oracle_hang_monitor 30 alert. By default,
email_id is commented.
Oracle Toolkit supports the online modification of service
attributes. By default, three monitoring services are started.
Monitoring service attributes
Services can be added, changed, or removed depending
on monitoring requirements.
To perform online package modification:
1. While package is up and running, retrieve the current package configuration values using
the command cmgetconf.
For example: #cmgetconf -p <<Toolkit_Package_Name>> <<Latest_Toolkit_Conf_File>>
2. Backup this latest configuration file using a copy utility. This allows you to refer to the previous
configuration values.
For example: # cp -p <<Latest_Toolkit_Conf_File>> <<Backup_Toolkig_Conf_File>>
3. Edit the <<Latest_Toolkit_Conf_File>> file to modify the required attribute values.
4. Use the cmcheckconf command to verify the package configuration file.
For example: #cmcheckconf –P <<Latest_Toolkit_Conf_File>>
5. Use the cmapplyconf command to add the new changes in the package configuration to
the Serviceguard cluster environment.
For example: #cmapplyconf –P <<Latest_Toolkit_Conf_File>>
NOTE: Information related to package reconfiguration is logged in the package log.
Managing a package 47