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

SQLGETCONNECTATTR ALWAYS REPORTS THE APPLICATION HANDLE AS A 16-BIT NUMBER

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
On a database that has more than one database partition, the 
application handle of an application consists of the 
coordinating partition number concatenated with a 16-bit 
counter. 
So if the coordinating partition is not database partition zero, 
the application handle should be a number that is greater than 
the maximum value of a 16-bit number (65536). 
 
As a result of this defect, when you call the CLI (Call Level 
Interface) API function SQLGetConnectAttr to get the application 
handle by passing the parameter fOption as 
SQL_ATTR_DB2_APPLICATION_HANDLE, it always reports the 
application handle as a 16-bit number, even for applications 
whose coordinating partition is not partition zero. 
 
This APAR fix is to make SQLGetConnectAttr report the 
application handle correctly even for applications whose 
coordinating partition is not partition zero.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of DB2 for Linux, UNIX and Windows with a database     * 
* that has more than one database partition.                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* .                                                            * 
****************************************************************
Local Fix:
You can get the true application handle in the output of LIST 
APPLICATIONS, or in the APPLICATION_HANDLE column of the result 
set returned by the table function SYSPROC.MON_GET_CONNECTION.
available fix packs:
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
Problem was first fixed in Version 9.7 Fix Pack 6. 
At a minimum, this fix should be applied on the client.
Workaround
You can get the true application handle in the output of LIST 
APPLICATIONS, or in the APPLICATION_HANDLE column of the result 
set returned by the table function SYSPROC.MON_GET_CONNECTION.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.10.2011
13.06.2012
13.06.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList