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

SQL2314W WHEN RUNSTATS ON TABLE WITH WRITE ACCESS AND LOW
INSERT/UPDATE ACTIVITY.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Warning SQL2314W issued regarding incosistent table and index 
statistics when user running "RUNSTATS ON TABLE 
<SCHEMA.TABLE_NAME> AND INDEXES ALL WITH WRITE ACCESS" with 
concurrent insert / update activities on the table. 
Runstats would completed successfully. 
 
To verify if this scenario, you may collect db2cat result of the 
table: 
db2cat -d <dbname> -s <schema> -n <table_name> -o output_file 
 
Per each index, verify the field "Indcard" against the "No. of 
rows" of the table, if any Indcard > No. of rows, you have 
encounted this scenario.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* SQL2314W when runstats on table with write access and low    * 
* insert/update activity.                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V97 FP2                                           * 
****************************************************************
Local Fix:
Given Runstats is successful, there is no action needed. 
To collect the most updated statistics, you may rerun the same 
Runstats command when there is no insert / update actitivites.
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.08.2009
13.05.2010
13.05.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList