* * * READ ME * * *
                       * * * InfoScale 7.4 * * *
                         * * * Patch 1300 * * *
                         Patch Date: 2021-04-07


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 1300


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


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


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * InfoScale Availability 7.4
   * InfoScale Enterprise 7.4
   * InfoScale Storage 7.4


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: VRTSamf-7.4.0.1200
* 4032036 (4001565) On Solaris 11.4, IMF fails to provide notifications when Oracle processes stop.
Patch ID: VRTSamf-7.4.0.1100
* 3970684 (3970679) Veritas Infoscale Availability does not support Oracle Solaris 11.4.
Patch ID: VRTSvcsea-7.4.0.1100
* 3956206 (3960499) Support for Oracle 18c
* 3958613 (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.
* 3980547 (3989826) The VCS agent for Oracle does not support Oracle 19c databases.
* 3982248 (3989510) The VCS agent for Oracle does not support Oracle 19c databases.


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

Patch ID: VRTSamf-7.4.0.1200

* 4032036 (Tracking ID: 4001565)

SYMPTOM:
On Solaris 11.4, IMF fails to provide notifications when Oracle processes stop.

DESCRIPTION:
On Solaris 11.4, when Oracle processes stop, IMF provides notification to Oracle agent, but the monitor is not scheduled. As as result, agent fails intelligent monitoring.

RESOLUTION:
Oracle agent now provides notifications when Oracle processes stop.

Patch ID: VRTSamf-7.4.0.1100

* 3970684 (Tracking ID: 3970679)

SYMPTOM:
Veritas Infoscale Availability does not support Oracle Solaris 11.4.

DESCRIPTION:
Veritas Infoscale Availability does not support Oracle Solaris versions later 
than 11.3.

RESOLUTION:
Veritas Infoscale Availability now supports Oracle Solaris 11.4.

Patch ID: VRTSvcsea-7.4.0.1100

* 3956206 (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.

* 3958613 (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.

* 3980547 (Tracking ID: 3989826)

SYMPTOM:
The VCS agent for Oracle does not support Oracle 19c databases.

DESCRIPTION:
The VCS agent for Oracle does not support Oracle 19c databases.

RESOLUTION:
The VCS agent for Oracle now supports Oracle 19c databases.

* 3982248 (Tracking ID: 3989510)

SYMPTOM:
The VCS agent for Oracle does not support Oracle 19c databases.

DESCRIPTION:
In case of non-CDB or CDB-only databases, the VCS agent for Oracle does not recognize that an Oracle 19c resource is intentionally offline after a graceful shutdown. This functionality is never supported for PDB-type databases.

RESOLUTION:
The agent is updated to recognize the graceful shutdown of an Oracle 19c resource as intentional offline in case of non-CDB or CDB-only databases. For details, refer to the article at: https://www.veritas.com/support/en_US/article.100046803.



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

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 [<path to this patch>] [<host1> <host2>...]

Install the patch manually:
--------------------------
Manual installation is not recommended.


REMOVING THE PATCH
------------------
Manual uninstallation is not recommended.


SPECIAL INSTRUCTIONS
--------------------
NONE


OTHERS
------
NONE