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

DB2DART /LHWM MAY FAIL WITH "ERROR: INTERNAL ERROR HAPPENED: FOUND
UNEXPECTED GLOBAL INDEX OBJECT"

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
db2dart /LHWM throws following error incorrectly: 
Error: Internal error happened: found unexpected global index 
object 
 
If db2dart /lhwm encounters a non-partitioned table(with index) 
after a partitioned table(global index), db2dart may incorrectly 
consider the non-partitioned table as partitioned table with 
global index and throw the error.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 Users using db2dart /LHWM                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* see above                                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.5 Fix Pack 9 or higher              * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem first fixed in DB2 Version 9.5 Fix Pack 9
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC80125 IC84182 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.11.2011
12.03.2012
12.03.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.9 FixList