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

DB2RUNSTATS API CAN FAIL WITH SQL1197N OR UNEXPECTEDLY EXECUTE WITH INDEX
SAMPLING

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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;
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Upgrade to DB2 LUW version 10.1 Fix Pack 3
Workaround
See Local Fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.01.2013
18.11.2013
18.11.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList