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 IC65784 Status: Closed

SYSTEM MODULE ROUTINE DBMS_LOB.COMPARE() WITH INVALID OFFSET ARG UMENT MAY
INCORRECTLY RETURN A RESULT INSTEAD OF GIVING SQL0138.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The system module routine DBMS_LOB.COMPARE(...) is used to 
compare two large objects.  An optional argument to the routine 
is to provide a offset for either of the input large objects to 
use as the starting point for the comparison. 
If the user inputs an offset value that is larger than the 
length of 
the input large object, then this is invalid input and an 
SQL0138 should be returned.  However, because of this defect, it 
may not detect this situation and instead the routine would 
return a -1,0, or 1 return code. 
 
The fix for the issue will ensure that SQL0138 is properly given 
if the input argument for the offset exceeds the length of the 
input large object.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users Affected: All                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Problem description:SYSTEM MODULE ROUTINE DBMS_LOB.COMPARE() * 
* WITH INVALID OFFSETARGUMENT MAY INCORRECTLY RETURN A RESULT  * 
* INSTEAD OF GIVINGSQL0138.                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* install v97 fp2                                              * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
fix contained in v97fp2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.01.2010
12.07.2010
12.07.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList