The SECTION_LEVEL_LOB debug flag was added in Db2 v11.1 M4FP4SAP
for SAP optimization and was on only under SAP workload reg var:
DB2_WORKLOAD=SAP
...
DB2_RUNTIME_DEBUG_FLAGS=TOLERANT_FLOAT,DISABLE_BLANK_TOLERANCE,S
ECTION_LEVEL_LOB [DB2_WORKLOAD]
However, it may cause UPDATE statement with FLOB/LOB greater
than 512KB failed during the SAP Java EHP upgrade.
Some may experience db2diag having following error message and
stack dump:
2019-04-08-17.56.44.482795-240 I2186E2703 LEVEL:
Severe
PID : 10611 TID : 140496408143616 PROC :
db2sysc 0
INSTANCE: db2sid NODE : 000 DB : SID
APPHDL : 0-76 APPID:
9.123.123.88.40023.190408215555
UOWID : 1549 ACTID: 278
AUTHID : SAPSIDDB HOSTNAME: HOSTNAME
EDUID : 165 EDUNAME: db2agent (SID) 0
FUNCTION: DB2 UDB, data management, sqldFixExistingTCB,
probe:13569
MESSAGE : ZRC=0x82040001=-2113667071=SQLD_NONSEVERE_PRGERR
"non-severe dms programming error"
DIA8532C An internal processing error has occurred.
DATA #1 : String, 17 bytes
Expected TEMP TCB
DATA #2 : String, 7 bytes
sqldtcb
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x00007FC89A194700 sqlzSetAndLog901 + 0x2C0
[1] 0x00007FC89355820D
_Z18sqldFixExistingTCBP16sqeLocalDatabaseP9SQLP_LSN8iiiiPP8SQLD_
TCB + 0x6AD
[2] 0x00007FC8932E0B8A
_Z12sqldFetchLFDP8sqeAgentP9sqllf_lseiiPiPc + 0x10A
[3] 0x00007FC899287D5B _Z8sqlriglfP8sqlrr_cbP9sqllf_lseiPiPh +
0xBB
[4] 0x00007FC8994A01D5
_Z8sqlrimsoP8sqlrr_cbP9sqllf_csoPhPjjisPPvi + 0xFB5
[5] 0x00007FC893312CD9 /db2/db2hia/sqllib/lib64/libdb2e.so.1 +
0x20CDCD9
[6] 0x00007FC893310B7C /db2/db2hia/sqllib/lib64/libdb2e.so.1 +
0x20CBB7C
[7] 0x00007FC893315F4C
_Z25sqldFullFormatValCompressP8sqeAgentP13SQLD_TDATARECP15SQLD_T
DATAREC32S2_PS4_PP10SQLD_VALUEiP8SQLD_TCBPiPhP15SQLD_XOR_UPDATE
+ 0x41C
[8] 0x00007FC893455D18
_Z13sqldRowUpdateP8sqeAgentP8SQLD_CCBmPP10SQLD_VALUEmPPv + 0xBA8
[9] 0x00007FC899335EB0 _Z8sqlriupdP8sqlrr_cb + 0x4D0
[10] 0x00007FC89932BE1D
_Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm + 0x4BD
[11] 0x00007FC898D3CB78
_Z29sqlrr_process_execute_requestP8sqlrr_cbib + 0xF08
[12] 0x00007FC898D1C0B6
_Z17sqlrr_array_inputP14db2UCinterfacePP15db2UCdiagStructmt +
0x1776
[13] 0x00007FC896E82C38
_Z19sqljs_ddm_excsqlsttP14db2UCinterfaceP13sqljDDMObject + 0x488
[14] 0x00007FC896E4DE0B
_Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db2U
Cinterface + 0x10B
[15] 0x00007FC896E4EECE
_Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb +
0x54E
[16] 0x00007FC896E41DAD /db2/db2hia/sqllib/lib64/libdb2e.so.1
+ 0x5BFCDAD
[17] 0x00007FC896E48393 /db2/db2hia/sqllib/lib64/libdb2e.so.1
+ 0x5C03393
[18] 0x00007FC896E4904F
_Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T + 0x11F
[19] 0x00007FC896872653 _ZN8sqeAgent6RunEDUEv + 0xDE3
[20] 0x00007FC89A19353E _ZN9sqzEDUObj9EDUDriverEv + 0x1BE
[21] 0x00007FC8986B8E6A sqloEDUEntry + 0x57A
[22] 0x00007FC8A02530A4 /lib64/libpthread.so.0 + 0x80A4
[23] 0x00007FC88FC8604D clone + 0x6D
... ...
2019-04-08-17.56.44.536971-240 I14376E1182 LEVEL:
Severe
PID : 10611 TID : 140496408143616 PROC :
db2sysc 0
INSTANCE: db2sid NODE : 000 DB : SID
APPHDL : 0-76 APPID:
9.123.123.88.40023.190408215555
UOWID : 1549 ACTID: 278
AUTHID : SAPSIDDB HOSTNAME: hostname
EDUID : 165 EDUNAME: db2agent (SID) 0
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_sibling,
probe:140
MESSAGE : section stmt
DATA #1 : Hexdump, 121 bytes
0x00007FC81BA7F1E0 : 5550 4441 5445 2022 4A32 4545 5F43 4F4E
UPDATE "J2EE_CON
0x00007FC81BA7F1F0 : 4649 4745 4E54 5259 2220 5345 5420 2246
FIGENTRY" SET "F
0x00007FC81BA7F200 : 424C 4F42 2220 3D20 3F2C 2022 4454 5950
BLOB" = ?, "DTYP
0x00007FC81BA7F210 : 4522 203D 203F 2057 4845 5245 2022 4349
E" = ? WHERE "CI
0x00007FC81BA7F220 : 4422 203D 203F 2041 4E44 2022 4E41 4D45
D" = ? AND "NAME
0x00007FC81BA7F230 : 4841 5348 2220 3D20 3F20 414E 4420 224E
HASH" = ? AND "N
0x00007FC81BA7F240 : 414D 4522 203D 203F 2041 4E44 2022 4953
AME" = ? AND "IS
0x00007FC81BA7F250 : 4649 4C45 2220 3D20 31
FILE" = 1
... ...
Others may also encounter FODC_Badpage (i.e. applying SAP
support pack) with the following
db2diag messages and stack
dumps:
MESSAGE : ZRC=0x870F0009=-2029060087=SQLO_EOF "the data does not
exist"
DIA8506C Unexpected end of file was reached.
DATA #1 :
Converting to non-critical read error.
MESSAGE : ADM14001C An unexpected and critical error has
occurred: "BadPage".
The instance may have been shutdown as a result. "Automatic"
FODC
(First Occurrence Data Capture) has been invoked and diagnostic
information has been recorded in directory
FUNCTION: DB2 UDB, data management, sqldDelTCB, probe:590
MESSAGE : FIXCOUNTNODEL DEBUG flag is set!
DATA #1 : String, 10 bytes
FixCount:
DATA #2 : Hexdump, 8 bytes
0x0A0002003543BAE8 : 0000 0000 0000 0002
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x09000000881C54DC
sqldDelTCB__FP8sqeAgentP16sqeLocalDatabaseP8SQLD_TCB + 0xF3C
[1] 0x090000008A142940
sqldDropTable__FP8sqeAgentP12SQLB_GLOBALSP8SQLD_TCBi + 0x11A0
[2] 0x09000000880A4F54
sqlbPFPrefetcherEntryPoint__FP16sqbPrefetcherEdu + 0x1474
[3] 0x09000000880C89D0 RunEDU__16sqbPrefetcherEduFv + 0x30
[4] 0x0900000087315BC0 EDUDriver__9sqzEDUObjFv + 0x300
[5] 0x09000000871F7200 sqloEDUEntry + 0x360
[6] 0x090000000056AE10 _pthread_body + 0xF0
[7] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF
... ...
[0] 0x09000000884C1510
sqldFetchLFD__FP8sqeAgentP9sqllf_lseiT3PiPc + 0x870
[1] 0x0900000089EA81FC sqlriglf__FP8sqlrr_cbP9sqllf_lseiPiPUc +
0x35C
[2] 0x0900000089E8EA7C
sqlrimso__FP8sqlrr_cbP9sqllf_csoPUcPUiUiisPPvT6 + 0x2D7C
[3] 0x090000008A498E6C
sqldmadx__FP8sqeAgentP8SQLD_TCBUcUsP9sqllf_csoiT6P8SQLD_LFDPUl +
0x88C
[4] 0x090000008A4B049C
IPRA.$sqldFormatLobLongCol__FP8sqeAgentP10sqlz_valueT2P8SQLD_TCB
iPiT2 + 0x89C
[5] 0x090000008A4A2B2C
IPRA.$sqldFormatNonDMSCols__FP8sqeAgentP13SQLD_TDATARECT2PP10SQL
D_VALUEP8SQLD_TCBPsPiT7P8SQLD_CCBP17SQLU_FORMATTER_CBP8SQLD_VAL
+ 0x138C
[6] 0x090000008A4A76F0
sqldFullFormatValCompress__FP8sqeAgentP13SQLD_TDATARECP15SQLD_TD
ATAREC32T2PP15SQLD_TDATAREC32PP10SQLD_VALUEiP8SQLD_TCBPiPUcP15S
+ 0x430
[7] 0x090000008A6988E0
sqldRowUpdate__FP8sqeAgentP8SQLD_CCBUlPP10SQLD_VALUET3PPv +
0xA60
[8] 0x090000008DB499EC sqlriupd__FP8sqlrr_cb + 0x8CC
[9] 0x090000008A2928B8
sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0x618
... ... |
With db2set registry variable DB2_WORKLOAD set to SAP, the
SECTION_LEVEL_LOB is set:
[i] DB2_WORKLOAD=SAP
...
[i]
DB2_RUNTIME_DEBUG_FLAGS=TOLERANT_FLOAT,DISABLE_BLANK_TOLERANCE,S
ECTION_LEVEL_LOB [DB2_WORKLOAD]
Unset the flag using the db2set:
db2set
DB2_RUNTIME_DEBUG_FLAGS="TOLERANT_FLOAT,DISABLE_BLANK_TOLERANCE"
After setting DB2_RUNTIME_DEBUG_FLAGS:
[i]
DB2_RUNTIME_DEBUG_FLAGS=TOLERANT_FLOAT,DISABLE_BLANK_TOLERANCE[O
] |
