|
Problem IC61879
|
Status: Closed |
A DB2 APPLICATION MAY NOT BE ABLE TO RECEIVE COLUMN NAMES FROM A RESULT SET OF A STORED PROCEDURE CALL. |
| product: |
DB2 CONNECT / DB2CONNCT / 970 - DB2 |
| Problem description: |
A DB2 application (for example an application using the DB2.NET
data provider), may not receive column names from a stored
procedure result set. The application may receive column
numbers (eg, 1, 2, 3, etc) instead of the actual column names.
.
The underlying problem is with a DRDA request being sent from
a DB2 Linux, Unix, Windows (LUW) server that will intermittently
fail to produce column names in an SQLCINRD (SQL Result Set
Column Information Reply Data) DRDA codepoint. |
| Problem Summary: |
Users Affected: Remote DB2 application drivers
Problem Description:
A DB2 application (for example an application using the DB2.NET
data provider), may not receive column names from a stored
procedure result set. The application may receive column
numbers (eg, 1, 2, 3, etc) instead of the actual column names. |
| 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 |
First fixed in DB2 UDB Version 9.7, Fixpak 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.07.2009
22.12.2009
22.12.2009 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
