Veritas Cluster Server Release Notes

Veritas Cluster Server Release Notes
Known issues
45
If secure and non-secure WAC are connected the engine_A.log
receives logs every 5 seconds [2653695]
Two WACs in GCO must always be started either in secure or non-secure mode.
The secure and non-secure WAC connections cause log messages to be sent to
engine_A.log file.
Workaround: Make sure that WAC is running in either secure mode or non-secure
mode on both the clusters in GCO.
Oracle group fails to come online if Fire Drill group is online
on secondary cluster [2653695]
If a parallel global service group faults on the local cluster and does not find a
failover target in the local cluster, it tries to failover the service group to the remote
cluster. However, if the firedrill for the service group is online on a remote cluster,
offline local dependency is violated and the global service group is not able to
failover to the remote cluster.
Workaround: Offline the Firedrill service group and online the service group on a
remote cluster.
Service group may fail to come online after a flush and a force
flush operation [2616779]
A service group may fail to come online after flush and force flush operations are
executed on a service group where offline operation was not successful.
Workaround: If the offline operation is not successful then use the force flush
commands instead of the normal flush operation. If a normal flush operation is
already executed then to start the service group use -any option.
Elevated TargetCount prevents the online of a service group
with hagrp -online -sys command [2871892]
When you initiate an offline of a service group and before the offline is complete,
if you initiate a forced flush, the offline of the service group which was initiated
earlier is treated as a fault. As start bits of the resources are already cleared, service
group goes to OFFLINE|FAULTED state but TargetCount remains elevated.
Workaround: No workaround.