home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC71908 Status: Closed

SQLCODE -901 WITH REASON "ERROR IN GETTING COLDIST_DATA FROM STATS
PROFILE" OBSERVED WITH STATEMENT COMPILATION

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The query compiler may return sqlcode -901 with reason "Error in 
getting coldist_data from stats profile" when processing 
distribution statistics for the tables involved in the query. 
 
Example db2diag.log message: 
 
2010-09-03-16.22.49.982651-240 I227585A815        LEVEL: Severe 
 
PID : 3101176 TID : 1 PROC : db2agent (sample) 0 
 
INSTANCE: db2inst1              NODE : 000         DB   : sample 
 
APPHDL  : 0-1789               APPID: *N0.db2inst1.100903201620 
 
AUTHID  : db2inst1 
 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data, probe:0 
 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 48 
 
 sqlerrmc: Error in getting coldist_data from stats profile 
 
 sqlerrp : SQLNQ741 
 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFFF9C      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
 
           (7)      (8)      (9)      (10)        (11) 
 
 sqlstate:
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of DB2                                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If the stats for a base table and a child table (MQT) are    * 
* out of sync it can cause a -901 error under certain          * 
* circumstances.                                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 fixpack 4 or later.                   * 
****************************************************************
Local Fix:
It is likely that the error will stop after collecting 
statistics for affected tables. It is important to consider that 
the affected tables may include tables that are not directly 
referenced in the user-specified SQL, for example, replicated 
tables and MQTs.  The statistics collection should have the same 
num_freqvalues and num_quantiles specification for all the 
columns of the table.  For example, the following runstats 
commands collect distribution statistics for all columns using 
the database default num_freqvalues and num_quantiles settings. 
    RUNSTATS ON TABLE S.T WITH DISTRIBUTION AND SAMPLED DETAILED 
INDEXES ALL 
    RUNSTATS ON TABLE S.T_REPLICATED WITH DISTRIBUTION AND 
SAMPLED DETAILED INDEXES ALL 
    RUNSTATS ON TABLE S.T_SUMMARY1 WITH DISTRIBUTION AND SAMPLED 
DETAILED INDEXES ALL
available fix packs:
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem first fixed in Version 9.7 fixpack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.10.2010
09.05.2011
09.05.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList