* * * READ ME * * *
                    * * * Database Edition 6.0 * * *
                         * * * P-patch 2 * * *
                         Patch Date: 2013-02-07


This document provides the following information:

   * PATCH NAME
   * PACKAGES AFFECTED BY THE PATCH
   * BASE PRODUCT VERSIONS FOR THE PATCH
   * OPERATING SYSTEMS SUPPORTED BY THE PATCH
   * INCIDENTS FIXED BY THE PATCH
   * INSTALLATION PRE-REQUISITES
   * INSTALLING THE PATCH
   * REMOVING THE PATCH


PATCH NAME
----------
Database Edition 6.0 P-patch 2


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSdbed


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


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


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

Patch ID: 149778-02

* 2953976 (Tracking ID: 2953973)

SYMPTOM:
use Oracle APIs to communicate with Oracle directly

DESCRIPTION:
Instead of using the perl DBI module , use the Oracle APIs to 
communicate with Oracle directly.

RESOLUTION:
-

* 3063206 (Tracking ID: 3077728)

SYMPTOM:
Sometime when creating a checkpoint an error output similar to the
following is displayed , but checkpoint gets created successfully:
$ vxsfadm -s checkpoint -a oracle -name c2 -o create
Putting database in backup mode...                           Done
Creating Storage Checkpoint c2 ...                           cannot fetch initial
working directory: No such file or directory 
Done
Storage Checkpoint c2 created
Removing the database from backup mode...                    Done

DESCRIPTION:
The problem is when removing a temporary folder created in /var/tmp
fails for a particular reason and dumps the above output. This output is now
captured and logged if the same occurs. This does not hamper the functionality in
any way

RESOLUTION:
-


INSTALLING THE PATCH
--------------------
If the patch 149778-01 is installed, please uninstall the same using
#patchrm 149778-01

For Solaris 10 releases, refer to the man pages for instructions
on using 'patchadd' and 'patchrm' scripts provided with Solaris.
Any other special or non-generic installation instructions should be
described below as special instructions.  The following example
installs a patch to a standalone machine:

        example: #patchadd /var/spool/patch/149778-02

For additional examples please see the appropriate man pages.


REMOVING THE PATCH
------------------
For Solaris 10 releases, refer to the man pages for instructions
on using 'patchadd' and 'patchrm' scripts provided with Solaris.
Any other special or non-generic installation instructions should be
described below as special instructions. The following example removes a patch from a standalone system:

        example: #patchrm 149778-02

For additional examples please see the appropriate man pages.


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


OTHERS
------
NONE