Can I configure an Oracle Dataguard standby in a Red Hat Cluster?

Environment

Red Hat Enterprise Linux 7, 8, 9 with High Availability or Resilient Storage cluster add-ons

Issue

My oracle standby database starts but it goes down immediately.

Dec  9 13:22:05 fvm-rhel-8-3-171 oracle(instance_mydb)[13357]: INFO: Oracle instance mydb started:
Dec  9 13:22:05 fvm-rhel-8-3-171 crmd[11693]:  notice: Result of start operation for instance_mydb on fvm-rhel-8-3-171: 0 (ok)

Dec  9 13:22:13 fvm-rhel-8-3-171 oracle(instance_mydb)[41217]: WARNING: Unable to login as "OCFMON", using "sysdba" user instead
Dec  9 13:22:13 fvm-rhel-8-3-171 oracle(instance_mydb)[41217]: INFO: mydb instance state is not OPEN (dbstat output: MOUNTED) 

Dec  9 13:22:13 fvm-rhel-8-3-171 oracle(instance_mydb)[41217]: ERROR: oracle instance mydb is down

Dec  9 13:22:13 fvm-rhel-8-3-171 lrmd[11690]:  notice: instance_mydb_monitor_10000:41217:stderr [ ocf-exit-reason:oracle instance mydb is down ]
Dec  9 13:22:13 fvm-rhel-8-3-171 crmd[11693]:  notice: fvm-rhel-8-3-171.local-instance_mydb_monitor_10000:71 [ ocf-exit-reason:oracle instance mydb is down\n ]

Resolution

Red Hat does not support the deployment of an Oracle Dataguard standby over a Red Hat cluster infrastructure.

Root Cause

The pacemaker resource agent used for Oracle databases only supports Oracle databases in an OPEN state. An Oracle Dataguard standby database has to be in a MOUNT state to be able to apply the archive logs that receive from the primary.

Diagnostic Steps

The database start mode will appear clearly in the cluster log files.

Dec  9 13:22:13 fvm-rhel-8-3-171 oracle(instance_mydb)[41217]: INFO: mydb instance state is not OPEN (dbstat output: **MOUNTED**) 

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.