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 and NetBackup Appliance 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.
vcs-sol10_x64-VRTSvcsea-6.0.3.100
Obsolete
The latest patch(es) : sfha-sol10_x64-6.0.5 
Sign in if you want to rate this patch.

 Basic information
Release type: Patch
Release date: 2013-03-12
OS update support: None
Technote: None
Documentation: None
Popularity: 821 viewed    74 downloaded
Download size: 3.86 MB
Checksum: 713271624

 Applies to one or more of the following products:
VirtualStore 6.0.1 On Solaris 10 X64
Cluster Server 6.0.1 On Solaris 10 X64
Storage Foundation Cluster File System 6.0.1 On Solaris 10 X64
Storage Foundation for Oracle RAC 6.0.1 On Solaris 10 X64
Storage Foundation HA 6.0.1 On Solaris 10 X64

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

This patch is obsolete. It is superseded by: Release date
sfha-sol10_x64-6.0.5 2014-04-15

This patch requires: Release date
sfha-sol10_x64-6.0.3 (obsolete) 2013-02-01

 Fixes the following incidents:
3088925

 Patch ID:
149793-01

 Readme file  [Save As...]
                          * * * READ ME * * *
           * * * Veritas Cluster Server VRTSvcsea-6.0.3 * * *
                      * * * Public Hot Fix 1 * * *
                         Patch Date: 2013-03-12


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 Cluster Server VRTSvcsea-6.0.3 Public Hot Fix 1


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
Solaris 10 X86


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


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas Cluster Server 6.0.1
   * Veritas Storage Foundation for Oracle RAC 6.0.1
   * Veritas Storage Foundation Cluster File System 6.0.1
   * Veritas Storage Foundation High Availability 6.0.1
   * Symantec VirtualStore 6.0.1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 149793-01
* 3088925 (3088915) After upgrade from VCS 6.0.1 to 6.0.3, Oracle resource is unable to come online in the container. Monitor fails to detect the processes.


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

Patch ID: 149793-01

* 3088925 (Tracking ID: 3088915)

SYMPTOM:
Veritas Cluster Server (VCS) reports the status of Oracle resources configured 
inside the container (Solaris local zone or AIX WPAR) as OFFLINE even when 
Oracle processes are running inside the container. Following message logged 
in /var/VRTSvcs/log/Oracle_A.log file:

VCS DBG_4 V-16-50-0 Oracle:resource_name:monitor:Container id [0] of input 
process [ora_smon_SID] did not match with container id [1] of system process 
[ora_smon_SID]

DESCRIPTION:
VCS Oracle agent uses common process library (ProcLib) for process level 
monitoring. In VCS 6.0.3 release, a check was introduced in ProcLib to match 
the container ID of the input process with the container ID of the processes 
running in the system.
The Oracle agent did not send the container ID of the container in which the 
resource is configured to the ProcLib for exact match which caused this issue.

RESOLUTION:
Symantec has updated the Oracle agent to send the container ID information to 
the ProcLib for exact process match. With this fix, Oracle agent can correctly 
match the Oracle processes running inside the container.



INSTALLING THE PATCH
--------------------
Prerequisite:
    The target system(s) should have VRTSvcsea 6.0.300.000-GA installed 
    before the installation of this patch.

The VRTSvcsea-6.0.300.100 patch may be installed either manually (see below)
or using the included installer.

 *  To apply the patch using the installer, enter the commands 
        # cd <hotfix_directory>  && ./installVCSEA603P1  [ <node1> <node2>... ]
    
    where 
      <hotfix_directory>
                is the directory where you unpacked this hotfix
      <node1>, <node2>, ...
                are the nodes to be patched.  If none are specified, you
                will be prompted to enter them interactively.  All nodes
                must belong to a single cluster.
    
    For information about installer options, run  './installVCSEA603P1 -help'.
    

 *  To apply the patch manually, perform the steps listed below on each node 
    in the VCS cluster.

 1. Save the VCS configuration:
        # haconf -dump 

 2. Stop VCS:
        # hastop -local -force 

 3. Install the patch by issuing the following commands:
   a. Change to the appropriate directory where patch is present.

   b. Apply patch as:
        # patchadd 149793-01 

 4. To verify that the patch was successfully applied, compare the output 
    from the following command with the sample output below:
        # showrev -p | grep 149793-01 

    The following output is displayed if the patch is installed successfully:

    Patch: 149793-01 Obsoletes:  Requires: 149693-01 Incompatibles:  Packages: VRTSvcsea
    

 5. Start VCS:
        # hastart


REMOVING THE PATCH
------------------
If you installed the patch using the installer, you may either use the patch 
uninstall script which was created at that time, or use manual methods to 
uninstall the patch.

 *  To remove the patch using the patch uninstall script, enter the command 
        # /opt/VRTS/install/uninstallVCSEA603P1  [ <node1> <node2>... ] 
    

 *  To manually remove the patch, run the following steps on all the nodes 
    in the VCS cluster.

 1. Save the VCS configuration:
        # haconf -dump 

 2. Stop VCS:
        # hastop -local -force 

 3. Uninstall the patch:
        # patchrm 149793-01 

 4. Verify that the patch is uninstalled from the node:
        # showrev -p | grep 149793-01 
    
    If the patch is successfully uninstalled, there will be no output.

 5. Start VCS:
        # hastart


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


OTHERS
------
NONE



Read and accept Terms of Service