Serviceguard Extension for RAC Version A.11.18 Release Notes, 5th Edition, October 2008

another kill signal. This allows the client more time to
process the signal and exit before another kill signal is sent.
For SGeRAC Version A.11.17 requires patch PHSS_33838.
Defect Number Problem and Resolution
SR:8606435963 (JAGaf94337)
Problem: cmgmsd killed itself and brought node down.
Resolution: Changed the source code not to process the
group member if the de-registration of this group member
is successful.
For SGeRAC Version A.11.17 requires patch PHSS_33838.
Defect Number Problem and Resolution
SR:8606427015 (JAGaf86496)
Problem: skgxnqgrp does not return correctly.
Resolution: Changed the source code to return an empty
bitmap if the specified group is not found.
For SGeRAC Version A.11.17 requires patch PHSS_33838.
Defect Number Problem and Resolution
SR:8606453198 (JAGag09971)
Problem: errors when /etc/cmcluster’s file system
becomes full (SGeRAC installations only). When the file
system where /etc/cmcluster resides became full when
Serviceguard Extension for RAC was running, and Oracle
software was trying to request a group membership
change, messages such as the following appeared in
syslog:
cmgmsd[1997]: Unable to apply the configuration change due to
insufficient disk space. cmgmsd[1997]:
ERROR: commit_cdb_txn: Failed to commit transaction (28, No space
left on device) This could ultimately lead to various Oracle
failures.
Resolution: cmgmsd transactions no longer fail if there is
not enough disk space to write them to the binary
configuration file. An error is written to syslogbut the
transaction completes, preventing Oracle errors. The
transaction is written to disk on nodes which have enough
space.
SGeRAC Version A.11.17 requires Serviceguard patch
PHSS_35371.
Known Problems and Workarounds
The following describes known problems for SGeRAC version A.11.18 and workarounds for
them. However, this is subject to change without notice. For the most current information contact
your HP support representative.
More recent information on known problems and workarounds may be available on the Hewlett
Packard IT Resource Center:
http://itrc.hp.com(Americas and Asia Pacific)
http://europe.itrc.hp.com (Europe)
JAGag33099 (SR860678856): In a cluster of more than 3 nodes, node failed to
join
What is the problem? In a cluster with more than 3 nodes, if 2 or more nodes restart at the same
time after certain failures and then try to automatically join the cluster (through system startup),
Known Problems and Workarounds 21