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 NotesWhat’s in this VersionChapter 116Support for 8192 Oracle Server Processes for Oracle9i RACThe maximum number of Oracle server processes cmgmsd can handle is8192. When there are more than 8192 server processes connected tocmgmsd, it will start to reject new requests. Oracle foreground serverprocesses are needed to handle the requests of the Data Base (DB) clientconnected to the DB instance.Serviceguard Extension for RAC does not supportMixed ClustersFor SGeRAC, the nodes in the cluster must be on the same architecture.SGeRAC does not support clusters containing mixed architectural nodes,which consist of HP 9000 and HP Integrity servers, or differentoperating system releases.About Device Special Files (DSFs)HP-UX releases up to and including 11i v2 use a naming convention fordevice files that encodes their hardware path. For example, a device filenamed /dev/dsk/c3t15d0 would indicate SCSI controller instance 3,SCSI target 15, and SCSI LUN 0. HP-UX 11i v3 introduces a newnomenclature for device files, known as agile addressing (sometimes alsocalled persistent LUN binding). Under the agile addressing convention,the hardware path name is no longer encoded in a storage device’s name;instead, each device file name reflects a unique instance number, forexample /dev/[r]disk/disk3, that does not need to change when thehardware path does.Agile addressing is the default on new 11i v3 installations, but the I/Osubsystem still recognizes pre-11i v3 device files, which as of 11i v3 arereferred to as legacy device files. Device files using the newnomenclature are called persistent device files, When you upgrade toHP-UX 11i v3, a set of new, persistent device files is created, but theexisting, legacy device files are left intact and by default will continue tobe used by HP-UX and Serviceguard.