Date: 2008-08-11 OS: HP-UX OS Version: 11iv3 Packages: VRTSdbac Etrack Incidents: 1245398, 1321146, 1322433, 1322756, 1376390 Errors/Problems Fixed: PrivNIC agent fails to fail back the IP address when the first link is restored. Oracle clusterware to detect Veritas Cluster server as a vendor clusterware "linkrac 10gR2" issue for oracle 10.2.0.4 ERROR: Oracle binary not linked with Veritas IPC library spfile param instance_groups appended to SKGXN group_name overruns 18 chars "linkrac" fails with Oracle 10.2.0.4. Fixes Applied for Products: Storage Foundation for Oracle RAC Install/Uninstall Instructions: Refer Veritas Storage Foundation for Oracle RAC README (sfrac_readme.pdf) shipped along with this patch for detailed installation instructions. Additional Notes: Patch Name: PVKL_03842 Patch Description: VRTS 5.0 RP1 VRTSdbac Kernel Patch Creation Date: 08/11/2008-15:52:25 Hardware Platforms - OS Releases: 11iv3 (B11.31) Products: VRTSdbac 5.0 MP1 Filesets: PVKL_03842.DBAC-RUN, r=1.0, a=HP-UX_B.11.31_IA/PA, v=Symantec, fr=1.0, fa=HP-UX_B.11.31_IA/PA PVKL_03842.VCSMM-RUN, r=1.0, a=HP-UX_B.11.31_IA/PA, v=Symantec, fr=1.0, fa=HP-UX_B.11.31_PA PVKL_03842.VCSMM-RUN, r=1.0, a=HP-UX_B.11.31_IA/PA, v=Symantec, fr=1.0, fa=HP-UX_B.11.31_IA Automatic Reboot?: No Status: General Release Critical: Yes Category Tags: Symptoms: PVKL_03842 : (SYMANTEC Incident Number:1321146) During Oracle Clusterware installation, the Oracle installer is unable to detect Veritas Cluster Server as a vendor clusterware and waits indefinitely for a default clusterware to start. (SYMANTEC Incident Number:1322433) After installing or upgrading the Oracle Clusterware and its binaries to version 10.2.0.4, the command "linkrac 10gR2" fails with the following error message: ERROR: Oracle binary not linked with Veritas IPC library. (SYMANTEC Incident Number:1322756) Assigning long string values to the spfile parameter "instance_groups" causes the value to exceed the allocated 18 bytes of space, resulting in a BAD TRAP panic. (SYMANTEC Incident Number:1245398) Occasionally, the PrivNIC agent is unable to fail over the IP address of the second private link to the first private link that is restored. Defect Description: PVKL_03842 : (SYMANTEC Incident Number:1321146) This issue arises because you have not updated the script $CRS_HOME/css/admin/init.cssd to enable Oracle Clusterware to detect Veritas Cluster Server as a vendor clusterware. As a result, Oracle Clusterware indefinitely waits for a default clusterware to start. Resolution This issue can be resolved by making manual patch updates to the init.cssd script. However, to avoid a manual update of the script, an alternative mechanism is used. The script clsinfo is now placed in the /opt/nmapi/nmapi2/bin directory. This change ensures that Oracle automatically detects the presence of Veritas Cluster Server as a vendor clusterware. (SYMANTEC Incident Number:1322433) The library format for the shared library, libskgxp, has changed from static to dynamic format in Oracle 10.2.0.4. As a result, the linkrac script is unable to locate the shared library and fails with the error message. Resolution The linkrac script is now modified to determine the format of the shared library that must be used with the installed version of Oracle. (SYMANTEC Incident Number:1322756) When you assign a value to the spfile parameter "instance_groups", Oracle appends this value to the SKGXN group_name. If the parameter value is a long string, it may lead to a buffer overflow resulting in a BAD TRAP panic of the system. Resolution A check has now been enforced on the length of the spfile parameter "instance_groups", to ensure that even if Oracle appends the "group_name" index, the length of the parameter value is within the allocated 18 bytes of space. (SYMANTEC Incident Number:1245398) When the first private link is removed or damaged, the interface is automatically stopped and the PrivNIC agent fails over the corresponding IP address to the second private link. Later, when the first private link is restored, the PrivNIC agent tries to retrieve the IP address but is unsuccessful because the interface is non-functional. Resolution If the private IP address (configured in PrivNIC) is found on any interface with the down state, clear it. Thus the IP address can be assigned on the correct interface and can be enabled. This also protects against the private IP being configured on any other interface with down state and resulting into connection loss from the other nodes. Enhancement: No Patch Files: /opt/VRTSvcs/bin/PrivNIC/hpux_netutil.pm /opt/VRTSvcs/bin/PrivNIC/monitor /opt/VRTSvcs/ops/bin/clsinfo /opt/VRTSvcs/rac/lib/linkrac /opt/VRTSvcs/rac/lib/oramake /opt/nmapi/nmapi2/bin/clsinfo /usr/lib/libvcsmm.1 /usr/lib/libvcsmm.sl /usr/lib/pa20_64/libvcsmm.1 /usr/lib/pa20_64/libvcsmm.sl /usr/lib/hpux32/libvcsmm.1 /usr/lib/hpux32/libvcsmm.so /usr/lib/hpux64/libvcsmm.1 /usr/lib/hpux64/libvcsmm.so Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: Equivalent Patches: None Installation Instructions: Please review all instructions and the VERITAS support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. Refer Veritas Storage Foundation for Oracle RAC README (sfrac_readme.pdf) shipped along with this patch for detailed installation instructions.