DB2 DATA SRVR D / DB2DSDRVR / A10 - DB2

Properties of the IBM Data Server Driver for JDBC and SQLJ 
driver (also known as the JCC driver) which define special 
register values are sometimes ignored. 
Such JCC driver properties include currentDegree, 
currentFunctionPath, currentMaintainedTableTypesForOptimization, 
currentPackagePath and currentSchema. 
 
The problem only happens when the application is connected to a 
DB2 on z/OS sysplex or a DB2 for Linux, UNIX and Windows 
pureScale cluster and the JCC driver property enableSysplexWLB 
is set to true. And it only happens after the JCC driver as part 
of the getConnection() processing has checked for the existence 
of a DB2 Connect license on the database server. 
The JCC driver typically caches the result of successful license 
validation on the client machine and this cache expires after 7 
days, so the the JCC driver does not check for the existence of 
a DB2 Connect license on the database server for up to 7 days 
after a successful result is cached on the client. For that 
reason the error might appear every 7 days. 
 
What error occurs depends on which JCC driver property is 
ignored. 
When the currentSchema property is ignored it might cause an 
SQLException with DB2 SQL Error: SQLCODE=-204 to be thrown when 
an SQL statement is executed that includes the name of a 
database object which exists in the schema specified by the 
currentSchema property yet the SQL statement does not explicitly 
include the schema name.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of the IBM Data Server Driver for JDBC and SQLJ        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade driver to DB2 10.1 FixPack 4                         * 
****************************************************************

The problem only happens after the application has called 
getConnection() to connect to a database and then called 
commit() or rollback() without first executing any SQL statement 
for the connection. 
As a workaround you can make sure that the application does not 
call commit() or rollback() for the connection before it 
executes any SQL statement for the connection.

? ? 
Close Code 
 ?edit 
Name 
? ? 
Reason Code 
 ?edit 
Release 
? ? 
Return Code 
 ?edit 
Fix Rel. 
 ?edit 
Failing Module 
 ?edit 
Failing Level/SU?Applicable RelsA10N 
 ?Edit... 
=> 
 ?edit 
Test Rel. 
 ?edit 
Support Code 
 ?edit 
Original APARALL ?edit 
Users Affected: (describe the specific software/hardware 
environment in which the problem occurs)NONE 
 ?Edit... 
SRLS/DocumentationNONE 
 ?Edit... 
Modules/Macros changedSee Error Description ?edit 
Problem Description: (describe the problem including external 
symptoms as seen by the customer)First fixed in Version 10.1 Fix 
Pack 3. 
 
? ? 
Close Code 
 ?edit 
Name 
? ? 
Reason Code 
 ?edit 
Release 
? ? 
Return Code 
 ?edit 
Fix Rel. 
 ?edit 
Failing Module 
 ?edit 
Failing Level/SU?Applicable RelsA10N 
 ?Edit... 
=> 
 ?edit 
Test Rel. 
 ?edit 
Support Code 
 ?edit 
Original APARALL ?edit 
Users Affected: (describe the specific software/hardware 
environment in which the problem occurs)NONE 
 ?Edit... 
SRLS/DocumentationNONE 
 ?Edit... 
Modules/Macros changedSee Error Description ?edit 
Problem Description: (describe the problem including external 
symptoms as seen by the customer)First fixed in Version 10.1 Fix 
Pack 3. 
Fixed in DB2 Version 10.1 FixPack 3

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

28.01.2014
19.06.2014
19.06.2014