|
Problem IC78749
|
Status: Closed |
APPLICATION MAY RECEIVE INCOMPLETE DESCRIBE DATA WHEN CLIENTPROGRAMID ATTRIBUTE IS SET |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Application connecting to DB2z, DB2i, or IDS servers with
ClientProgramID connection attribute set may receive incomplete
describe data for a SQL statement, the column names may be
missing or generic (Column1, Column2 ...). |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 Version 9.7 Fix Pack 4 clients on Linux, Unix, and *
* Windows platforms connecting to DB2z, DB2i, or IDS servers *
* with CLIENTPROGRAMID attribute set. *
****************************************************************
* PROBLEM DESCRIPTION: *
* .NET application connecting to DB2/z, DB2i, or IDS servers *
* with ClientProgramID connection attribute set may receive *
* incomplete describe data for a SQL statement, the column *
* names may be missing or generic (Column1, Column2 ...). *
* *
* A trace of such problem would show a request with SET CLIENT *
* PROGRAMID statement like this: *
* - *
* ------------------------------------------------------------ *
* - *
* SEND BUFFER(AR): *
* *
* *
* *
* EXCSQLSET RQSDSS (ASCII) *
* *
* 0 1 2 3 4 5 6 7 8 9 A B C D E F 0123456789ABCDEF *
* *
* 0000 004ED05100010048 201400442113C4E2 .N.Q...H ..D!... *
* *
* 0010 D5D3F44040404040 4040404040404040 ...@@@@@@@@@@@@@ *
* *
* 0020 D5E4D3D3C9C44040 4040404040404040 ......@@@@@@@@@@ *
* *
* 0030 4040E2E8E2E2D5F2 F0F0404040404040 @@........@@@@@@ *
* *
* 0040 4040404001010101 010101010001 @@@@.......... *
* *
* *
* *
* SQLSTT OBJDSS (ASCII) *
* *
* 0 1 2 3 4 5 6 7 8 9 A B C D E F 0123456789ABCDEF *
* *
* 0000 0041D0430001003B 2414000000003153 .A.C...;$.....1S *
* *
* 0010 455420434C49454E 542050524F475241 ET CLIENT PROGRA *
* *
* 0020 4D4944202742436F 6D2E4E455420436C MID 'BCom.NET Cl *
* *
* 0030 69656E7450726F67 72616D4944203727 ientProgramID 7' *
* *
* 0040 FF . *
* *
* *
* *
* PRPSQLSTT RQSDSS (ASCII) *
* *
* 0 1 2 3 4 5 6 7 8 9 A B C D E F 0123456789ABCDEF *
* *
* 0000 0053D0510002004D 200D00442113C4E2 .S.Q...M ..D!... *
* *
* 0010 D5D3F44040404040 4040404040404040 ...@@@@@@@@@@@@@ *
* *
* 0020 D5E4D3D3C9C44040 4040404040404040 ......@@@@@@@@@@ *
* *
* 0030 4040E2E8E2E2D5F2 F0F0404040404040 @@........@@@@@@ *
* *
* 0040 404040405359534C 564C303100040005 @@@@SYSLVL01.... *
* *
* 0050 2116F1 !.. *
* . *
* .. *
* - *
* ------------------------------------------------------------ *
* - *
* *
* A reply would contain the describe data, but the application *
* would still show Column1, Column2, ...: *
* ------------------------------------------------------------ *
* -- *
* RECEIVE BUFFER(AR): *
* *
* *
* *
* SQLCARD OBJDSS (ASCII) *
* *
* 0 1 2 3 4 5 6 7 8 9 A B C D E F 0123456789ABCDEF *
* *
* 0000 000BD04300010005 2408FF ...C....$.. *
* *
* *
* *
* SQLDARD OBJDSS (ASCII) *
* *
* 0 1 2 3 4 5 6 7 8 9 A B C D E F 0123456789ABCDEF *
* *
* 0000 0177D04300020171 2411000000000030 .w.C...q$......0 *
* *
* 0010 3030303044534E20 2020202000000000 0000DSN .... *
* *
* 0020 0000000000000027 1042F3AA75000000 .......'.B..u... *
* *
* 0030 0000000000202020 2020202020202020 ..... *
* *
* 0040 001044534E4C3420 2020202020202020 ..DSNL4 *
* *
* 0050 202000000000FFFF 0007000000000000 .............. *
* *
* 0060 00000000001201C0 0025000000000000 .........%...... *
* *
* 0070 0644424E414D4500 00000000000000FF .DBNAME......... *
* *
* 0080 FF00000000000000 000000000201F400 ................ *
* *
* 0090 0000000000000008 4341504143495459 ........CAPACITY *
* *
* 00A0 0000000000000000 FFFF000000000000 ................ *
* *
* 00B0 00000000000601C0 0025000000000000 .........%...... *
* *
* 00C0 0850524F56494445 5200000000000000 .PROVIDER....... *
* *
* 00D0 00FFFF0000000000 0000000000000A01 ................ *
* *
* 00E0 C000250000000000 00055244424D5300 ..%.......RDBMS. *
* *
* 00F0 00000000000000FF FF00000000000000 ................ *
* *
* 0100 000000000801C100 250000000000000A ........%....... *
* *
* 0110 4D56535F44424E41 4D45000000000000 MVS_DBNAME...... *
* *
* 0120 0000FFFF00000000 0000000000000008 ................ *
* *
* 0130 01C1002500000000 00000A4D56535F42 ...%.......MVS_B *
* *
* 0140 504E414D45000000 0000000000FFFF00 PNAME........... *
* *
* 0150 0000000000000000 00000801C1002500 ..............%. *
* *
* 0160 0000000000075347 5F4E414D45000000 ......SG_NAME... *
* *
* 0170 0000000000FFFF ....... *
* . *
* .. *
* - *
* ------------------------------------------------------------ *
* - *
* *
* In the trace parsing the reply there would be a call to *
* CLI_sqlCompleteCallback() for the sqljrParseSetSqlEnvReply, *
* which is incorrect: *
* 8965 | sqljrParse entry *
* 8966 | | sqljrPreRqstParse entry *
* 8967 | | sqljrPreRqstParse data [probe 500] *
* 8968 | | sqljrPreRqstParse exit *
* 8969 | | sqljrParseSetSqlEnvReply entry *
* 8970 | | | sqljrParseObj entry *
* 8971 | | | | sqljcReadHdrAr entry *
* 8972 | | | | | sqljcReadDssHdr entry *
* 8973 | | | | | sqljcReadDssHdr exit *
* 8974 | | | | sqljcReadHdrAr exit *
* 8975 | | | sqljrParseObj exit *
* 8976 | | | sqljrParsePossibleTypdefs entry *
* 8977 | | | sqljrParsePossibleTypdefs exit *
* 8978 | | | sqljrParseSqlcaGrp entry *
* 8979 | | | sqljrParseSqlcaGrp mbt *
* 8980 | | | sqljrParseSqlcaGrp data [probe 179] *
* 8981 | | | sqljrParseSqlcaGrp exit *
* 8982 | | | sqljrParseObj entry *
* 8983 | | | sqljrParseObj exit [rc = 1] *
* 8984 | | | CLI_sqlCompleteCallback entry <<<<<<<<<<<< *
* 8985 | | | | CLI_sqlCompleteCallback entry *
* 8986 | | | | | sqleUCSqlPostProcessing entry *
* 8987 | | | | | sqleUCSqlPostProcessing exit *
* 8988 | | | CLI_sqlCompleteCallback data [probe 1] *
* 8989 | | | | CLI_sqlCompleteCallback exit *
* 8990 | | | CLI_sqlCompleteCallback exit *
* 8991 | | sqljrParseSetSqlEnvReply exit [rc = 1] *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 5 or refer to Local Fix. *
**************************************************************** |
| Local Fix: |
Unset ClientProgramID |
| available fix packs: |
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 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 |
The problem is first fixed in DB2 Version 9.7 Fix Pack 5 and all
subsequent Fix Packs. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.09.2011
07.12.2011
07.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
