* * * READ ME * * * * * * Veritas High Availability Enterprise Agents 6.2.1 * * * * * * Patch 200 * * * Patch Date: 2016-05-16 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 ---------- Veritas High Availability Enterprise Agents 6.2.1 Patch 200 OPERATING SYSTEMS SUPPORTED BY THE PATCH ---------------------------------------- SLES12 x86-64 PACKAGES AFFECTED BY THE PATCH ------------------------------ VRTSvcsea BASE PRODUCT VERSIONS FOR THE PATCH ----------------------------------- * Symantec Application HA 6.2.1 * Symantec Cluster Server 6.2.1 * Symantec Storage Foundation Cluster File System HA 6.2.1 * Symantec Storage Foundation for Oracle RAC 6.2.1 * Symantec Storage Foundation HA 6.2.1 SUMMARY OF INCIDENTS FIXED BY THE PATCH --------------------------------------- Patch ID: 6.2.1.200 * 3879170 (3879366) Extended support for all shells in oracle systemd startup script. Patch ID: 6.2.1.100 * 3871617 (3871614) With HAD in user.slice, Oracle (or applications) are not shut down gracefully during system reboot. DETAILS OF INCIDENTS FIXED BY THE PATCH --------------------------------------- This patch fixes the following Symantec incidents: Patch ID: 6.2.1.200 * 3879170 (Tracking ID: 3879366) SYMPTOM: Systemd service for oracle resource fails to start when user shell is csh DESCRIPTION: Oracle resource fails to online when the owner has csh set as default shell. The systemd service which is started during online E.P. fails to start if owner has csh set as default login shell. After a few attempts, clean is called which causes the Oracle resource to fault. RESOLUTION: Support for all types of shell used by the oracle user in systemd startup script. Patch ID: 6.2.1.100 * 3871617 (Tracking ID: 3871614) SYMPTOM: If HAD is running in the user.slice then during system reboot, Oracle (or its applications) running as a non-root user do not shut down gracefully. DESCRIPTION: On RHEL7 and SLES12, systemd is enabled. Therefore, all the processes running under user.slice are killed on system reboot. Since Oracle (or its applications) run under user.slice by default, a system reboot may cause Oracle to crash or udergo an abrupt shut down. RESOLUTION: Move the Oracle processes to system.slice to prevent them from an abrupt shut down during a system reboot. INSTALLING THE PATCH -------------------- Run the Installer script to automatically install the patch: ----------------------------------------------------------- To install the patch perform the following steps on at least one node in the cluster: 1. Copy the patch vcsea-sles12_x86_64-Patch-6.2.1.200.tar.gz to /tmp 2. Untar vcsea-sles12_x86_64-Patch-6.2.1.200.tar.gz to /tmp/hf # mkdir /tmp/hf # cd /tmp/hf # gunzip /tmp/vcsea-sles12_x86_64-Patch-6.2.1.200.tar.gz # tar xf /tmp/vcsea-sles12_x86_64-Patch-6.2.1.200.tar 3. Install the hotfix # pwd /tmp/hf # ./installVRTSvcsea621P2 [ ...] Install the patch manually: -------------------------- Perform the following steps on all nodes in the VCS cluster: 1. Take backup of your configurations. 2. Stop VCS on the cluster node. 3. Install the patch. 4. Restart VCS on the node. Stopping VCS on the cluster node -------------------------------- Perform the following steps: 1. Ensure that the "/opt/VRTSvcs/bin" directory is included in your PATH environment variable so that you can execute all the VCS commands. Refer to Veritas Cluster Server Installation Guide for more information. 2. Ensure that the VRTSvcsea package version for Linux is 6.2.1 3. Freeze all the service groups persistently. # haconf -makerw # hagrp -freeze [group] -persistent 4. Stop the cluster on all nodes. If the cluster is writable, you may close the configuration before stopping the cluster. # haconf -dump -makero From any node, execute the following command. # hastop -all or # hastop -all -force Verify that you have stopped the cluster on all nodes by entering the following command: # hasys -state After you run the command, the following output must be displayed: VCS ERROR V-16-1-10600 Cannot connect to VCS engine On all nodes, make sure that both had and hashadow processes are stopped. Also, stop the VCS CmdServer on all nodes. # CmdServer -stop Installing the Patch -------------------- Perform the following steps: 1. Un-compress the downloaded patch from Symantec. Change the directory to the uncompressed patch location. Install the VRTSvcsea patch using the following command: i. For SLES12: # rpm -Uvh VRTSvcsea-6.2.1.200-SLES12.i686.rpm 2. Run the following command to verify if the new patch has been installed: # rpm -q VRTSvcsea If the proper patch is installed, the following output is displayed: i. For SLES12: # VRTSvcsea-6.2.1.200-SLES12.i686.rpm Re-starting VCS on the cluster node ----------------------------------- 1. To start the cluster services on all cluster nodes. Execute the following command first on one node: # hastart On all the other nodes, start VCS by executing the hastart command after the first node goes to LOCAL_BUILD or RUNNING state. 2. Make VCS cluster writable. # haconf -makerw 3. Unfreeze all the groups. # hagrp -unfreeze [group] -persistent # haconf -dump -makero REMOVING THE PATCH ------------------ Removal of the patch will result in removing the entire package from the system/node. To go back to a previous installed version of the package, you may need to re-install the package. Run the following steps on all the VCS cluster nodes: To remove the patch from a cluster node: --------------------------------------------- 1. Freeze all the service groups persistently. # haconf -makerw # hagrp -freeze [group] -persistent 2. Stop VCS on the node by following the steps provided in the section "Stopping VCS on the cluster node". 3. Remove the patch by using the following command: # rpm -e VRTSvcsea 4. Verify that the patch has been removed from the system: # rpm -qa | grep VRTSvcsea Ensure that the VRTSvcsea package is not be displayed. This confirms that the package is removed. 5. Install the VRTSvcsea 6.2.1 package from the installation media. 6. To start the cluster services on all cluster nodes, execute the following command first on one node: # hastart On all the other nodes, start VCS by executing hastart after the first node goes to LOCAL_BUILD or RUNNING state. 7. Unfreeze all the groups. # hagrp -unfreeze [group] -persistent # haconf -dump -makero SPECIAL INSTRUCTIONS -------------------- NONE OTHERS ------ NONE