This page lists publically-released patches for Veritas Enterprise Products.
For Product GA build, see Veritas Entitlement Management System(VEMS) by clicking the Veritas Support 'Licensing' option.
For information on private patches, contact Veritas Technical Support.
Veritas is making it easier to find all software installers and updates for Veritas products with a completely redesigned experience. NetBackup HotFixes and NetBackup Appliance patches are now also available at the new Veritas Download Center.
Patches for your product can have a variety of names. These names are based on product, component, or package names. For more information on patch naming conventions and the relationship between products, components, and packages, see the SORT online help.
odm-hpux1123-5.0MP2RP3
Sign in if you want to rate this patch.

 Basic information
Release type: Rolling Patch
Release date: 2013-11-22
OS update support: None
Technote: None
Documentation: None
Popularity: 744 viewed    7 downloaded
Download size: 501.77 KB
Checksum: 426322491

 Applies to one or more of the following products:
Storage Foundation Cluster File System 5.0MP2 On HP-UX 11i v2 (11.23)
Storage Foundation for Oracle 5.0MP2 On HP-UX 11i v2 (11.23)
Storage Foundation for Oracle RAC 5.0MP2 On HP-UX 11i v2 (11.23)

 Obsolete patches, incompatibilities, superseded patches, or other requirements:

This patch supersedes the following patches: Release date
odm-hpux1123-5.0MP2RP2 (obsolete) 2012-09-03

This patch requires: Release date
5.0 MP1a 2007-05-29

 Fixes the following incidents:
2800073, 3326485, 3330684

 Patch ID:
PHKL_43745

 Readme file  [Save As...]
                          * * * READ ME * * *
                * * * Oracle Disk Manager 5.0 MP2 * * *
                      * * * Rolling Patch 3 * * *
                         Patch Date: 2013-11-22


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 MP2 Rolling Patch 3


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
HP-UX 11i v2 (11.23)


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


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


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: PHKL_43745
* 3326485 (2444146) The Oracle Disk Manager read returns EINTR while running unspecified Oracle 
jobs.
* 3330684 (2203917) The I/O performance for Oracle Disk Manager (ODM) is poor.
Patch ID: PHKL_43106
* 2800073 (1903999) panic in panic at as_nubcopy from volkio_to_kio_copy


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

Patch ID: PHKL_43745

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

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

Patch ID: PHKL_43106

* 2800073 (Tracking ID: 1903999)

SYMPTOM:
On a system with Oracle Disk Manager (ODM) installed, when a write
request is served, the system can panic with the following stack trace:
as_nubcopy+0x601
lbcopy+0x200
privlbcopy+0x50
volkio_to_kio_copy+0x38
volsio_unstabilize+0x19
vol_mv_wrback_done+0xdc
voliod_iohandle+0xb0
voliod_loop+0x650
kthread_daemon_startup+0x40

DESCRIPTION:
The flags passed by ODM to the Virtual Memory Manager (VMM) layer
are incorrect. Therefore, when a read request is received by VMM from the File
System (FS) or ODM, VMM tries to copy the Kernel Input Output (KIO) buffer,
created by VMM, to the user buffer. When VMM tries to write to the user
buffer, which receives information from the FS or the ODM layer, the FS or the
ODM layer that have the READ_ONLY permission cannot be written to VMM. This
results in the panic.

RESOLUTION:
The code is modified such that the flags passed by ODM to the VMM
layer are correct.



INSTALLING THE PATCH
--------------------
1. To install the ODM 5.0-MP2RP3 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.01.00           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_43745

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

a) Execute the following command:

# swremove -x autoreboot=true PHKL_43745


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


OTHERS
------
NONE



Read and accept Terms of Service