* * * READ ME * * *
      * * * Veritas Storage Foundation for Oracle RAC 6.0.1 * * *
                      * * * Public Hot Fix 1 * * *
                         Patch Date: 2013-09-13


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 Storage Foundation for Oracle RAC 6.0.1 Public Hot Fix 1


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


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSdbac


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas Storage Foundation for Oracle RAC 6.0.1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 6.0.100.100
* 3302221 (3302091) Could not up vcs after reboot first node in phase upgrade on solaris 11 sparc


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

Patch ID: 6.0.100.100

* 3302221 (Tracking ID: 3302091)

SYMPTOM:
On Solaris 11, VCS/SFRAC is unable to start after reboot.

DESCRIPTION:
The fencing module is unable to start because the add_drv command 
from the fencing init script failed. The command failed because another module's 
add_drv command was running at the same time. This can happen to any VCS/SFRAC 
kernel module as these modules call the add_drv command in their respective init 
scripts. If different modules call the add_drv command at the same time, it 
causes 
a race condition.

RESOLUTION:
To resolve this, two new Service Management Facility (SMF) services 
have been created for simulating the post-install and pre-remove operations. The 
add_drv/rem_drv command has been moved out of the start/stop script and moved in 
to the post-install/pre-remove operation respectively. These changes have been 
made for the VRTSllt, VRTSgab, VRTSvxfen, and VRTSdbac packages.



INSTALLING THE PATCH
--------------------
Before installing VRTSdbac p-patch on a Solaris 11 host, you can optionally create a boot environment (BE) and install VRTSdbac 6.0.100.100 p-patch on the new BE.  Doing this makes it easier to revert to the current version of VRTSdbac if required in future.

To create a new boot environment, perform steps 1-4 below on each node.

1. Identify the active boot environment (BE) by looking at the NR tag:
        # beadm list

2. Create a new boot environment:
        # beadm create <new_BE_name>    

    where <new_BE_name>     is any valid name not listed in step 1.
    Example:
        # beadm create sfrac_vcsmm

3. Activate the newly-created boot environment:
        # beadm activate <new_BE_name>    

4. Reboot the node so that the new boot environment is active:
        # reboot

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

1. Save the configuration:
        # haconf -dump

2. Stop vcsmm:
        # hastop -local
        # svcadm disable -s vcsmm
        

3. Apply the VRTSdbac patch by issuing the following commands:

   a. Set the publisher
        # pkg set-publisher -p <patch_file_pathname>      Symantec
      e.g:
        # pkg set-publisher -p /hotfix_dir/patches/VRTSdbac.p5p  Symantec

   b. Install the package
        # pkg install --accept VRTSdbac
4. Verify that the new patch is installed.  The output of the following command should display the version for VRTSdbac package as 6.0.100.100:
        # pkg info VRTSdbac

5. Start vcsmm :
        # svcadm enable -s vcsmm
       
        # hastart
    etc.


REMOVING THE PATCH
------------------
On Solaris 11, patch removal is not supported.  If you created a new boot environment before installing the new VRTSdbac package, you can revert to the boot environment which was in effect prior to that installation.

 *  To revert to previous boot environment, perform steps 1-3 below on each cluster node.

 1. Activate the boot environment which was in effect prior to installing this patch (noted in step 1 of 'To create a new boot environment' above):
        # beadm activate <prev_BE_name>    

 2. Reboot the node so that the new boot environment takes effect:
        # reboot

 3. (optional) If you have no further use for the boot environment on which you installed the patch, you may destroy it:
        # beadm destroy <new_BE_name>    

    Example:
        # beadm destroy sfrac_vcsmm

If you did not create a new boot environment, you must uninstall the version of VRTSdbac included in this patch and then re-install the prior version of the package (6.0.100.0) from original source media.


SPECIAL INSTRUCTIONS
--------------------
You need to install VRTSllt-6.0.300.100, VRTSgab-6.0.300.200 and VRTSvxfen-6.0.300.100 patches with this patch. Start vcsmm service after llt and gab services are up.


OTHERS
------
NONE