* * * READ ME * * * * * * InfoScale 7.4 * * * * * * Patch 1100 * * * Patch Date: 2018-07-02 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 ---------- InfoScale 7.4 Patch 1100 OPERATING SYSTEMS SUPPORTED BY THE PATCH ---------------------------------------- AIX PACKAGES AFFECTED BY THE PATCH ------------------------------ VRTSodm VRTSvxfs VRTSvxvm BASE PRODUCT VERSIONS FOR THE PATCH ----------------------------------- * InfoScale Enterprise 7.4 * InfoScale Foundation 7.4 * InfoScale Storage 7.4 SUMMARY OF INCIDENTS FIXED BY THE PATCH --------------------------------------- Patch ID: VRTSodm-7.4.0.1100 * 3953235 (3953233) After installing the 7.4.0.1100 (on AIX and Solaris) and 7.4.0.1200 (on Linux) patch, the Oracle Disk Management (ODM) module fails to load. Patch ID: VRTSvxvm-7.4.0.1100 * 3949322 (3944259) The vradmin verifydata and vradmin ibc commands fail on private diskgroups with Lost connection error. * 3950578 (3953241) Messages in syslog are seen with message string "0000" for VxVM module. Patch ID: VRTSvxfs-7.4.0.1100 * 3950740 (3953165) Messages in syslog are seen with message string "0000" for VxFS module. DETAILS OF INCIDENTS FIXED BY THE PATCH --------------------------------------- This patch fixes the following incidents: Patch ID: VRTSodm-7.4.0.1100 * 3953235 (Tracking ID: 3953233) SYMPTOM: After installing the 7.4.0.1100 (on AIX and Solaris) and 7.4.0.1200 (on Linux) patch, the Oracle Disk Management (ODM) module fails to load. DESCRIPTION: As part of the 7.4.0.1100 (on AIX and Solaris) and 7.4.0.1200 (on Linux) patch, the VxFS version has been updated to 7.4.0.1200. Because of the VxFS version update, the ODM module needs to be repackaged due to an internal dependency on VxFS version. RESOLUTION: As part of this fix, the ODM module has been repackaged to support the updated VxFS version. Patch ID: VRTSvxvm-7.4.0.1100 * 3949322 (Tracking ID: 3944259) SYMPTOM: The vradmin verifydata and vradmin ibc commands fail on private diskgroups with Lost connection error. DESCRIPTION: This issue occurs because of a deadlock between the IBC mechanism and the ongoing I/Os on the secondary RVG. IBC mechanism expects I/O transfer to secondary in a sequential order, however to improve performance I/Os are now written in parallel. The mismatch in IBC behavior causes a deadlock and the vradmin verifydata and vradmin ibc fail due to time out error. RESOLUTION: As a part of this fix, IBC behavior is now improved such that it now considers parallel and possible out-of-sequence I/O writes to the secondary. * 3950578 (Tracking ID: 3953241) SYMPTOM: Customer may get generic message or warning in syslog with string as "vxvm:0000: " instead of uniquely numbered message id for VxVM module. DESCRIPTION: Few syslog messages introduced in InfoScale 7.4 release were not given unique message number to identify correct places in the product where they are originated. Instead they are marked with common message identification number "0000". RESOLUTION: This patch fixes syslog messages generated by VxVM module, containing "0000" as the message string and provides them with a unique numbering. Patch ID: VRTSvxfs-7.4.0.1100 * 3950740 (Tracking ID: 3953165) SYMPTOM: Customer may get generic message or warning in syslog with string as "vxfs:0000:" instead of uniquely numbered message id for VxFS module. DESCRIPTION: Few syslog messages introduced in InfoScale 7.4 release were not given unique message number to identify correct places in the product where they are originated. Instead they are marked with common message identification number "0000". RESOLUTION: This patch fixes syslog messages generated by VxFS module, containing "0000" as the message string and provides them with a unique numbering. INSTALLING THE PATCH -------------------- Run the Installer script to automatically install the patch: ----------------------------------------------------------- Please be noted that the installation of this P-Patch will cause downtime. To install the patch perform the following steps on at least one node in the cluster: 1. Copy the patch infoscale-aix71-Patch-7.4.0.1100.tar.gz to /tmp 2. Untar infoscale-aix71-Patch-7.4.0.1100.tar.gz to /tmp/hf # mkdir /tmp/hf # cd /tmp/hf # gunzip /tmp/infoscale-aix71-Patch-7.4.0.1100.tar.gz # tar xf /tmp/infoscale-aix71-Patch-7.4.0.1100.tar 3. Install the hotfix(Please be noted that the installation of this P-Patch will cause downtime.) # pwd /tmp/hf # ./installVRTSinfoscale740P1100 [ ...] You can also install this patch together with 7.4 base release using Install Bundles 1. Download this patch and extract it to a directory 2. Change to the Veritas InfoScale 7.4 directory and invoke the installer script with -patch_path option where -patch_path should point to the patch directory # ./installer -patch_path [] [ ...] Install the patch manually: -------------------------- Manual installation is not recommended. REMOVING THE PATCH ------------------ Run the Uninstaller script to automatically remove the patch: ------------------------------------------------------------ To uninstall the patch perform the following step on at least one node in the cluster: # /opt/VRTS/install/uninstallVRTSinfoscale740P1100 [ ...] Remove the patch manually: ------------------------- Manual uninstallation is not recommended. SPECIAL INSTRUCTIONS -------------------- NONE OTHERS ------ NONE