home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC96391 Status: Closed

SOME XML QUERIES COULD BE IMPACTED BY PERFORMANCE ISSUE ON SOLARIS AND
HP-UX PLATFORMS.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Some memory alignment issues have been found in certain data 
structures involved in xml code which get stressed by the 
specific query. 
The alignment issue is handled differently on different 
platforms . 
Solaris and HP , handle the misalignment in software and are 
prone to performance degradation. 
This Apar will fix this memory alignment issue.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to V10.1 FP3                                  * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in V10.1 FP3
Workaround
N/A
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.09.2013
11.11.2013
11.11.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList