Patch-ID# 104840-03 Keywords: clmon dmond udlm pdb pdbcf ccon Synopsis: Ultra Enterprise Cluster PDB 1.2 jumbo patch Date: Oct/28/97 Solaris Release: 2.5 SunOS Release: 5.5.1 Unbundled Product: Ultra Enterprise Cluster PDB Unbundled Release: 1.2 Relevant Architectures: sparc BugId's fixed with this patch: 4011161 4013948 4008077 4008506 4004844 4005519 4005981 4023331 4044313 4024729 4006500 4031927 Changes incorporated in this version: 4031927 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Files included with this patch: opt/SUNWcluster/bin/cconsole opt/SUNWcluster/bin/clustmon opt/SUNWcluster/lib/cfg_sun4uI.so.1 usr/sbin/in.mond opt/SUNWcluster/bin/pdbconf opt/SUNWcluster/bin/pdbssa opt/SUNWcluster/bin/reconf_ener opt/SUNWcluster/bin/clustd var/opt/SUNWcluster/user.scripts/TEMPLATE.user_script etc/opt/SUNWcluster/conf/TEMPLATE.cdb opt/SUNWcluster/lib/libcdb.so.1 opt/SUNWcluster/lib/libcluster.so.1 opt/SUNWcluster/lib/libudlmlib.so.1 opt/SUNWcluster/bin/ccmd opt/SUNWcluster/bin/cdbmatch opt/SUNWcluster/bin/pdbogms opt/SUNWcluster/bin/udlmctl opt/SUNWcluster/man/man1m/pdbogms.1m /usr/lib/locale/POSIX/LC_MESSAGES/SUNWcluster.mo Problem Description: Added functionality to automatically start Oracle8 Group Membership Services (GMS) as part of the node startup. 4031927 (SUNWudlm) The maximum number of file descriptors that can be open when calling fopen() must be less than 255 otherwise the fopen() call will silently fail. This is an issue when Oracle uses the cdb library interface to query cdb values for the interconnect IP addresses used by internode parallel query and there are a large number of database files in the database already opened. 4006500 (SUNWcmm) This patch contains a fix with aborting joiner nodes when max reconfigurations have happened without any change in the membership set. When any possible joiners have been aborted, if there are still max reconfig consecutive reconfigurations, it aborts the higest numbered node rather than the lowest numbered node as we used to do previously. 4011161 (SUNWclmon) If clustmon is active and both nodes are rebooted, often the display for the connections to the combo's will be corrupted. Problems include: 1) All connections show from one node only instead of both nodes cross configured (IE 2 connections to both ports of the combo from 1 node) 2) "Imaginary" combo may be shown. 3) Item display shows the internal system drives in the "imaginary" combo 4013948 (SUNWclmon) Clustmon gets a segmentation violation when "reading" configuration on a duracell cluster if a graphics card is installed. 4008077 (cconsole) This bug caused BIND errors in very occasional reconfigurations, due to a small time window that exists where bind() can fail. This leads to node abort. 4008506 (clustmon/cconsole) ccp using nisplus tables for clusters and serialports fails 4004844 (reconf_ener/TEMPLATE.user_script) The PDB_DATE variable in the user defined script is not set correctly. 4005519 (reconf_ener/pdbconf/pdbssa) When the quorum device is changed using the -q option of pdbconf when only one node is in the cluster, the reservation on the old quorum device is not released when the second node joins the cluster. This may prevent the second node from joining the cluster. 4005981 (reconf_ener/pdbconf/pdbssa) If clustmon indicates that the node joined the cluster successfully, the error message is harmless and can be ignored. If the node failed to join the cluster, there will be other errors logged in the system's console logs. The diagnosis for the failure needs to be based on these other error messages. 4023331 (SUNWclmon) Core dump (segmentation violation) occurs on the 1.2 jumbo patch level starting clustmon to a duracell with the following config 2 combos via 2 sunswift cards 2 ssa's via 1 fibercard with 2 modules interconnect via fast ethernet 4044313 (SUNWpdb) It's not possible to use a quantum 2.1GB as quorum disk in pdb1.2 4024729 (SUNWpdb) Changing quorum disk still leaves reservations outstanding after 104492-01 Patch Installation Instructions: -------------------------------- Refer to the Install.info file for instructions on using the generic 'installpatch' and 'backoutpatch' scripts provided with each patch. Any other special or non-generic installation instructions should be described below as special instructions. Special Install Instructions: ----------------------------- This patch should be installed with both Oracle and PDB stopped. The system should be rebooted after you install the patch.