* * * READ ME * * *
               * * * Veritas Cluster Server 6.0.300 * * *
                      * * * 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 6.0.300 Public Hot Fix 1


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


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: 6.0.300.100
* 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: 6.0.300.100

* 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 install the patch package 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 package 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. Apply the patch by using the following command:

a. Set the publisher
    # pkg set-publisher -p <location of the patch_file>   Symantec
    e.g: # pkg set-publisher -p /patch_location/VRTSvcsea.p5p Symantec

b. Install the package
    # pkg install --accept --no-backup-be VRTSvcsea

4. Verify that the new patch is installed:
    The output of the following command should display the version for VRTSvcsea package as 6.0.300.100 
    # pkg info VRTSvcsea

5. Start VCS:
    # hastart


REMOVING THE PATCH
------------------
Note:  Uninstalling the patch will remove the entire package.  If you need
an earlier version of the package, install it from the original source media.

To uninstall the patch package, perform the following steps on all nodes
in the VCS cluster.

1. Save the VCS configuration:
    # haconf -dump

2. Stop VCS:
    # hastop -local -force

3. Uninstall the VRTSvcsea package:

Note: Uninstalling the patch will remove the entire package. If you need earlier version of the package, install it from the original source media.

a. Uninstall the package from within the local zone using the below command if you have zones running on the system.
    local# pkg uninstall VRTSvcsea

b. Once the package is uninstalled from the local zones, uninstall the package from the global zone using same command.
    global# pkg uninstall VRTSvcsea


SPECIAL INSTRUCTIONS
--------------------
1. This patch is applicable for Solaris 11 U1 and later versions of the OS.

2. Note: If the 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 the local zone use the following command:
    # zoneadm -z <zone_name>   attach -u


OTHERS
------
NONE