DB2 - Problembeschreibung
Problem IC89492 | Status: Geschlossen |
DB2RUNSTATS API CAN FAIL WITH SQL1197N OR UNEXPECTEDLY EXECUTE WITH INDEX SAMPLING | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
In DB2 V10.1, the db2RunstatsData structure includes a new field, iIndexSamplingOption. If your application calls db2Runstats with an input versionNumber of SQL_REL9800 or lower, and the new field is not initialized, you might observe: - runstats fails with: SQL1197N Invalid value specified for keyword "INDEX SAMPLE" in command "RUNSTATS" - runstats executes successfully, but index sampling was used when the application did not request it | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 LUW version 10.1 Fix Pack 3 * **************************************************************** | |
Local-Fix: | |
If compiling the application on DB2 V10.1, change the application to set the new iIndexSamplingOption and use versionNumber db2Version1010. If compiling the application on DB2 pre-V10.1, change the application to initialize the entire db2Runstats structure before setting the desired pre-V10.1 parameters. For example, a c application could have: /* declare and initialize the db2RunstatsData structure to hex zeros */ db2RunstatsData runstatsData = {0}; /* set the desired runstats options */ runstatsData.iSamplingOption = 0; runstatsData.piTablename = (unsigned char *)fullTableName; ... runstatsData.iUtilImpactPriority = 100; | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
Upgrade to DB2 LUW version 10.1 Fix Pack 3 | |
Workaround | |
See Local Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 11.01.2013 18.11.2013 18.11.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.3 | |
10.1.0.3 |