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

INSTANCE MAY ABEND DURING COMPILATION OF A QUERY CONTAINING IMPL ICITLY
EQUIVALENT COLUMNS AND A PREDICATE WITH AN EMPTY STRING

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
A query being compiled that has a local predicate (LOCPRD) with 
an empty string literal, i.e., '', may cause the instance to 
abend if the following conditions are satisfied: 
 
1) The column (COMPCOL) in LOCPRD is equivalent to another 
column (OTHCOL), e.g., via a join 
2) OTHCOL is also involved in a local predicate (OTHLOCPRD) 
3) LOCPRD is either an equi-join or non-equi-join predicate 
4) OTHLOCPRD is an equi-join predicate 
5) OTHCOL and COMPCOL are both string-type columns 
 
The stack trace from such an abend will look something like: 
 
sqlrxcp1 
sqlnr_seldel_test 
sqlnr_upddelpd_cond 
sqlnr_seq 
sqlnr_rcc 
sqlnr_magic_detail_action 
...
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 3 or later.              * 
****************************************************************
Local Fix:
Manually rewrite the query by adjusting the empty strings in 
the2 predicates involved to have the same length as the columns 
 they are being compared against using spaces, e.g., 
VARCHAR_4_COL = '' 
can be safely adjusted to: 
VARCHAR_4_COL = '    '
available fix packs:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 9.7 Fix Pack 3.
Workaround
See LOCAL FIX
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.08.2009
30.09.2010
30.09.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList