home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC82547 Status: Closed

ERROR, "INVALID INDEXCOLNAMES" WHILE RUNNING NNSTAT OR CREATING
NICKNAME

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The following error was logged in db2dial.log and a dump file 
was generated while running nnstat. 
 
2012-03-19-03.23.56.773360+540 I232756A623        LEVEL: Severe 
PID     : 27239                TID  : 2199216187728PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000         DB   : DBNAME 
APPHDL  : 0-5831               APPID: 
*LOCAL.db2inst1.120318182101 
AUTHID  : DB2INST1 
EDUID   : 8734                 EDUNAME: db2agent (DBNAME) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:275 
MESSAGE : MASTER TIME INFO 
DATA #1 : Hexdump, 32 bytes 
0x000002053D88C080 : 0000 0000 4F65 EA76 0220 0000 0008 4DEE 
....Oe.v. ....M. 
0x000002053D88C090 : C949 CB68 B58F 4107 0000 0000 0000 0000 
.I.h..A......... 
 
2012-03-19-03.23.56.773469+540 I233380A243        LEVEL: Severe 
PID:27239 TID:2199216187728 NODE:000 Title: MASTER TIME INFO 
Dump 
File:/home/db2inst1/sqllib/db2dump/FODC_AppErr_2012-03-19-03.23. 
56.770865_27239_8734_000/27239.8734.000.dump.bin 
 
2012-03-19-03.23.56.773628+540 I233624A847        LEVEL: Severe 
PID     : 27239                TID  : 2199216187728PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000         DB   : DBNAME 
APPHDL  : 0-5831               APPID: 
*LOCAL.db2inst1.120318182101 
AUTHID  : DB2INST1 
EDUID   : 8734                 EDUNAME: db2agent (DBNAME) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:300 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 22 
 sqlerrmc: invalid index colnames 
 sqlerrp : SQLRL13D 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFFF22      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
 
The -901 error may also occur with the following error message 
returned when user creates a nickname: 
 
SQL0901N  The SQL statement or command failed because of a 
database system 
error. (Reason "invalid index colnames".)  SQLSTATE=58004 
 
This is an error raised when there is a remote table which has 
an index defined on lots of columns involved in NNSTAT operation 
or nickname creation. 
 
This error results from a limit on sum of the length of a 
nickname index columns, which is 640-bytes.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all platform                                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to v97fp7                                            * 
****************************************************************
Local Fix:
Drop the index that has lots of columns on the remote table
available fix packs:
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
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
v97fp7
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.04.2012
24.10.2012
24.10.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP7
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.7 FixList