DB2 - Problembeschreibung
Problem IT08737 | Status: Geschlossen |
AUTOMATIC REORG FAILS WITH SQLCODE: -2205 RC 6 FOR MDC TABLE | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.5 and Fix Pack 7 * **************************************************************** | |
Local-Fix: | |
Lösung | |
Problem was first fixed in DB2 Version 10.5 and Fix Pack 7 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 06.05.2015 20.01.2016 20.01.2016 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.7 |