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

IN DPF OR PURESCALE, TRAP OR HANG POSSIBLE AFTER INTERRUPT OF INTERNAL SQL

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
In DPF or pureScale environments, if the execution of a 
statement or command involves the db2 engine issuing an internal 
SQL statement, and the execution of the internal SQL statement 
was interrupted, then a subsequent connection might pick up an 
EDU that has not been properly cleaned up resulting in possible 
trap or hang or applications receiving SQL0902N. 
 
For example, when a WLM queuing threshold is enabled, 
applications may receive sqlcode -902.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Anybody using queuing thresholds in a dpf, pureScale or SMP  * 
* environment.                                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 11.1 Mod 3 Fix Pack 3                         * 
****************************************************************
Local Fix:
available fix packs:
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
First Fixed in DB2 11.1 Mod 3 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.06.2017
15.03.2018
15.03.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)