* * * READ ME * * *
           * * * Veritas Oracle Disk Manager 5.0.1 RP1 * * *
                         * * * P-patch 3 * * *
                         Patch Date: 2014-04-02


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 Oracle Disk Manager 5.0.1 RP1 P-patch 3


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
HP-UX 11i v3 (11.31)


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


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas Storage Foundation 5.0.1
   * Veritas Storage Foundation Cluster File System 5.0.1
   * Veritas Storage Foundation for Oracle 5.0.1
   * Veritas Storage Foundation for Oracle RAC 5.0.1
   * Veritas Storage Foundation HA 5.0.1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: PHKL_43857
* 3425771 (2203917) The I/O performance for Oracle Disk Manager (ODM) is poor.
* 3425801 (2693010) VxFS patches to not remove formatted/cached man pages
Patch ID: PHKL_43601
* 3220484 (2444146) The Oracle Disk Manager read returns EINTR while running unspecified Oracle 
jobs.
Patch ID: PHKL_42792
* 2552880 (2051907) SxRT5.1SP1:SFCFSHA:failed to start odm
* 2608642 (2603511) ORA-00600: [ODM ERROR V-41-4-1-105-22 Invalid argument], when database is in archive log mode.


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

Patch ID: PHKL_43857

* 3425771 (Tracking ID: 2203917)

SYMPTOM:
The I/O performance for Oracle Disk Manager (ODM) is poor.

DESCRIPTION:
The I/O performance for ODM is due to a lock contention on the odm_iop_table. 
The odm_iop_table maintains a structure for each process performing I/O 
operations via ODM.

RESOLUTION:
The code is modified to increase the number of hash buckets from 32 to 256. 
This reduces the contention on the global lock.

* 3425801 (Tracking ID: 2693010)

SYMPTOM:
The formatted uncompressed files created by the catman(1M) command for Oracle
Disk Manager (ODM) man pages remain available even after the removal of the 
ODM package.

DESCRIPTION:
Currently, the formatted compressed files created by the catman(1M) command for 
ODM man pages are not removed during the removal/uninstall of patches.

RESOLUTION:
The code is modified in the postremove and preinstall/postinstall packaging 
scripts to cleanup any remaining formatted uncompressed files created by the 
catman(1M) command.

Patch ID: PHKL_43601

* 3220484 (Tracking ID: 2444146)

SYMPTOM:
The Oracle Disk Manager (ODM) read returns EINTR while running unspecified 
Oracle jobs. Oracle returns following error:

ORA-01115: IO error reading block from file 11 (block #  <block number>)
 
ORA-01110: data file 11: '/<database file>'
 
ORA-17500: ODM err:ODM ERROR V-41-4-2-281-4 Interrupted system call
 
Oracle says that ODM ERROR V-41-4-2-281-4 Interrupted system call

DESCRIPTION:
In the ODM API version 1, if Oracle specified that IO is interruptible and the 
thread is interrupted then ODM has to indicate that by setting the 
ODM_IO_POSTED flag in the status word of the request. Oracle retries the IO 
after seeing this flag in the status word. ODM did not handle this condition 
and hence returned the error. In the ODM API version 2, all IO waits are non-
interruptible.

RESOLUTION:
The code is modified to check if the IO is interruptible and set the 
appropriate kernel flag.

Patch ID: PHKL_42792

* 2552880 (Tracking ID: 2051907)

SYMPTOM:
When configuring SFCFSHA on cluster, odm module failed to load with following error.
<snip>
odm failed to start on <test_machine>
odm failed to start on <test_machine>
</snip>

DESCRIPTION:
To start odm successfully,  it require the 'VXCFS#VERITAS File System = Enabled'
in the license. 'VXCFS#VERITAS File System' feature was replaced with 'CFSODM'
feature. CPI installation is not able to find 'VXCFS#VERITAS File System' in the
license, hence odm enabling fails.

RESOLUTION:
In the ODM license checking code, we now check for "CFSODM" in addition to
"VXCFS#VERITAS File System".

* 2608642 (Tracking ID: 2603511)

SYMPTOM:
On Systems with Oracle 11.2.0.3 or higher installed, database operations can 
fail with the following message is displayed in the system logs: "ODM ERROR 
V-41-4-1-105-22 Invalid argument"

DESCRIPTION:
A change in and Oracle API in 11.2.0.3 , Oracle Disk Manager (ODM) is unable to 
create a file due to a unrecognized f-mode.

RESOLUTION:
The code is modified to mask and take into consideration only the files which 
are known to ODM instead of failing the creation of the file.



INSTALLING THE PATCH
--------------------
To install the ODM 5.0.1-RP1P3 patch:
a) The ODM 5.0.1(GA) must be installed before applying this
  patch.
b) To verify the Veritas Oracle Disk Manager level, execute:
     # swlist -l product | egrep -i 'VRTSodm'
  VRTSodm     5.0.31.5        Veritas Oracle Disk Manager
c) All prerequisite/corequisite patches must be installed. The Kernel patch
  requires a system reboot for both installation and removal.
d) To install the patch, execute the following command:
# swinstall -x autoreboot=true -s <patch_directory>   PHKL_43857
If the patch is not registered, you can register it
using the following command:
# swreg -l depot <patch_directory>  
The <patch_directory>   is the absolute path where the patch resides.


REMOVING THE PATCH
------------------
To remove the ODM 5.0.1-RP1P3 patch:
a) Execute the following command:
# swremove -x autoreboot=true PHKL_43857


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


OTHERS
------
NONE