Serviceguard Extension for RAC Version A.11.18 Release Notes, 2nd Edition, December 2007
Table Of Contents
- Serviceguard Extension for RAC Version A.11.18 Release Notes Second Edition
- Table1 Printing History
- Announcements
- What’s in this Version
- Support for Cluster Interconnect Subnet Monitoring
- Support for Veritas CFS and CVM
- Support for Oracle 9i RAC on CFS and CVM
- Support for Oracle 10gR2 RAC on CFS and CVM
- Support for the SGeRAC Toolkit
- Support for 8192 Oracle Server Processes for Oracle 9i RAC
- Serviceguard Extension for RAC does not support Mixed Clusters
- About Device Special Files (DSFs)
- What Manuals are Available for This Version
- Further Reading
- Compatibility Information and Installation Requirements
- Types of Releases and Patches
- Serviceguard Extension for RAC Compatibility with HP-UX and Oracle Releases
- Port Requirements
- Installing Serviceguard Extension for RAC
- Adding Serviceguard Extension for RAC to an Existing Cluster
- Removing SGeRAC
- Removing Serviceguard Extension for RAC Without Removing Serviceguard
- Troubleshooting Tips
- Patches and Fixes in this Version
- Known Problems and Workarounds
- Software Availability in Native Languages
Serviceguard Extension for RAC Version A.11.18 Release NotesKnown Problems and WorkaroundsChapter 132Known Problems and WorkaroundsThe following describes known problems for SGeRAC version A.11.18and workarounds for them. However, this is subject to change withoutnotice. For the most current information contact your HP supportrepresentative.More recent information on known problems and workarounds may beavailable 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 than3 nodes, node failed to joinWhat is the problem? In a cluster with more than 3 nodes, if 2 or morenodes restart at the same time after certain failures and then try toautomatically join the cluster (through system startup), then one of thenodes can fail to join the cluster. The cmrunnode command run by thesystem startup script will time out. The syslog file on that node willcontain messages such as:Feb 24 17:30:58 sienna syslog: /usr/sbin/cmrunnode -v ........Feb 24 17:40:19 sienna cmcld[2729]: Cluster formation failedFeb 24 17:40:19 sienna cmcld[2729]: Reason: Ran out of time forautomatically joining a clusterIn addition, one of the existing nodes in the cluster will have a messagesuch as this in syslog :Feb 24 17:31:04 milan cmcld[2729]: Detected differentconfiguration data on node siennaFeb 24 17:31:04 milan cmcld[2729]: Can not form cluster withnode siennaWhat is the workaround? Run cmrunnode from the command line on thenode which has failed to join the cluster.