|
Problem IC62319
|
Status: Closed |
ABEND ON HOST DATABASE SERVER WHEN USING CLI ON DB2 LUW CLIENT TO EXECUTE A PREPARED STATEMENT WITH VERY MANY PARAMETER MARKERS |
| product: |
DB2 CONNECT / DB2CONNCT / 970 - DB2 |
| Problem description: |
PROBLEM DESCRIPTION:
When a CLI (Call Level Interface) application on a DB2 LUW (DB2
on Linux, UNIX and Windows) client that is connected to a DB2
database on a host calls
SQLExecute() to execute a prepared statement that has very many
parameter markers, it causes an abend (abnormal end of task) on
the host.
The abend occurs because of bad DRDA
(Distributed Relational Database Architecture) data that DB2 LUW
sends to the host.
The abend is ABND=04E-00D35011
PROBLEM SUMMARY:
The bad DRDA data that DB2 LUW sends is an SQLDTA object.
The SQLDTA object contains an FDODTA object for which the
extended length value is 4 greater than what it should be. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of CLI (Call Level Interface) applications on DB2 for *
* Linux, Windows and UNIX clients that connect to a host DB2 *
* database server *
****************************************************************
* PROBLEM DESCRIPTION: *
* Problem Description:: *
* When a CLI (Call Level Interface) application on a DB2 LUW *
* (DB2 on Linux, UNIX and Windows) client that is connected to *
* a DB2 database on a host calls *
* SQLExecute() to execute a prepared statement that has very *
* many parameter markers, it causes an abend (abnormal end of *
* task) on the host. *
* The abend occurs because of bad DRDA (Distributed Relational *
* Database Architecture) data that DB2 LUW sends to the host. *
* The abend is ABND=04E-00D35011 *
* *
* *
* Problem Summary: *
* The bad DRDA data that DB2 LUW sends is an SQLDTA object. *
* The SQLDTA object contains an FDODTA object for which the *
* extended length value is 4 greater than what it should be. *
****************************************************************
* RECOMMENDATION: *
* . *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
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 |
Problem was first fixed in Version 9.7 Fix Pack 1
The fix should be applied on the DB2 LUW installation. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 31.07.2009
11.01.2010
11.01.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
