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

SQL0901N REASON "PROBE 015 IN SQLKT_PACK_TUPLE(), MSG=INVALID LEN.CLEN(X)
OR STORAGELEN" WHEN CREATING AN INDEX

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
$ db2 "CREATE INDEX TEXTI ON DB2INST1.SAMPLE(C1)"
DB21034E  The command was processed as an SQL statement because
it was not a valid Command Line Processor command.  During SQL
processing it returned:
SQL0901N  The SQL statement failed because of a non-severe
system error. Subsequent SQL statements can be processed.
(Reason "probe 015 in sqlkt_pack_tuple(), msg=Invalid
len.clen(9) or storageLen".) SQLSTATE=58004

The problem only happens when the DB2_RUNTIME_DEBUG_FLAGS
registry variable is set to 1.

The problem may also happen when querying a table which
triggers index recreation.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to the latest fixpack of DB2 V10.1, V10.5 or V11.1.  *
****************************************************************
Local Fix:
Unset DB2_RUNTIME_DEBUG_FLAGS registry variable, recycle the
instance, and retry the failing command.
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : 
follow-up : IT15687 IT15688 IT21721 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
16.05.2016
01.03.2017
01.03.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)