GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages
OCF_HEARTBEAT_DB2(7) OCF resource agents OCF_HEARTBEAT_DB2(7)

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.

db2 [start | stop | monitor | promote | demote | meta-data | validate-all]

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)

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")

This resource agent supports the following actions (operations):
start
Starts the resource. Suggested minimum timeout: 120s.
stop
Stops the resource. Suggested minimum timeout: 120s.
promote
Promotes the resource to the Master role. Suggested minimum timeout: 120s.
demote
Demotes the resource to the Slave role. Suggested minimum timeout: 120s.
notify
Suggested minimum timeout: 10s.
monitor
Performs a detailed status check. Suggested minimum timeout: 60s. Suggested interval: 20s.
monitor (Master role)
Performs a detailed status check. Suggested minimum timeout: 60s. Suggested interval: 22s.
validate-all
Performs a validation of the resource configuration. Suggested minimum timeout: 5s.
meta-data
Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5s.

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="60s" interval="20s" \
  op monitor depth="0" timeout="60s" role="Master" interval="22s" 
ms ms_db2 p_db2 \
  meta notify="true" interleave="true"

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="60s" interval="20s" \
  op monitor depth="0" timeout="60s" role="Master" interval="22s" --master

http://clusterlabs.org/

ClusterLabs contributors (see the resource agent source for information about individual authors)
01/01/2019 resource-agents UNKNOWN

Search for    or go to Top of page |  Section 7 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.