ocf_heartbeat_ids(7)

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

SUPPORTED ACTIONS

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

EXAMPLE CRM SHELL

88       The following is an example configuration for a ids resource using the
89       crm(8) shell:
90
91           primitive p_ids ocf:heartbeat:ids \
92             op monitor depth="0" timeout="30s" interval="10s"
93

EXAMPLE PCS

95       The following is an example configuration for a ids resource using
96       pcs(8)
97
98           pcs resource create p_ids ocf:heartbeat:ids \
99             op monitor depth="0" timeout="30s" interval="10s"
100

AUTHOR

105       ClusterLabs contributors (see the resource agent source for information
106       about individual authors)
107
108
109
110resource-agents UNKNOWN           10/24/2018              OCF_HEARTBEAT_IDS(7)