This page lists publically-released patches for Veritas Enterprise Products.
For Product GA build, see Veritas Entitlement Management System(VEMS) by clicking the Veritas Support 'Licensing' option.
For information on private patches, contact Veritas Technical Support.
Veritas is making it easier to find all software installers and updates for Veritas products with a completely redesigned experience. NetBackup HotFixes, NetBackup Appliance patches and APTARE IT Analytics patches are now also available at the new Veritas Download Center.
Patches for your product can have a variety of names. These names are based on product, component, or package names. For more information on patch naming conventions and the relationship between products, components, and packages, see the SORT online help.
vcsea-sol11_sparc-Patch-7.3.1.100
Sign in if you want to rate this patch.

 Basic information
Release type: Patch
Release date: 2019-01-14
OS update support: None
Technote: None
Documentation: None
Popularity: 342 viewed    36 downloaded
Download size: 1.67 MB
Checksum: 3606770215

 Applies to one or more of the following products:
InfoScale Availability 7.3.1 On Solaris 11 SPARC
InfoScale Enterprise 7.3.1 On Solaris 11 SPARC

 Obsolete patches, incompatibilities, superseded patches, or other requirements:
None.

 Fixes the following incidents:
3959872, 3960354, 3960502, 3965684

 Patch ID:
VRTSvcsea-7.3.1.100

 Readme file  [Save As...]
                          * * * READ ME * * *
     * * * Veritas High Availability Enterprise Agents 7.3.1 * * *
                         * * * Patch 100 * * *
                         Patch Date: 2019-01-11


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 7.3.1 Patch 100


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
Solaris 11 SPARC


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSvcsea


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * InfoScale Availability 7.3.1
   * InfoScale Enterprise 7.3.1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 7.3.1.100
* 3959872 (3959871) The VCS agents for Oracle do not work as expected with the changes in commands and in behavior from Oracle 12.1.0.2 onwards.
* 3960354 (3960353) An ASMInst resource fails to come online when the ocssd.bin process is not running.
* 3960502 (3960499) Support for Oracle 18c
* 3965684 (3931460) The Cluster Server component creates some required files in 
the /tmp and /var/tmp directories.


DETAILS OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
This patch fixes the following incidents:

Patch ID: 7.3.1.100

* 3959872 (Tracking ID: 3959871)

SYMPTOM:
The VCS agents for Oracle do not work as expected with the changes in commands and in behavior from Oracle 12.1.0.2 onwards.

DESCRIPTION:
From 12.1.0.2 onwards, Oracle does not let you modify ora.* resources by using the crsctl command. Instead, you can only use the srvctl command to modify ora.* resources. (For details, refer to the Oracle Doc ID 2016160.1.)

By default, AUTO_START is set to "restore", which does not fit the requirements for ASMInst monitoring. To manage ASM instances through the ASMInst resource type, the AUTO_START attribute must be set to "never". This lets VCS independently manage ASM resources and avoid conflicts with Oracle settings.

$ crsctl stat res ora.asm -p |grep AUTO_START
AUTO_START=restore

Also, the command to modify AUTO_START attribute fails and displays the following error:

$ crsctl modify resource "ora.asm" -attr "AUTO_START=never"
CRS-4995: The command 'Modify resource' is invalid in crsctl. Use srvctl for this command.

Instead, Oracle now mandates the use of "srvctl disable asm".

RESOLUTION:
The hotfix updates the agent to support the changes in Oracle 12.1.0.2 or later. As a prerequisite, you must use the following command, instead of the "crsctl modify resource "ora.asm" -attr "AUTO_START=never"" command that is mentioned in the "Cluster Server Agent for Oracle Installation and Configuration Guide".

$ srvctl disable asm
$ srvctl status asm -detail
ASM is not running.
ASM is disabled.

The agent enables or disables the ora.asm resource internally with each function of the ASMInst and the ASMDG resource types.

* 3960354 (Tracking ID: 3960353)

SYMPTOM:
An ASMInst resource fails to come online when the ocssd.bin process is not running. The following error is logged: "VCS ERROR V-16-20002-244 ASMInst:asminst:online:Cluster Synchronization Service process is not running"

DESCRIPTION:
The ASMInst agent monitors the ora.asm resource and its related processes. During the online operation of the ASMInst agent, the ora.asm resource is brought online by using either of the following options:
- SQL startup options: STARTUP, STARTUP_MOUNT, or STARTUP_OPEN
- srvctl startup option: SRVCTLSTART, SRVCTLSTART_MOUNT, SRVCTLSTART_OPEN
defined in the StartUpOpt attribute.
When the Oracle High Availability Services daemon (ohasd) is stopped by using the 'crsctl stop has' command, it stops all the parent resources, including ora.cssd. However, when ohasd is started by using the 'crsctl start has' command, it does not start the ora.cssd. For ASMInst resource to come online, the ora.cssd must be started, otherwise, the agent reports the ASMInst resource status as offline.

RESOLUTION:
The ASMInst agent is modified to bring ora.cssd online as part of its online function. The SQL query to start ASM returns an error if ocssd.bin is not running. The only way to start ASM along with ora.cssd (ocssd.bin) is to use the 'srvctl start asm' command. If ora.cssd is not running and an SQL option (STARTUP, STARTUP_MOUNT, or STARTUP_OPEN) is provided as part of StartUpOpt attribute, the modified agent maps the StartUpOpt option to its srvctl alternative. Thus, if ora.cssd is not running, the agent always uses the srvctl options internally to start the process.

* 3960502 (Tracking ID: 3960499)

SYMPTOM:
InfoScale did not support Oracle 18c.

DESCRIPTION:
Need to add support for Oracle 18c.

RESOLUTION:
This patch provides support for Oracle 18c with InfoScale.

* 3965684 (Tracking ID: 3931460)

SYMPTOM:
The Cluster Server component creates some required files in the /tmp 
and /var/tmp directories.

DESCRIPTION:
The Cluster Server component creates some required files in the 
/tmp and /var/tmp directories. Non-root users have access to these folders, 
and they may accidentally modify, move, or delete these files. Such actions 
may interfere with the normal functioning of Cluster Server.

RESOLUTION:
This hotfix addresses the issue by moving the required Cluster 
Server files to secure locations.



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 vcsea-sol11_sparc-Patch-7.3.1.100.tar.gz to /tmp
2. Untar vcsea-sol11_sparc-Patch-7.3.1.100.tar.gz to /tmp/hf
    # mkdir /tmp/hf
    # cd /tmp/hf
    # gunzip /tmp/vcsea-sol11_sparc-Patch-7.3.1.100.tar.gz
    # tar xf /tmp/vcsea-sol11_sparc-Patch-7.3.1.100.tar
3. Install the hotfix(Please be noted that the installation of this P-Patch will cause downtime.)
    # pwd /tmp/hf
    # ./installVRTSvcsea731P100 [<host1> <host2>...]

You can also install this patch together with 7.3.1 maintenance release using Install Bundles
1. Download this patch and extract it to a directory
2. Change to the Veritas InfoScale 7.3.1 directory and invoke the installmr script
   with -patch_path option where -patch_path should point to the patch directory
    # ./installmr -patch_path [<path to this patch>] [<host1> <host2>...]

Install the patch manually:
--------------------------
To apply the patch manually, perform the steps listed below on each node.
Ensure that the "/opt/VRTS/bin" directory is included in your PATH environment variable.
 1. Stop VCS:
    # haconf -dump -makero
    # hastop -local -force
 2. Apply the patch by issuing the following commands:
   a. Set the publisher
        # pkg set-publisher -p <patch_file_pathname>    Veritas
      e.g:
        # pkg set-publisher -p /hotfix_dir/patches/VRTSvcsea.p5p Veritas
   b. Install the package
        # pkg install --accept --no-backup-be VRTSvcsea
 3. Verify that the new package is installed.  The output of the following
    command should display the version for VRTSvcsea package as 7.3.1.100:
   # pkg info VRTSvcsea
 4. Unset the publisher:
   # pkg unset-publisher Veritas
 5. Start VCS:
   # hastart


REMOVING THE PATCH
------------------
Note:  Uninstalling this patch will remove the entire VRTSvcsea package. If you need
 an earlier version of the package, re-install it from original source media (ref. step 3 below).
Run the following steps on all the nodes in the VCS cluster:
 1. Stop VCS:
    # haconf -dump -makero
    # hastop -local -force
 2. Uninstall the VRTSvcsea package:
   a. If you have local zones on the system, uninstall the VRTSvcsea package  from all local zones in which it is present (repeat with <zonename>    set to each local zone in which VRTSvcsea is installed):
        # zlogin <zonename>     pkg uninstall VRTSvcsea
   b. Once the package is uninstalled from all local zones, uninstall the VRTSvcsea package from the global zone:
        # pkg uninstall VRTSvcsea
 3. (optional) Install the previous version of the VRTSvcsea package from original source media to revert your system to pre-patch conditions.
 4. Start VCS:
   # hastart


SPECIAL INSTRUCTIONS
--------------------
Note: If a local zone is in 'configured' state while the VRTSvcsea package is being updated, then the package is not updated in local zone. To update the packages inside a local zone, set the publisher on the global zone and execute the below command (repeat per zone as needed):
# zoneadm -z <zonename>    attach -u


OTHERS
------
NONE



Read and accept Terms of Service