DB2 - Problembeschreibung
Problem IT09649 | Status: Geschlossen |
DB2OPTSTAT log file can contain incorrect details for RUNSTATS | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
Incorrect entries in the db2optstat files are made of all indexes that had runstats executed already. In db2optstat file we can see excessive entries during execute runstats.. example: 1. create table and indexes IDX_1,IDX_2,IDX_3,IDX_4 2. runstats on IDX_1 -> entires for IDX_1 3. runstats on IDX_2 -> entires for IDX_2,IDX_1 4. restart 5. runstats on IDX4 -> entires for IDX_4 and IDX_2,IDX_1 (the ones which had runstats already collected) 6. runstats on IDX_3 -> entires for IDX_3 and IDX_4,IDX_2,IDX_1 (the ones which had runstats already collected) example output: COLLECT : TABLE AND INDEX STATS : Object name with schema : AT "2015-04-14-11.29.51.707000" : BY "User" : success OBJECT : Object name with schema, 19 bytes MYSCHEMA.TAB IMPACT : None DATA #1 : String, 113 bytes RUNSTATS ON TABLE "MYSCHEMA"."TAB" FOR INDEXES "MYSCHEMA"."IDX_2", "MYSCHEMA"."IDX_1" UTIL_IMPACT_PRIORITY 30 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.5 Fix Pack 7 * **************************************************************** | |
Local-Fix: | |
Lösung | |
First fixed in DB2 10.5 Fix Pack 7 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 24.06.2015 09.05.2017 09.05.2017 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.7 |