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

INVALID CATALOG CACHE STATISTICS SIZE SHOWING UP IN SOME DATABASE
EVENT MONITOR RECORDS

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
Suppose a database event monitor is created. After some SQL 
activity a flush is done on the event monitor followed by a 
connect reset. The flush and reset cause TWO events to be 
written, one generated by the flush and the second one generated 
by the connect reset. There is a count which seems wrong for the 
event that is written due to the connect reset. 
 
4) Database Event 
 
 Record is the result of a flush: FALSE 
 
 Lock Statistics: 
  Lock Waits: 0 
  Total time waited on locks (milliseconds): 0 
  Deadlocks: 0 
  Lock escalations:  0 
  X lock escalations:  0 
  Lock timeouts:  0 
 
................................................................ 
...... 
 
 Catalog Cache Statistics 
  Catalog Cache Lookups: 22    <---- this is wrong 
  Catalog Cache Inserts: 2 
  Catalog Cache Overflows: 0 
  Catalog cache high water mark: 86560 
  Catalog cache statistics size: 18446744073709551604     <---- 
 this is wrong
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All server environments                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Suppose a database event monitor is created. After some SQL  * 
*                                                              * 
* activity a flush is done on the event monitor followed by a  * 
*                                                              * 
* connect reset. The flush and reset cause TWO events to be    * 
*                                                              * 
* written, one generated by the flush and the second one       * 
* generated                                                    * 
* by the connect reset. The catalog cache and statistics cache * 
* sizes                                                        * 
* are wrong for the event that is written due to the connect   * 
* reset.                                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.5 fp6 or higher                     * 
****************************************************************
Local Fix:
Use db2pd -db testdb -statisticscache summary or 
db2pd -db testdb -catalogcache or look at other event records 
to get accurate information on the statistics and catalog 
caches.
available fix packs:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
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
The catalog cache and statistics cache sizes in the database 
event monitor records will be accurate after this APAR is 
applied.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.01.2010
22.04.2010
22.04.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP6
Problem solved according to the fixlist(s) of the following version(s)
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.