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-hpux1131-6.0.5.100
Sign in if you want to rate this patch.

 Basic information
Release type: Patch
Release date: 2014-09-15
OS update support: None
Technote: None
Documentation: None
Popularity: 653 viewed    164 downloaded
Download size: 7.4 MB
Checksum: 1216420497

 Applies to one or more of the following products:
Storage Foundation 6.0.1 On HP-UX 11i v3 (11.31)
Storage Foundation Cluster File System 6.0.1 On HP-UX 11i v3 (11.31)
Storage Foundation for Oracle RAC 6.0.1 On HP-UX 11i v3 (11.31)
Storage Foundation HA 6.0.1 On HP-UX 11i v3 (11.31)

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

This patch requires: Release date
sfha-hpux1131-6.0.5 2014-04-15

 Fixes the following incidents:
3142142, 3149270, 3241794, 3346108, 3516699

 Patch ID:
PVKL_04038

 Readme file  [Save As...]
                          * * * READ ME * * *
             * * * Veritas Oracle Disk Manager 6.0.5 * * *
                      * * * Patch 6.0.5.100 * * *
                         Patch Date: 2014-09-04


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 6.0.5 Patch 6.0.5.100


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


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: PVKL_04038
* 3516699 (3326358) The system panics if it accesses a block device associated with the Oracle Disk Manager (ODM)  device major number.
Patch ID: PVKL_04031
* 3142142 (3079215) Oracle RAC Database creation failed with the Ora-00600
[ksfd_odmio1] error  when Veritas ODM links.
* 3149270 (3149174) Veritas Oracle Disk Manager (ODM) clone shutdown fails with
the ORA-03113: end-of-file on communication channel error.
* 3241794 (3101418) The current time returned by the operating system (Oracle error code ORA-01513)
during Oracle startup is invalid.
* 3346108 (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: PVKL_04038

* 3516699 (Tracking ID: 3326358)

SYMPTOM:
The system panics with the following recursive stack trace:
bad_news
bubbledown
odm_strategy
io_invoke_devsw
odm_strategy
io_invoke_devsw
odm_strategy
io_invoke_devsw
...

DESCRIPTION:
If a block device is created with the same major number as the ODM device, when this device is accessed for example via the statvfsdev function, the ODM strategy routine will be invoked. The ODM device recursively searches the underlying block device associated with this major number in the device table, and then calls its strategy routine, which leads to a dead loop.

RESOLUTION:
In the ODM strategy routine, check if the block number which has been passed in is pointed to the ODM device itself.

Patch ID: PVKL_04031

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

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

* 3346108 (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
--------------------
Run the Installer script to automatically install the patch:
-----------------------------------------------------------
To install the patch perform the following steps on at least one node in the cluster:
1. Copy the hot-fix odm-hpux1131-6.0.5.100-patches.tar.gz to /tmp
2. Untar odm-hpux1131-6.0.5.100-patches.tar.gz to /tmp/hf
    # mkdir /tmp/hf
    # cd /tmp/hf
    # gunzip /tmp/odm-hpux1131-6.0.5.100-patches.tar.gz
    # tar xf /tmp/odm-hpux1131-6.0.5.100-patches.tar
3. Install the hotfix
    # pwd /tmp/hf
    # ./installODM605P1 [<host1> <host2>...]

Install the patch manually:
--------------------------
To install the ODM 6.0.500.100 patch:
a) The ODM 6.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     6.0.100.000        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>  PVKL_04038 
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 6.0.500.100 patch:
a) Execute the following command:
# swremove -x autoreboot=true PVKL_04038


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


OTHERS
------
NONE



Read and accept Terms of Service