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

AUTOMATIC REORG FAILS WITH SQLCODE: -2205 RC 6 FOR MDC TABLE

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Automatic reorg might fail on MDC table with the following 
messages in db2diag.log 
 
EDUID   : 1224                 EDUNAME: db2acd 0 
FUNCTION: DB2 UDB, Health Monitor, db2AutoReorgExec, probe:190 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -2205   sqlerrml: 1 
 sqlerrmc: 6 
 sqlerrp : db2Reorg 
 sqlerrd : (1) 0x801A006D      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFF95C      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
EDUID   : 1224                 EDUNAME: db2acd 0 
FUNCTION: DB2 UDB, Health Monitor, db2AutoReorgExec, probe:10 
STOP    : Automatic reorg has completed with errors on table 
xxx."yyyy"."mdc_table" 
 
SQL2205N  The requested operation failed because the specified 
index is 
      not valid. Reason code: "<reason-code>". 
 
Explanation: 
 
The specified index parameter is not valid for the requested 
operation. 
Following is a list of reason codes: 
 
 
6 
 
         An index cannot be specified for a REORG TABLE of a 
table that 
         has one or more dimensions using the ORGANIZE BY clause 
of the 
         CREATE TABLE command. 
 
 
health snapshot will also show "State 
= Automation failed" for that table. 
 
 
This is very similar APAR IT04820 although in this case the 
command run is 
REORG TABLE INDEX USE TEMPTBSP RESETDICTIONARY
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Problem was first fixed in DB2 Version 10.1 and Fix Pack 5   * 
****************************************************************
Local Fix:


Solution


Problem was first fixed in DB2 Version 10.1 and Fix Pack 5


Workaround


not known / see Local fix


Timestamps


Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

20.04.2015
13.07.2015
13.07.2015


Problem solved at the following versions (IBM BugInfos)




Problem solved according to the fixlist(s) of the following version(s)


10.1.0.5

FixList