DB2 - Problem description
Problem IC96122 | Status: Closed |
EXPLAINING AN SQL STATEMENT ACCESSING COLUMN-ORGANIZED TABLES IN"RECOMMEND INDEXES" EXPLAIN MODE CAN RESULT IN SQL0901N | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
When explaining an SQL statement that accesses a column-organized table in "RECOMMEND INDEXES" explain mode, a SQL0901N error message with reason "Column number out of range" can be returned. Indexes are not supported on column-organized tables but a SQL0217W warning should be returned instead of the SQL0901N error along with no index recommendation. Example : db2 "CREATE TABLE CO (F1 INTEGER) ORGANIZE BY COLUMN" DB20000I The SQL command completed successfully. $ db2 SET CURRENT EXPLAIN MODE RECOMMEND INDEXES DB20000I The SQL command completed successfully. $ db2 "SELECT F1 FROM CO WHERE F1=1" SQL0901N The SQL statement or command failed because of a database system error. (Reason "column number out of range".) SQLSTATE=58004 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users executing the index advisor or using the RECOMMEND * * INDEXES explain mode with column organized tables * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.5 Fix Pack 4 * **************************************************************** | |
Local Fix: | |
Creation of indexes on column organized tables is not supported. A workaround is to avoid recommending indexes on queries accessing column organized tables until the DB2LUW instance can be upgraded to version 10.5 fixPack 3 where the fix for this APAR is provided. | |
available fix packs: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 20.09.2013 19.09.2014 19.09.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.4 |