Veritas Cluster Server Release Notes

Veritas Cluster Server Release Notes
Known issues
54
Intentional Offline does not work for VCS agent for Oracle
[1805719]
Due to issues with health check monitoring, Intentional Offline does not work for
VCS agent for Oracle.
No health check monitoring for Oracle agent on SLES11
platform [1919203]
Oracle agent does not support health check monitoring on SLES11 platform.
The ASMInstAgent does not support having pfile/spfile for the
ASM Instance on the ASM diskgroups
The ASMInstAgent does not support having pfile/spfile for the ASM Instance on
the ASM diskgroups.
Workaround:
Have a copy of the pfile/spfile in the default $GRID_HOME/dbs directory to make sure
that this would be picked up during the ASM Instance startup.
VCS agent for ASM: Health check monitoring is not supported
for ASMInst agent
The ASMInst agent does not support health check monitoring.
Workaround: Set the MonitorOption attribute to 0.
NOFAILOVER action specified for certain Oracle errors
The Veritas High Availability agent for Oracle provides enhanced handling of Oracle
errors encountered during detailed monitoring. The agent uses the reference file
oraerror.dat, which consists of a list of Oracle errors and the actions to be taken.
See the Veritas Cluster Server Agent for Oracle Installation and Configuration Guide
for a description of the actions.
Currently, the reference file specifies the NOFAILOVER action when the following
Oracle errors are encountered:
ORA-00061, ORA-02726, ORA-6108, ORA-06114
The NOFAILOVER action means that the agent sets the resource’s state to OFFLINE
and freezes the service group. You may stop the agent, edit the oraerror.dat file,
and change the NOFAILOVER action to another action that is appropriate for your
environment. The changes go into effect when you restart the agent.