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

DROP TABLE FAILS WITH SQL1034C AFTER INSPECT INDEXDATA COMMAND

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
After running INSPECT with the INDEXDATA option on a partitioned 
table with partitioned indexes, an attempt to drop that table 
may fail with a critical error SQL1034C. 
 
The drop command may fail with the following error: 
 
DB21034E  The command was processed as an SQL statement because 
it was not a 
valid Command Line Processor command.  During SQL processing it 
returned: 
SQL1034C  The database is damaged.  All applications processing 
the database 
have been stopped.  SQLSTATE=58031 
 
In the db2diag.log, you will see entries similar to this: 
 
2011-04-20-12.02.32.444843-240 I7348E571            LEVEL: 
Severe 
PID    : 32742                TID  : 47435351058752 KTID : 14489 
PROC    : db2sysc 0 
INSTANCE: db2test              NODE : 000          DB  : SAMPLE 
APPHDL  : 0-164                APPID: *N0.xxxxxx.9999999 
AUTHID  : TEST 
EDUID  : 439                  EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, data management, sqldDelTCB, probe:9018 
RETCODE : ZRC=0x87040055=-2029780907=SQLD_PRGERR "Unknown 
PROGRAM ERROR" 
          DIA8576C A data management services programming error 
occurred.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of partitioned tables with partitioned indexes         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* After running INSPECT on a partitioned table with            * 
* partitioned indexes, you may hit an error when dropping that * 
* table.                                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to the latest fix pack.                              * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
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
Problem is first fixed in DB2 UDB version 9.7 fix pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.06.2011
08.12.2011
08.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.