1OCF_HEARTBEAT_IDS(7)          OCF resource agents         OCF_HEARTBEAT_IDS(7)
2
3
4

NAME

6       ocf_heartbeat_ids - Manages an Informix Dynamic Server (IDS) instance
7

SYNOPSIS

9       ids [start | stop | status | monitor | meta-data | validate-all]
10

DESCRIPTION

12       OCF resource agent to manage an IBM Informix Dynamic Server (IDS)
13       instance as an High-Availability resource.
14

SUPPORTED PARAMETERS

16       informixdir
17           The value the environment variable INFORMIXDIR has after a typical
18           installation of IDS. Or in other words: the path (without trailing
19           '/') where IDS was installed to. If this parameter is unspecified
20           the script will try to get the value from the shell environment.
21           (optional, string, no default)
22
23       informixserver
24           The value the environment variable INFORMIXSERVER has after a
25           typical installation of IDS. Or in other words: the name of the IDS
26           server instance to manage. If this parameter is unspecified the
27           script will try to get the value from the shell environment.
28           (optional, string, no default)
29
30       onconfig
31           The value the environment variable ONCONFIG has after a typical
32           installation of IDS. Or in other words: the name of the
33           configuration file for the IDS instance specified in
34           INFORMIXSERVER. The specified configuration file will be searched
35           at '/etc/'. If this parameter is unspecified the script will try to
36           get the value from the shell environment.  (optional, string, no
37           default)
38
39       dbname
40           This parameter defines which database to use in order to monitor
41           the IDS instance. If this parameter is unspecified the script will
42           use the 'sysmaster' database as a default.  (optional, string,
43           default sysmaster)
44
45       sqltestquery
46           SQL test query to run on the database specified by the parameter
47           'dbname' in order to monitor the IDS instance and determine if it's
48           functional or not. If this parameter is unspecified the script will
49           use 'SELECT COUNT(*) FROM systables;' as a default.  (optional,
50           string, default SELECT COUNT(*) FROM systables;)
51

SUPPORTED ACTIONS

53       This resource agent supports the following actions (operations):
54
55       start
56           Starts the resource. Suggested minimum timeout: 120.
57
58       stop
59           Stops the resource. Suggested minimum timeout: 120.
60
61       status
62           Performs a status check. Suggested minimum timeout: 60.
63
64       monitor
65           Performs a detailed status check. Suggested minimum timeout: 30.
66           Suggested interval: 10.
67
68       validate-all
69           Performs a validation of the resource configuration. Suggested
70           minimum timeout: 5.
71
72       meta-data
73           Retrieves resource agent metadata (internal use only). Suggested
74           minimum timeout: 5.
75
76       methods
77           Suggested minimum timeout: 5.
78
79       usage
80           Suggested minimum timeout: 5.
81

EXAMPLE

83       The following is an example configuration for a ids resource using the
84       crm(8) shell:
85
86           primitive p_ids ocf:heartbeat:ids \
87             op monitor depth="0" timeout="30" interval="10"
88

SEE ALSO

90       http://www.linux-ha.org/wiki/ids_(resource_agent)
91

AUTHOR

93       Linux-HA contributors (see the resource agent source for information
94       about individual authors)
95
96
97
98resource-agents 3.9.2             07/08/2011              OCF_HEARTBEAT_IDS(7)
Impressum