* * * READ ME * * *
               * * * Oracle Disk Manager 5.0.1RP1P2 * * *
                          * * * P-patch * * *
                         Patch Date: 2013-08-20


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 5.0.1RP1P2 P-patch


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 File System 5.0.1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
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_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-RP1P2 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_43601

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-RP1P2 patch:

a) Execute the following command:

# swremove -x autoreboot=true PHKL_43601


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


OTHERS
------
NONE