|
Problem IC95370
|
Status: Closed |
VALUES STATEMENT CONTAINING THE VALUE NULL MIGHT RETURN SQL901N IN THE PARTITIONED DATABASE ENVIRONMENT |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 UDB Users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB v10.5 Fixpak 3 *
**************************************************************** |
| Local Fix: |
Move the row of the column containing the value NULL to the
first row of the VALUES statement |
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Problem First Fixed In DB2 UDB v10.5 Fixpak 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.08.2013
10.03.2014
10.03.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
