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

INACCURACY IN MONITOR DATA WHEN A SET INTEGRITY STATEMENT IS ISS UED AND A
TABLE HAS A CHECK CONSTRAINT THAT INVOKES A ROUTINE.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
User may see inaccuracy in the total_section_time and 
total_routine_time monitor elements if they have a table which 
has a check constraint that invokes a routine, and they issue 
the SET INTEGRITY statement on that table.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW users issuing SET INTEGRITY and using routines in    * 
* table check constraints                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When the SET INTEGRITY statement is issued on a table that   * 
* has one or more check constraints defined that invoke a UDF, * 
* some monitoring elements may report incorrect data. In       * 
* particular the total_section_time and total_routine_time     * 
* elements may report values that are larger/smaller than      * 
* expected.                                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW Version 9.7 Fix Pack 2.                   * 
****************************************************************
Local Fix:
No local workaround.
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
There is no workaround for this problem. Upgrade to DB2 LUW 
Version 9.7 Fix Pack 2.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.12.2009
08.04.2010
15.06.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