* * * READ ME * * *
                 * * * Oracle Disk Manager 6.0.3 * * *
                      * * * Public Hot Fix 1 * * *
                         Patch Date: 2013-09-17


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
----------
Oracle Disk Manager 6.0.3 Public Hot Fix 1


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
RHEL5 x86-64
RHEL6 x86-64
SLES10 x86-64
SLES11 x86-64


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSodm


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas Storage Foundation for Oracle RAC 6.0.1
   * Veritas Storage Foundation Cluster File System 6.0.1
   * Veritas Storage Foundation 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
* 3142142 (3079215) Oracle RAC Database creation failed with Ora-00600
[ksfd_odmio1] error  when Veritas ODM linked.
* 3142252 (3142045) With Oracle 12c version , ODM version mismatch issue observed.
* 3149270 (3149174) ODM clone shutdown is fails with error "ORA-03113: end-of-file
on communication channel"
* 3241794 (3101418) Oracle during startup displays ORA-01513 errors.


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

Patch ID: 6.0.300.100

* 3142142 (Tracking ID: 3079215)

SYMPTOM:
Oracle RAC Database creation failed with Ora-00600 [ksfd_odmio1] error 
when Veritas ODM linked.

DESCRIPTION:
Earlier ODM interface provides a context pointer which is returned 
to oracle by odm_init()
and then passed back to ODM by oracle with each interface call, here ODM 
interface just keeping
track of whether we are running oracle (>10GR2 or not)
In Oracle 12, introduced/started using multiple contexts from the same process, 
but currently
our implementation of odm library is not set up multithreaded which  doesn't 
hadle this which causing the EBADF(Bad file descriptor).

RESOLUTION:
Introduced new changes to support multiple contexts per process.

* 3142252 (Tracking ID: 3142045)

SYMPTOM:
With Oracle 12c version, Veritas ODM library give version mismatch issue

DESCRIPTION:
Each process/task, calling ODM ioctl, has exit hook which scan VMA of 
process/task for valid libodm library. VMA of process/task contains libodm.so 
text section. Exit hook compares the VMA's libodm library names with hard-coded 
library names such as libodm9.so, libodm10.so etc. Some of the new Oracle 
versions might have conflicting hard-coded names with its predecessor, such as 
12c. And the conflicting names fail the check on the existence of libodm in VMA.

RESOLUTION:
To avoid this issue, library name comparison is now done with valid 'libodm' 
pattern instead of hard-coded library name.

* 3149270 (Tracking ID: 3149174)

SYMPTOM:
ODM clone shutdown is failing with error "ORA-03113: end-of-file on 
communication channel"

DESCRIPTION:
odm_fini() which generally releases the memory allocated for the 
context and any other memory structure that have not yet been freed, can be 
called multiple times.Here odm_fini() being called twice with the same context 
which causes the problem

RESOLUTION:
Before freeing, clear the pid field of the context structure to 
avoid double freeing if odm_fini is called by mistake again with same context

* 3241794 (Tracking ID: 3101418)

SYMPTOM:
The invalid current time is returned by the operating system (Oracle error code 
ORA-01513) during Oracle startup.

DESCRIPTION:
Oracle intercepts calls to the localtime_r() function as it is not asynchronous 
signal safe. They do not support any client library to spawn a thread and call 
the localtime_r() function. The localtime_r() function is called from the 
feature_tracking library as a part of the odm_discover() function in VRTSodm.

RESOLUTION:
The code is modified so that it does not spawn the thread and call the 
localtime_r() function, while feature_tracking.



INSTALLING THE PATCH
--------------------
Before installing the patch, the SF/SFHA/SFCFS/SFRAC stack have to be at the 6.0.3 level.
Please refer to this appnote at http://www.symantec.com/docs/TECH210620 for detailed instructions/dependencies before installing this patch.
RHEL5
# rpm -Uvh VRTSodm-6.0.300.100-RHEL5.x86_64.rpm
RHEL6
# rpm -Uvh VRTSodm-6.0.300.100-RHEL6.x86_64.rpm
SLES10
# rpm -Uvh VRTSodm-6.0.300.100-SLES10.x86_64.rpm
SLES11
# rpm -Uvh VRTSodm-6.0.300.100-SLES11.x86_64.rpm


REMOVING THE PATCH
------------------
# rpm -e rpm-name


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


OTHERS
------
NONE