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

CONNECTION FAILS WITH A DRDA DATA STREAM SYNTAX ERROR -4499, ON A 3-TIER
CONNECTION TO DB2 V10 AND ABOVE

product:
DB2 DATA SRVR D / DB2DSDRVR / A10 - DB2
Problem description:
On 3-tier connection to DB2 Linux, 
Unix and Windows Server version 10.1 or above via DB2 Connect 
Gateway version 9.7 or lower, connection fails with the 
following exception: 
 
[jcc][t4][2034][11148][3.64.106] Execution failed due to a 
distribution protocol error that caused deallocation of the 
conversation. 
A DRDA Data Stream Syntax Error was detected. 
Reason: 0x1900. ERRORCODE=-4499, SQLSTATE=58009 
 
This occurs due to the driver sending MONITOR element in 
the COMMIT and ROLLBACK DRDA commands which the downlevel 
DB2 Connect gateway does not understand and results in a 
DRDA error.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of IBM Data Server Driver for JDBC and SQLJ        * 
* shipped with DB2 10.1 releases earlier than DB2 10.1 Fixpack * 
* 5                                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Refer error description                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 Fixpack 5                                * 
****************************************************************
Local Fix:
Solution
Upgrade to DB2 10.1 Fixpack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.07.2015
22.07.2015
22.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList