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

SQL1224 OR -4499 ERROR RETURNS WHEN QUERYING A DB2 LUW 9.7 FIX PACK 4
SERVER FROM A DB2 9.7 FIX PACK 4 CLIENT THROUGH A GATEWAY

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
A SQL1224 error occurs when a query is issued from a DB2 version 
9.7 Fix Pack 4 client, or a -4499 Exception returns to an 
application using a version 9.7 Fix Pack 4 (3.62.56/ 4.12.55) 
IBM Data Server Driver for JDBC and SQLJ connecting in type 4 
mode.  Both the client's and the driver's error message will 
contain the text "The database manager is not able to accept new 
requests, has terminated all requests in progress". 
 
This issue will only occur if a Version 9.7 Fix Pack 4 or higher 
client or driver connects to a Version 9.7 Fix Pack 4 or higher 
server through a DB2 LUW server (acting as a 
gateway) that is at version 9.7 Fix Pack 3a or below. 
 
 
If the 9.7 client/driver, gateway and server are all at Fix Pack 
4 or higher, or if a 9.7 Fix Pack 4 client or driver connects 
directly to the 9.7 Fix Pack 4 server this issue will not occur. 
 
The issue will also not occur if both the client/driver and the 
gateway are at a lower level than version 9.7 Fix Pack 4.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Clients who are connecting to a DB2 LUW 9.7 Fix Pack 4       * 
* server through a DB2 LUW 9.7 Fix Pack 3a or lower DB2 LUW    * 
* server acting as a gateway.                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack6.                        * 
****************************************************************
Local Fix:
There are several workarounds for this issue, which are 
documented below. 
 
1.  You can connect directly to the server from the DB2 client 
or IBM Data Server Driver for JDBC and SQLJ. 
2.  You can upgrade the gateway to Version 9.7 Fix Pack 4. 
3.  You can use a DB2 LUW client or an IBM Data Server Driver 
for JDBC and SQLJ that is older than version 9.7 Fix Pack 4.
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
First  fixed in Version 9.7 Fix Pack 6.
Workaround
See Local Fix Above.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.08.2011
15.06.2012
15.06.2012
Problem solved at the following versions (IBM BugInfos)
9.7.,
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList