* * * READ ME * * * * * * CPI 5.1 SP1 RP4 * * * * * * P-patch 2 * * * Patch Date: 2014-05-22 This document provides the following information: * PATCH NAME * OPERATING SYSTEMS SUPPORTED BY THE PATCH * PACKAGES AFFECTED BY THE PATCH * BASE PRODUCT VERSIONS FOR THE PATCH * SUMMARY OF INCIDENTS FIXED BY THE PATCH * DETAILS OF INCIDENTS FIXED BY THE PATCH * INSTALLATION PRE-REQUISITES * INSTALLING THE PATCH * REMOVING THE PATCH PATCH NAME ---------- CPI 5.1 SP1 RP4 P-patch 2 OPERATING SYSTEMS SUPPORTED BY THE PATCH ---------------------------------------- Solaris BASE PRODUCT VERSIONS FOR THE PATCH ----------------------------------- * Symantec VirtualStore 5.1 SP1 PR2 * Symantec VirtualStore 5.1 SP1 * Veritas Cluster Server 5.1 SP1 PR2 * Veritas Cluster Server 5.1 SP1 PR1 * Veritas Cluster Server 5.1 SP1 * Veritas Dynamic Multi-Pathing 5.1 SP1 * Veritas Dynamic Multi-Pathing 5.1 SP1 PR2 * Veritas Dynamic Multi-Pathing 5.1 SP1 PR1 * Veritas Storage Foundation 5.1 SP1 PR1 * Veritas Storage Foundation 5.1 SP1 * Veritas Storage Foundation 5.1 SP1 PR2 * Veritas Storage Foundation Cluster File System 5.1 SP1 * Veritas Storage Foundation Cluster File System 5.1 SP1 PR2 * Veritas Storage Foundation Cluster File System 5.1 SP1 PR1 * Veritas Storage Foundation Cluster File System for Oracle RAC 5.1 SP1 PR2 * Veritas Storage Foundation Cluster File System for Oracle RAC 5.1 SP1 PR1 * Veritas Storage Foundation Cluster File System for Oracle RAC 5.1 SP1 * Veritas Storage Foundation for Oracle RAC 5.1 SP1 PR2 * Veritas Storage Foundation for Oracle RAC 5.1 SP1 PR1 * Veritas Storage Foundation for Oracle RAC 5.1 SP1 * Veritas Storage Foundation HA 5.1 SP1 PR2 * Veritas Storage Foundation HA 5.1 SP1 PR1 * Veritas Storage Foundation HA 5.1 SP1 SUMMARY OF INCIDENTS FIXED BY THE PATCH --------------------------------------- Patch ID: 5.1.134.200 * 3363809 (3371456) vxconfigd get started before upgrade with -nostart option * 3512862 (3365076) The Symantec product installer failed to add nodes to the cluster correctly due to a gap in the node ID list in the /etc/llthosts file. DETAILS OF INCIDENTS FIXED BY THE PATCH --------------------------------------- This patch fixes the following Symantec incidents: Patch ID: 5.1.134.200 * 3363809 (Tracking ID: 3371456) SYMPTOM: The Symantec Product Installer attempts to start vxconfigd before upgrade, which may lead data corruption. DESCRIPTION: LUNs over 1TB in size in Volume Manager(VxVM) may encounter data corruption when upgrading to 5.1SP1 or 5.1SP1RPx. TechNote: http://www.symantec.com/business/support/index?page=content&id=TECH188018 During patch upgrade from 5.1SP1 to 5.1SP1RP4 release, the Symantec Product Installer attempts to start vxconfigd before patch upgrade, which leads data corruption. RESOLUTION: CPI provides a hot fix for customer to avoid vxconfigd get started if option '-nostart' is specified. * 3512862 (Tracking ID: 3365076) SYMPTOM: The Symantec product installer failed and reported a GAB error while adding nodes to the cluster. DESCRIPTION: For the newly added node, the node ID in the /etc/llthosts file is based on the node number, which belongs to the node before it is added. If there is a gap in the /etc/llthosts file before the node is added, then a duplicate node ID is assigned to the new node. Due to this assignment, GAB fails and adds incorrect information for the new node in the main.cf file. RESOLUTION: Assign node IDs that's not been used in /etc/llthosts to newly added nodes to avoid duplicate node IDs. INSTALLING THE PATCH -------------------- 1. Copy the hot fix CPI_5.1SP1RP4P2.pl to /tmp. 2. Run installation scripts with the hot fix via 'require' option every time. Example: ./installsfcfs -require /tmp/CPI_5.1SP1RP4P2.pl REMOVING THE PATCH ------------------ NONE KNOWN ISSUES ------------ * Tracking ID: 3512862 SYMPTOM: No Symptom Found WORKAROUND: No WorkAround Found * Tracking ID: 3363809 SYMPTOM: No Symptom Found WORKAROUND: No WorkAround Found SPECIAL INSTRUCTIONS -------------------- NONE OTHERS ------ NONE