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

MESSAGES ABOUT SQLO_QUE_BAD_HANDLE WHEN ONE DOES "DB2 ?
SQL<X>". NO NEED FOR AN INSTANCE.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
Lots of messages about SQLO_QUE_BAD_HANDLE when one does "db2 ? 
sql<X>" due to the passing of bad queue handle 0 to close the 
queue.   Does not require to start up an instance. 
 
This problem reproduces on Unix platform.  Unable to 
reproduce on Windows platform.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Linux/Unix                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Lots of messages about SQLO_QUE_BAD_HANDLE when one does     * 
* "db2 ? sql<X>" in db2diag.log                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V95FP5                                            * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
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
Fixed in V95FP5
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC62078 IC62129 IC68164 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
16.07.2009
09.02.2010
09.02.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.5 FixList