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

DB2 JCC TYPE4 DRIVER FORGETS THE CURRENTSCHEMA VALUE IF ROLLBACK
IMMEDIATELY AFTER A NEW CONNECTION AND ENABLESYSPLEXWLB=TRUE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The special registers are sent with the first SQL on a 
connection and when the commit or rollback is called after the 
first SQL the server returns the current special registers 
values effective at that point in time on a connection. The 
driver only remembers these special registers values returned 
from the server at the transaction boundary and clears any 
values that were set on the datasource property (i.e 
currentSchema). For subsequent transactions if the driver picks 
a new DB2 member it flows these remembered values first before 
flowing any new SQLs. 
 
But if an application is calling rollback as the first thing on 
a connection the server does not return any  special registers 
values back and the driver clears anything that is set as a 
property.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users prior to DB2 V97 FP2                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2 JCC TYPE4 DRIVER FORGETS THE CURRENTSCHEMA VALUE IF      * 
* ROLLBACK                                                     * 
* IMMEDIATELY AFTER A NEW CONNECTION AND ENABLESYSPLEXWLB=TRUE * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 V97 FP2                                * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 V97 FP2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
16.03.2010
22.07.2010
22.07.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList