ocf_heartbeat_db2 (7) - Linux Manuals
ocf_heartbeat_db2: Resource Agent that manages an IBM DB2 LUW databases in Standard role as primitive or in HADR roles as master/slave configuration. Multiple partitions are supported.
NAME
ocf_heartbeat_db2 - Resource Agent that manages an IBM DB2 LUW databases in Standard role as primitive or in HADR roles as master/slave configuration. Multiple partitions are supported.
SYNOPSIS
- db2 [start | stop | monitor | promote | demote | meta-data | validate-all]
DESCRIPTION
Standard mode:
An instance including all or selected databases is made highly available. Configure each partition as a separate primitive resource.
HADR mode:
A single database in HADR configuration is made highly available by automating takeover operations. Configure a master / slave resource with notifications enabled and an additional monitoring operation with role "Master".
In case of HADR be very deliberate in specifying intervals/timeouts. The detection of a failure including promote must complete within HADR_PEER_WINDOW.
In addition to honoring requirements for crash recovery etc. for your specific database use the following relations as guidance:
"monitor interval" < HADR_PEER_WINDOW - (appr 30 sec)
"promote timeout" < HADR_PEER_WINDOW + (appr 20 sec)
For further information and examples consult http://www.linux-ha.org/wiki/db2_(resource_agent)
SUPPORTED PARAMETERS
instance
-
The instance of the database(s).
(unique, required, string, no default)
dblist
-
List of databases to be managed, e.g "db1 db2". Defaults to all databases in the instance. Specify one db for HADR mode.
(optional, string, no default)
admin
-
DEPRECATED: The admin user of the instance.
(optional, string, no default)
dbpartitionnum
-
The number of the partion (DBPARTITIONNUM) to be managed.
(optional, string, default "0")
SUPPORTED ACTIONS
This resource agent supports the following actions (operations):
start
- Starts the resource. Suggested minimum timeout: 120.
stop
- Stops the resource. Suggested minimum timeout: 120.
promote
- Promotes the resource to the Master role. Suggested minimum timeout: 120.
demote
- Demotes the resource to the Slave role. Suggested minimum timeout: 120.
notify
- Suggested minimum timeout: 10.
monitor
- Performs a detailed status check. Suggested minimum timeout: 60. Suggested interval: 20.
monitor (Master role)
- Performs a detailed status check. Suggested minimum timeout: 60. Suggested interval: 22.
validate-all
- Performs a validation of the resource configuration. Suggested minimum timeout: 5.
meta-data
- Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5.
EXAMPLE CRM SHELL
The following is an example configuration for a db2 resource using the crm(8) shell:
-
primitive p_db2 ocf:heartbeat:db2 \ params \ instance=string \ op monitor depth="0" timeout="60" interval="20" \ op monitor depth="0" timeout="60" role="Master" interval="22"
-
ms ms_db2 p_db2 \ meta notify="true" interleave="true"
EXAMPLE PCS
The following is an example configuration for a db2 resource using pcs(8)
-
pcs resource create p_db2 ocf:heartbeat:db2 \ instance=string \ op monitor depth="0" timeout="60" interval="20" \ op monitor depth="0" timeout="60" role="Master" interval="22" --master
AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors)