Latest versionsfixlist
11.1.0.6 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
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC71391 Status: Closed

Automatic statistics collection logs excessive messages to db2diag log
files

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
During automatic statistics collection,  diagnostic information 
can be logged to 
the db2diag log.  In some situations,  log entries are 
incorrectly indicated as Error level when they should be 
indicated as Warning level.  In other situations, the log 
entries should be logged to the optstats log instead of the 
db2diag log. 
 
Automatic statistics collection is controlled by the 
AUTO_RUNSTATS and AUTO_STMT_STMTS database configuration 
parameters. 
 
For example, the following error is logged to the db2diag log 
when automatic statistics collection tries to process a table 
scheduled for asynchronous runstats, but the table can no longer 
be found because it has been dropped. 
 
2010-09-21-13.40.25.393781-240 I267916A578        LEVEL: Error 
PID     : 9711862              TID  : 1029        PROC : db2acd 
INSTANCE: sahanant             NODE : 000 
APPID   : *LOCAL.sahanant.100921174026 
EDUID   : 1029                 EDUNAME: db2acd 
FUNCTION: DB2 UDB, Automatic Table Maintenance, 
atmRefreshInfoTable, probe:390 
DATA #1 : String, 11 bytes 
AutoStats: 
DATA #2 : String, 145 bytes 
[IBM][CLI Driver][DB2/AIX64] SQL0100W  No row was found for 
FETCH, UPDATE or DELETE; or the result of a query is an empty 
table.  SQLSTATE=02000 
DATA #3 : String, 5 bytes 
02000 
 
The condition the message describes is only a warning condition 
and should be logged into the optstats log.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* During automatic statistics collection,                      * 
* diagnosticinformationcan be logged tothe db2diag log.  In    * 
* some situations,  log entries areincorrectly indicated as    * 
* Error level when they should beindicated as Warning level.   * 
* In other situations, the logentries should be logged to the  * 
* optstats log instead of thedb2diag log.Automatic statistics  * 
* collection is controlled by theAUTO_RUNSTATS and             * 
* AUTO_STMT_STMTS database configurationparameters.            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version9.5 Fix Pack 7.                        * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Version 9.5 Fix Pack 7.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.09.2010
15.11.2010
15.11.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP7
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.7 FixList
9.5.0.7 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.