|
Problem IC88290
|
Status: Closed |
SQL0901N ERROR MAY BE RETURNED WHEN CREATING AN INDEX ON A USER-DEFINED TEMPORARY TABLE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Problem description:
A create index on a user-defined temporary table (also knows as
CGTT) may fail with the error SQL0901N.
The following example may reproduce the problem :
db2 "create user temporary tablespace ts1"
db2 "create table t1 (i1 int, i2 int)"
db2 "insert into t1 values (1,1),(2,2),(3,3)"
db2 "create global temporary table session.t2 as (select i1,i2
from t1) definition only"
db2 "insert into session.t2 values (4,4),(5,5),(6,6)"
db2 "create index session.t2_i1 on session.t2 (i1,i2)"
The last CREATE INDEX statement is where the failure may occur
and return :
SQL0901N The SQL statement failed because of a non-severe
system error. Subsequent SQL statements can be processed.
(Reason "".) SQLSTATE=58004 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 8. *
**************************************************************** |
| Local Fix: |
If possible instead of a user-defined temporary table a regular
table could be used. |
| available fix packs: |
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 8. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC88471
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.11.2012
02.04.2013
02.04.2013 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP8
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.8
|
 |
