OCF_HEARTBEAT_IDS(7)

💖 OCF_HEARTBEAT_IDS 💖

okay bestie, welcome to the OCF_HEARTBEAT_IDS(7) page — yes, that's a section 7 manual page from the OCF resource agents collection, and we're about to make it make sense 🫶

---

✨ NAME ✨

ocf_heartbeat_ids — manages an Informix Dynamic Server (IDS) instance. that's the whole vibe. it's the resource agent that babysits your IDS instance so your cluster can ✨do its thing✨

---

🌸 SYNOPSIS 🌸

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

---

🦋 DESCRIPTION 🦋

so like, this is an OCF resource agent whose whole job is managing an IBM Informix Dynamic Server (IDS) instance as an High-Availability resource. one instance, one agent, infinite loyalty fr fr 💅

---

👑 SUPPORTED PARAMETERS 👑

these are the knobs you can turn, bestie. turn them wisely 🌈

• informixdir — this is the value the environment variable INFORMIXDIR has after a typical install of IDS. or, to say it like a normal person: the path (with no trailing '/', ok, don't do it) where IDS was installed. if you don't set this param, the script will try to grab the value from the shell environment instead.

(optional, string, no default)

• informixserver — the value the environment variable INFORMIXSERVER has after a typical IDS install. aka the name of the IDS server instance you wanna manage. leave it unset and the script goes looking in the shell environment.

(optional, string, no default)

• onconfig — the value the environment variable ONCONFIG has after a typical IDS install. translation: the name of the config file for the IDS instance named in INFORMIXSERVER. the config file you name here gets searched for at '/etc/'. and yeah, if it's unspecified the script will try to pull it from the shell environment.

(optional, string, no default)

• dbname — which database to use for monitoring the IDS instance. not specified? the script just uses the 'sysmaster' database as the default. iconic default behavior honestly ✨

(optional, string, default "sysmaster")

• sqltestquery — the SQL test query that gets run against the database named by the 'dbname' param, to monitor the IDS instance and figure out if it's functional or not. unspecified means it defaults to 'SELECT COUNT(*) FROM systables;'.

(optional, string, default "SELECT COUNT(*) FROM systables;")

---

🔥 SUPPORTED ACTIONS 🔥

this resource agent supports these actions (operations), and every single one of them has a suggested minimum timeout, so listen up 🎀

• start — starts the resource. suggested minimum timeout: 120s.
• stop — stops the resource. suggested minimum timeout: 120s.
• status — performs a status check. suggested minimum timeout: 60s.
• monitor — performs a detailed status check. suggested minimum timeout: 30s. suggested interval: 10s.
• validate-all — performs a validation of the resource configuration. suggested minimum timeout: 5s.
• meta-data — retrieves resource agent metadata (internal use only, so don't go poking at it unless you know what you're doing 👀). suggested minimum timeout: 5s.
• methods — suggested minimum timeout: 5s.
• usage — suggested minimum timeout: 5s.

---

🎀 EXAMPLE CRM SHELL 🎀

here's what a ids resource config looks like using the crm(8) shell. screenshot this, bestie 📸

primitive p_ids ocf:heartbeat:ids \
  op monitor depth="0" timeout="30s" interval="10s"

---

💜 EXAMPLE PCS 💜

and here's the same energy using pcs(8):

pcs resource create p_ids ocf:heartbeat:ids \
  op monitor OCF_CHECK_LEVEL="0" timeout="30s" interval="10s"

---

🌈 SEE ALSO 🌈

http://clusterlabs.org/ — go forth and read, iykyk 💖

---

🧚 AUTHOR 🧚

ClusterLabs contributors — and if you're curious about individual authors, the resource agent source has all the receipts (see the resource agent source for information about individual authors).

---

that's the whole page, no cap. every param, every action, every timeout, every example — all accounted for 💅

---

and that's a wrap, bestie 🫶 this lil masterpiece is from resource-agents UNKNOWN, dated 04/08/2026 — go slay your cluster, mwah 💋✨