OCF_HEARTBEAT_SYBASE(7)

💅 ocf_heartbeat_sybaseASE — it's giving failover realness

okay bestie, so this is ocf_heartbeat_sybaseASE, and it lives in the OCF_HEARTBEAT_SYBASE(7) manual page. it's a resource agent, which is basically the little choreographer that makes your Sybase ASE database do the failover dance when the cluster says so 🩰

---

✨ NAME ✨

ocf_heartbeat_sybaseASE — Sybase ASE Failover Instance. yes, the title says it all, no notes 💖

---

🌸 SYNOPSIS 🌸

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

that's the whole vibe. six actions, pick your fighter 🎀

---

🦋 DESCRIPTION 🦋

Sybase ASE Failover Instance.

lowkey that's the entire description the original gives us and i am not about to invent lore, so: it's a Sybase ASE failover instance. periodt. 👑

---

💖 SUPPORTED PARAMETERS 💖

these are the knobs you can turn. turn them correctly, bestie, or the cluster will simply not have a good time 🙈

• sybase_home — the home directory where all your sybase products live. it's optional, it's a string, and its default is "detect" (yes, she detects it herself, main character energy ✨)
• sybase_ase — the directory name under sybase_home where the ASE products are installed. optional, string, default "detect" 🎀
• sybase_ocs — the directory name under sybase_home where the OCS products are installed, i.e. ASE-15_0. optional, string, default "detect" 🦋
• server_name — the ASE server name that's configured for the HA service. this one is unique, required, a string, and has no default. so like. you have to set it. no skipping 💅
• interfaces_file — the full path of the interfaces file, the one used to start/access the ASE server. optional, string, default "detect/interfaces" 🌸
• sybase_user — the user who can run the ASE server. optional, string, default "sybase" 🫶
• db_user — the database user you need to log in to isql. required, string, no default. mandatory, bestie, mandatory 😤
• db_passwd — the database user's password, also needed to log in to isql. optional, string, and it has no default 🔐
• logfile — Logfile. optional, string, default "detect" 📓

---

🔥 SUPPORTED ACTIONS 🔥

This resource agent supports the following actions (operations). here's the whole roster, with the timeouts and intervals attached, because numbers matter and i would never fudge them 💯

• start — Starts the resource. Suggested minimum timeout: 300s.
• stop — Stops the resource. Suggested minimum timeout: 300s.
• status — Performs a status check. Suggested minimum timeout: 100s. Suggested interval: 30s.
• monitor — Performs a detailed status check. Suggested minimum timeout: 100s. Suggested interval: 30s.
• status — Performs a status check. Suggested minimum timeout: 100s. Suggested interval: 120s.
• monitor — Performs a detailed status check. Suggested minimum timeout: 100s. Suggested interval: 120s.
• meta-data — Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5s.
• validate-all — Performs a validation of the resource configuration. Suggested minimum timeout: 5s.

ngl, you clocked that status and monitor each show up twice with different intervals? that's not a typo on my part, bestie, that's literally what the page says. 30s and 120s versions of both. iconic of it, honestly 💀

---

🌈 EXAMPLE CRM SHELL 🌈

here's what it looks like when you configure a sybaseASE resource with the crm(8) shell:

primitive p_sybaseASE ocf:heartbeat:sybaseASE \
  params \
    server_name=string \
    db_user=string \
  op monitor interval="30s" timeout="100s" \
  op monitor depth="10" timeout="100s" interval="120s"

look at her. all configured. so demure 🎀

---

⭐ EXAMPLE PCS ⭐

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

pcs resource create p_sybaseASE ocf:heartbeat:sybaseASE \
  server_name=string \
  db_user=string \
  op monitor interval="30s" timeout="100s" \
  op monitor OCF_CHECK_LEVEL="10" timeout="100s" interval="120s"

heads up, the pcs version uses OCF_CHECK_LEVEL="10" while the crm shell version above uses depth="10" — that's exactly how the original has it, so don't come for me, i'm just the messenger 🫶

---

👀 SEE ALSO 👀

• http://clusterlabs.org/

that's the link. go read it. iykyk 🌐

---

🫶 AUTHOR 🫶

ClusterLabs contributors (see the resource agent source for information about individual authors). love that for them, honestly, they ate 💜

---

and that's the page!! this was resource-agents version UNKNOWN, dated 04/08/2026. no cap. slay, go configure your failover instance bestie 💅✨🎀