AutoRecover or a userApplication failover occurred because of an Oracle instance resource failure.
[Case 1]
If there is insufficient space to archive, and data updating processing through monitoring SQL hangs, an oracle resource might fail.
Afterwards, the service might stop finally on both operating node and standby node, because the space of shared disk is insufficient and the failover of userApplication fails on the standby node.
Check the Oracle database alertlog, so you might be able to detect the cause of the failure.
Also, backup archive logs then reserve enough disk space.
[Case 2]
If monitoring timeout occurs twice in a row, a resource failure will occur. If the following error message is output to syslog, you can determine the cause of this problem:
ERROR: 0226: Watch Timeout occurred
Take corrective action on Oracle.
In Oracle instance monitoring of PRIMECLUSTER Wizard for Oracle, if there is no reply from Oracle database within a specified time, monitoring timeout will be considered. At the first monitoring timeout, the resource will only enter Warning, however, if it occurs twice in a row, a resource failure will be determined.
