home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC62508 Status: Geschlossen

ERROR SQL0429N ENCOUNTERED WHEN RUNNING AUTO RUNSTATS ON OVER 32KTABLES
WITH SET STATISTICS PROFILE OPTION.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
You may encounter error SQL0429N if you have  over 32K tables 
and running Auto Runstats with SET STATISTICS PROFILE option. 
 
Sample Runstats command ran under Auto Runstats: 
db2 runstats on table "TABSCHEMA"."TABNAME" with distribution on 
all columns default num_freqvalues 100 num_quantiles 200 and 
detailed 
indexes all allow write access set profile. 
 
Sample error logged in db2diag.log 
---------------------------------------------------------------- 
------ 
2009-07-02-10.32.11.826667-300 I107285A474        LEVEL: Error 
PID     : 364570               TID  : 1164        PROC : db2acd 
0 
INSTANCE: db2ecp               NODE : 000 
APPID   : *LOCAL.db2ecp.090702153136 
FUNCTION: DB2 UDB, Automatic Table Maintenance, 
Atm::process_tables, probe:360 
MESSAGE : ZRC=0xFFFFFE53=-429 
DATA #1 : <preformatted> 
AutoStats: [IBM][CLI Driver][DB2/AIX64] SQL0429N  The maximum 
number of concurrent LOB locators has been exceeded. 
SQLSTATE=54028 
---------------------------------------------------------------- 
------
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users running runstats with SET STATISTICS PROFILE option    * 
* against more that 32000 tables.                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* SQL0429N error returned if you have  over 32000 tables and   * 
* running Auto Runstats with SET STATISTICS PROFILE option.    * 
*                                                              * 
*                                                              * 
* Sample Runstats command ran under Auto Runstats:             * 
*                                                              * 
* db2 runstats on table "TABSCHEMA"."TABNAME" with             * 
* distribution on all columns default num_freqvalues 100       * 
* num_quantiles 200 and                                        * 
* detailed indexes all allow write access set profile.         * 
*                                                              * 
*                                                              * 
*                                                              * 
* Sample error logged in db2diag.log                           * 
*                                                              * 
* -------------------------------------------------------------- 
*                                                              * 
* 2009-07-02-10.32.11.826667-300 I107285A474        LEVEL:     * 
* Error                                                        * 
* PID    : 364570              TID  : 1164        PROC :       * 
* db2acd                                                       * 
* 0                                                            * 
*                                                              * 
* INSTANCE: ****         NODE : 000                            * 
* APPID  : ********                                            * 
* FUNCTION: DB2 UDB, Automatic Table Maintenance,              * 
*                                                              * 
* Atm::process_tables, probe:360                               * 
*                                                              * 
* MESSAGE : ZRC=0xFFFFFE53=-429                                * 
*                                                              * 
* DATA #1 : <preformatted>                                     * 
*                                                              * 
* AutoStats: [IBM][CLI Driver][DB2/AIX64] SQL0429N  The        * 
* maximum                                                      * 
* number of concurrent LOB locators has been exceeded.         * 
*                                                              * 
* SQLSTATE=54028                                               * 
*                                                              * 
* -------------------------------------------------------------- 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.7 FP2.                                         * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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

Lösung
First fixed in V9.7 FP2.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
12.08.2009
30.06.2010
30.06.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList