* * * READ ME * * *
              * * * Veritas Oracle Disk Manager 5.0 * * *
                      * * * Rolling Patch 6 * * *
                         Patch Date: 2016-06-27


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 Rolling Patch 6


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 Cluster File System 5.0
   * Veritas Storage Foundation for Oracle 5.0
   * Veritas Storage Foundation for Oracle RAC 5.0


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: PHKL_44460
* 2609130 (2603511) On systems with Oracle 11.2.0.3 or higher installed, database operations can 
fail.
* 3876446 (2693010) Formatted uncompressed files created by the catman(1M) 
command for the Veritas Oracle Disk Manager (VRTSodm) man pages are available 
even after 
VRTSodm package is removed.
Patch ID: PHKL_43683
* 3277006 (2444146) The Oracle Disk Manager read returns EINTR while running unspecified Oracle 
jobs.


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

Patch ID: PHKL_44460

* 2609130 (Tracking ID: 2603511)

SYMPTOM:
On systems with Oracle 11.2.0.3 or higher installed, database operations
fails with the following message in the system log:
 "ODM ERROR V-41-4-1-105-22 Invalid argument"

DESCRIPTION:
A change in the 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 fmode and take into consideration only the files,
which 
are known to ODM. As a result, the files are now created.

* 3876446 (Tracking ID: 2693010)

SYMPTOM:
Formatted uncompressed files created by the catman(1M) command for the Veritas 
Oracle Disk Manager (VRTSodm) man pages are available even after the VRTSodm 
package is removed.

DESCRIPTION:
When removal or uninstall of patches is done, the formatted compressed files, 
which are
created by the catman(1M) command for VRTSodm man pages are not removed.

RESOLUTION:
To cleanup any remaining formatted uncompressed files created by the 
catman(1M) command, the code is modified in the post remove, and preinstall or 
post install packaging 
scripts.

Patch ID: PHKL_43683

* 3277006 (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.



INSTALLING THE PATCH
--------------------
To install the ODM 5.0-RP6 patch:
a) The ODM 5.0(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.0
       Veritas Oracle Disk Manager
c) All prerequisite/corequisite patches must be installed. The Kernel patch  req
uires a system reboot for both installation and removal.
d) To install the patch, execute the following command:# s
winstall -x autoreboot=true -s <patch_directory>    PHKL_44460 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-RP6 patch:
a) Execute the following command:# swremove -x autoreboot=true PHKL_44460


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


OTHERS
------
NONE