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

EXCESSIVE DB2DIAG.LOG ERROR REPORTING FOLLOWING "WARNING: DB2 MAY BE
LOOPING IN LOOKUP STATMENT." MESSAGE

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
V9.5 Fixpak 6 contains a fix for apar IC67239 
As part of the fix, debug code was added but that may get 
triggered in normal circumstances 
( e.g. when a connection has more than 100 open cursors ) which 
may lead to excessive unnecessary error reporting in the 
db2diag.log. 
 
The messages will start with "WARNING: DB2 MAY BE LOOPING IN 
LOOKUP STATMENT." 
 
 
for example the following shell script may trigger the problem 
from CLP : 
 
i=200 
while [ $i -gt 100 ] 
do 
   db2 +c "declare c$i cursor for  values ( $i )" 
   db2 +c "open c$i" 
   i=`expr $i - 1` 
done 
while [ $i -gt 0 ] 
do 
    db2 +c "declare c$i cursor with hold for  values ( $i )" 
    db2 +c "open c$i" 
    i=`expr $i - 1` 
done 
 
db2 commit
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The db2diag.log may contain excessive diagnostic messages    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade DB2 to V9.5 Fixpack 8                                * 
****************************************************************
Local Fix:
Turn off the statement monitor switch 
Identify the application/connection with a high number of open 
cursors and alter the application.( e.g. more frequent commits )
available fix packs:
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
This problem was first fixed in V9.5 FixPack 8
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC73941 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.11.2010
19.07.2011
19.07.2011
Problem solved at the following versions (IBM BugInfos)
9.5.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.8 FixList