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

IMPROVEMENT IN FORCE-ABILITY WHEN QUERY LOOKS TO BE HUNG/LOOPING

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
An application may seem "hung" during query compilation and 
cannot be forced off using the  "FORCE" command.  A long, 
complex query can cause this to happen, and may look like its 
hung, however, it is likely progressing very slowly.  In this 
situation it cannot be interrupted.  This APAR will address the 
ability to force off an application in such a state. 
 
If you suspect such an issue, you can dump a stack trace for the 
problem application.  Determine the EDUID of the application, 
and run "db2pd -stack xxxxx, where xxxxx is the EDUID).  If you 
see the following stack, you may have hit this issue, that is 
not allowing you to force the application off: 
 
<StackTrace> 
.... 
sqlno_kc_func_colcount 
sqlno_kc_get_eff_colcount 
sqlno_kc_func_colcount 
sqlno_kc_get_eff_colcount 
...etc... 
 
If you see the above, then the application is not force-able.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* An application may seem "hung" during query compilation and  * 
* cannot be forced off using the  "FORCE" command.  A long,    * 
* complex query can cause this to happen, and may look like    * 
* its hung, however, it is likely progressing very slowly.  In * 
* this situation it cannot be interrupted.                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* apply the most recent fixpack                                * 
****************************************************************
Local Fix:
available fix packs:
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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
This APAR will address the ability to force off an application 
in such a state.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.09.2010
05.05.2011
05.05.2011
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList