ocf: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.
OCF_RESKEY_instance=string [OCF_RESKEY_dblist=string] [OCF_RESKEY_admin=string] [OCF_RESKEY_dbpartitionnum=string] db2 [start | stop | promote | demote | notify | monitor | monitor | validate-all | meta-data]
Resource Agent that manages an IBM DB2 LUW databases in Standard role as primitive or in HADR roles in master/slave configuration. Multiple partitions are supported. 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)
The instance of the database(s).
List of databases to be managed, e.g "db1 db2". Defaults to all databases in the instance. Specify one db for HADR mode.
DEPRECATED: The admin user of the instance.
The number of the partion (DBPARTITIONNUM) to be managed.