DB2 - Problembeschreibung
Problem IC77174 | Status: Geschlossen |
STATISTICS COLLECTION MIGHT LEAD TO ERROR SQLCODE SQL1034C UNDER SPECIFIC CONDITIONS. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
Statistics collection might lead to error sqlcode SQL1034C under specific conditions. For the error to occur, the following conditions are needed: - the database has UCA collation - statistics collection is being done on a partitioned table - the partitioned table has at least one character non FOR BIT column - a character non FOR BIT column is a key part in a partitioned index If the problem occurs, a FODC collection should appear in DIAGPATH, for example: 2011-03-21-08.10.32.828790-240 E29714445E761 LEVEL: Error PID : 16701 TID : 47821436741952PROC : db2sysc 0 INSTANCE: svtdbm2 NODE : 000 DB : LNX1 APPHDL : 0-1827 APPID: *N0.svtdbm2.110321121616 AUTHID : SVTDBM2 EDUID : 14612 EDUNAME: db2agent (LNX1) 0 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:10 MESSAGE : ADM14005E The following error occurred: "AppErr". First Occurrence Data Capture (FODC) has been invoked in the following mode: "Automatic". Diagnostic Information has been recorded in the directory named "/home/svtdbm2/sqllib/db2dump/FODC_AppErr_2011-03-21-08.10.32.82 7774_16701_14612_000/". The diagnostic log might show a SQLZ_RC_BADOPT retcode message with sqlcode -902: 2011-03-21-08.10.32.836193-240 I29715754E565 LEVEL: Severe PID : 16701 TID : 47821436741952PROC : db2sysc 0 INSTANCE: svtdbm2 NODE : 000 DB : LNX1 APPHDL : 0-1827 APPID: *N0.svtdbm2.110321121616 AUTHID : SVTDBM2 EDUID : 14612 EDUNAME: db2agent (LNX1) 0 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:250 RETCODE : ZRC=0x80000062=-2147483550=SQLZ_RC_BADOPT "Invalid option" DIA8108C Incompatible code page "" with country code "". Option was "". 2011-03-21-08.10.32.840637-240 I29717187E823 LEVEL: Severe PID : 16701 TID : 47821436741952PROC : db2sysc 0 INSTANCE: svtdbm2 NODE : 000 DB : LNX1 APPHDL : 0-1827 APPID: *N0.svtdbm2.110321121616 AUTHID : SVTDBM2 EDUID : 14612 EDUNAME: db2agent (LNX1) 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: -902 sqlerrml: 2 sqlerrmc: 98 sqlerrp : SQLRR046 sqlerrd : (1) 0x80000062 (2) 0x00000062 (3) 0x00000000 (4) 0x00000000 (5) 0xFFFFDCE3 (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: The stack in the FODC directory is likely to include: sqloDumpEDU sqldDumpContext sqlrr_dump_ffdc sqlzeDumpFFDC sqlzeMapZrc sqlrrMapZrc sqlrLocalRunstats sqlrrsta sqlrr_runstats_DA This problem was first introduced into DB2 Version 9.7 Fix Pack 1. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * Statistics collection might lead to error sqlcode SQL1034C * * under specific conditions. * * * * For the error to occur, the following conditions are needed: * * - the database has UCA collation * * - statistics collection is being done on a partitioned table * * - the partitioned table has at least one character non FOR * * BIT column * * - a character non FOR BIT column is a key part in a * * partitioned index * * * * If the problem occurs, a FODC collection should appear in * * DIAGPATH, for example: * * * * 2011-03-21-08.10.32.828790-240 E29714445E761 LEVEL: * * Error * * PID : 16701 TID : 47821436741952PROC : * * db2sysc 0 * * INSTANCE: svtdbm2 NODE : 000 DB : * * LNX1 * * APPHDL : 0-1827 APPID: * * *N0.svtdbm2.110321121616 * * AUTHID : SVTDBM2 * * EDUID : 14612 EDUNAME: db2agent (LNX1) 0 * * FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, * * probe:10 * * MESSAGE : ADM14005E The following error occurred: "AppErr". * * First Occurrence Data Capture (FODC) has been invoked in the * * following mode: "Automatic". Diagnostic Information has * * been recorded in the directory named * * "/home/svtdbm2/sqllib/db2dump/FODC_AppErr_2011-03-21-08.10.3 * * 2.827774_16701_14612_000/". * * * * The diagnostic log might show a SQLZ_RC_BADOPT retcode * * message with sqlcode -902: * * * * 2011-03-21-08.10.32.836193-240 I29715754E565 LEVEL: * * Severe * * PID : 16701 TID : 47821436741952PROC : * * db2sysc 0 * * INSTANCE: svtdbm2 NODE : 000 DB : * * LNX1 * * APPHDL : 0-1827 APPID: * * *N0.svtdbm2.110321121616 * * AUTHID : SVTDBM2 * * EDUID : 14612 EDUNAME: db2agent (LNX1) 0 * * FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, * * probe:250 * * RETCODE : ZRC=0x80000062=-2147483550=SQLZ_RC_BADOPT "Invalid * * option" * * DIA8108C Incompatible code page "" with country code "". * * Option was "". * * * * 2011-03-21-08.10.32.840637-240 I29717187E823 LEVEL: * * Severe * * PID : 16701 TID : 47821436741952PROC : * * db2sysc 0 * * INSTANCE: svtdbm2 NODE : 000 DB : * * LNX1 * * APPHDL : 0-1827 APPID: * * *N0.svtdbm2.110321121616 * * AUTHID : SVTDBM2 * * EDUID : 14612 EDUNAME: db2agent (LNX1) 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: -902 sqlerrml: 2 * * sqlerrmc: 98 * * sqlerrp : SQLRR046 * * sqlerrd : (1) 0x80000062 (2) 0x00000062 (3) * * 0x00000000 * * (4) 0x00000000 (5) 0xFFFFDCE3 (6) * * 0x00000000 * * sqlwarn : (1) (2) (3) (4) (5) (6) * * (7) (8) (9) (10) (11) * * sqlstate: * * * * The stack in the FODC directory is likely to include: * * * * sqloDumpEDU * * sqldDumpContext * * sqlrr_dump_ffdc * * sqlzeDumpFFDC * * sqlzeMapZrc * * sqlrrMapZrc * * sqlrLocalRunstats * * sqlrrsta * * sqlrr_runstats_DA * * * * This problem was first introduced into DB2 Version 9.7 Fix * * Pack 1. * **************************************************************** * RECOMMENDATION: * * Updrade to DB2 Version 9.7 Fix Pack 5. * **************************************************************** | |
Local-Fix: | |
It is possible that the problem can be avoided if table and index statistics are collected separately. For example, instead of executing: RUNSTATS ON TABLE S.T WITH DISTRIBUTION AND SAMPLED DETAILED INDEXES ALL; execute table and index collection separately back to back: RUNSTATS ON TABLE S.T WITH DISTRIBUTION; RUNSTATS ON TABLE S.T FOR SAMPLED DETAILED INDEXES ALL; | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Lösung | |
This problem is first fixed in DB2 Version 9.7 Fix Pack 5. | |
Workaround | |
See Local Fix. | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 27.06.2011 19.01.2012 19.01.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP5 | |
Problem behoben lt. FixList in der Version | |
9.7.0.5 |