Symptom
The db2diag.log records several errors relating to the BUFFER in the following context.
2025-01-14-10.00.48.038358-300 I96159196A4186 LEVEL: Error
PID : XXXX TID : XXXXXX PROC : db2sysc
INSTANCE:XXXXX NODE : 000 DB : XXX
HOSTNAME: XXXXX
EDUID : XXXXX EDUNAME: db2agent
FUNCTION: DB2 UDB, oper system services, sqloBytesToHex, probe:0
MESSAGE : ZRC=0x800F00C2=-2146500414=SQLO_BUFF_TOO_SMALL "Buffer too small"
DATA #1 : Codepath, 8 bytes
0
DATA #2 : String, 35 bytes
Output buffer is not large enough.
The call stack indicates that the table function MON_GET_PKG_CACHE_STMT is involved.
MON_GET_PKG_CACHE_STMT
CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol)
[0] 0x0900000065510104 sqloBytesToHex + 0x2E4
[1] 0x090000004EAD7D38 monFormatSingleStmtArg__FPCcR17sqlmXMLDocBuilderUlT3UiP10sqlz_valuePPcbT8 + 0x2698
[2] 0x090000004EB43608 monFormatPkgCacheStmtArgs__FR17sqlmXMLDocBuilderP21sqlrwPkgCacheStmtInfo + 0x118
[3] 0x090000004EB42DF4 IPRA.$monFormatPkgCacheStmtMetrics__F24sqlmMetricOutputFunctionP21sqlrwPkgCacheStmtInfoR24pkgCacheOutputParametersP17sqmRequest + 0x51A4
[4] 0x090000004EB3774C IPRA.$monGetPkgCacheStmtCommon__FPcN31P17sqludf_scratchpadP16sqludf_call_typeP5sqlcaPFUiPPv_iR24pkgCacheOutputParametersC24sqlm + 0x36C
[5] 0x090000004EB3B34C monGetPkgCacheStmt_v115m9fp0 + 0x1B1C
Read more...
Environment
DB2 LUW "DB2 v11.5.9.0",
Keywords
Slow, Performance, defect, IBM, table function, SQL, Statement, sqloBytesToHex, Zero-length data, , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview