DB2 - Problem description
| Problem IT09513 | Status: Closed |
DIA5000C INVALID FD:OCA DESCRIPTOR REPORTED IN DB2DIAG.LOG FILE | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problem description: | |
DB2 might report the following messages in the db2diag.log file:
2015-05-11-11.39.54.226043+180 E16080E798 LEVEL:
Error
PID : 42025 TID : 140496831768320 PROC :
db2sysc 0
INSTANCE: xxx NODE : 000 DB : L1P
APPHDL : 0-64739 APPID: 150509074732
AUTHID : xxxxxx HOSTNAME: xxxxx
EDUID : 1154 EDUNAME: db2agent (xxx) 0
FUNCTION: DB2 UDB, DRDA Application Server, sqljsParseSqldta,
probe:422
MESSAGE : DIA5000C A DRDA AS token "RECOVERABLE" was detected.
The diagnostic
data returned is (SRVDGN): "FUNCTION ID = 0054 , PROBE
POINT = 0422 ,
TRACE POINT = 0160 , SUBCODE1 = FFFFFFFF800A008E,
SUBCODE2 =
0000000000000002, SUBCODE3 = 0000000000007FEF, ERROR
MSG = Parser:
Invalid FD:OCA descriptor".
2015-05-11-11.39.54.249175+180 I16879E662 LEVEL:
Error
PID : 42025 TID : 140496831768320 PROC :
db2sysc 0
INSTANCE: xxxxx NODE : 000 DB : xxx
APPHDL : 0-64739 APPID: 150509074732
AUTHID : xxxxxx HOSTNAME: xxxxx
EDUID : 1154 EDUNAME: db2agent (xxx) 0
FUNCTION: DB2 UDB, DRDA Application Server, sqljsParseSqldta,
probe:160
MESSAGE : ZRC=0x800A008E=-2146828146=SQLJ_DSCINV "INVALID FDOCA
DESCRIPTOR"
DATA #1 : DDM Object, PD_TYPE_DDM_OBJECT, 16 bytes
data length : 453052
codepoint : 0x2412 ( SQLDTA )
length : 8 ( EXTENDED ) | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.5 Fix Pack 7. * **************************************************************** | |
| Local Fix: | |
| Solution | |
First fixed in DB2 Version 10.5 Fix Pack 7. | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 17.06.2015 16.02.2016 16.02.2016 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.5.0.7 |
|