DB2 FOR LUW / DB2FORLUW / 970 - DB2

This problem only occurs in the partitioned database 
environment. When running a SQL statement contains a VALUES 
statement which forms a set of rows, DB2 may produce the 
internal error SQL0901N with the following message in the 
db2diag.log file 
 
FUNCTION: DB2 UDB, table Q services, sqlkt_pack_tuple, probe:20 
MESSAGE : DIA0001E An internal error occurred. Report the 
following error code 
          : "Line=02412, rc1=0x82170001, rc2=0x00000000, 
rc3=(nil), 
          msg=cold=NONULLS zvalue=ISNULL ...". 
 
 
This problem can be identified by inspecting the SQL statement 
that whether it has the following characteristics: 
 
1. The VALUES statement contains more than one row. 
2. Some of the columns contain a mix of literals and the value 
NULL. 
3. The value NULL is not on the first row.

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Users                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v9.7 Fixpack 9                                    * 
****************************************************************

Move the row of the column containing the value NULL to the 
first row of the VALUES statement

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
 

Problem first fixed in v9.7 Fixpack 9

Move the row of the column containing the value NULL to the 
first row of the VALUES statement

forerunner  : APAR is sysrouted TO one or more of the following: IC91787 IC95370 IC95432 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

31.01.2013
30.12.2013
30.12.2013

9.7.FP9