DB2 - Problem description
Problem IT39240 | Status: Closed |
A FODC TRAP MAY OCCUR WHEN DIA5000C MESSAGE IS ISSUED DUE TO A PARSING ERROR. | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
The following error message might be received: 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 = 0053 , PROBE POINT = 0409 , TRACE POINT = 0030 , SUBCODE1 = 000000000000413C, SUBCODE2 = 0000000000004040, SUBCODE3 = 0000000000004140, ERROR MSG = Parser: Invalid DDM Extended Length". The error message may be issued when bad data for a RDBRLLBCK message is received by the server. During the error handling the trap may be encountered and can be identified by the following stack: 00007FF9387E6C10 offset: 0000000000000036 in 0000004100000000 offset: 000000000000030A in 0000000000000000 offset: 00000000000002CC in db2_v111 tx64s1606081100engnsqjssqljserr.C:830> 0000000000000000 offset: 00000000000002CC in If this issue occurs, the dbm is brought down, connections are terminated and an FODC_TRAP is generated in db2dump folder. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 Version 11.5.7.0 * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * All users. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 Version 11.5.7.0 * **************************************************************** | |
Comment | |
Problem was first fixed in Db2 Version 11.5.7.0 | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 29.11.2021 15.12.2021 15.12.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |