|
Problem IC88704
|
Status: Closed |
SQLSTATE 58017 (SQL30073 ERROR) REPORTED WHEN A NON-DB2 CLIENT OR DRIVER ATTEMPTS TO ESTABLISH A CONNECTION |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Connections from non IBM DB2 Client or Driver (CONNX being an
example) may fail with SQL30073 or SQLSTATE = 58017. The
db2diag.log will report 'Invalid DDM Extended Length':
2012-09-25-06.21.33.395768-240 E1196403816E711 LEVEL: Error
PID : 18740 TID : 46928284870976PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-28976
EDUID : 4444 EDUNAME: db2agent 0
FUNCTION: DB2 UDB, DRDA Application Server,
sqljsParseExtendedLength, probe:409
MESSAGE : DIA5000C A DRDA AS token "RECOVERABLE" was detected.
The diagnostic
data returned is (SRVDGN): "FUNCTION ID = 0051 , PROBE
POINT = 0409 ,
TRACE POINT = 0030 , SUBCODE1 = 00000000000058CF,
SUBCODE2 =
000000000000F0F6, SUBCODE3 = 00000000000058D3, ERROR
MSG = Parser:
Invalid DDM Extended Length". |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of non IBM Data Server Clients *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 10.1 Fix Pack 2 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 10.1 FP2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.11.2012
31.12.2012
31.12.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
