DB2 - Problem description
Problem IT36535 | Status: Closed |
INTERNAL LATCHING LOGIC ERROR FROM TABLE QUEUE SERVICES LEADS TODATABASE SHUTDOWN | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
db2diag.log entries - 2020-12-07-21.48.32.865245+060 I26672726E630 LEVEL: Error PID : 87113 TID : 17754484568416 PROC : db2sysc 1 INSTANCE: db2inst1 NODE : 001 DB : BLUDB APPHDL : 0-44108 APPID: A.B.C.D AUTHID : AUTH1 HOSTNAME: host101 EDUID : 35270 EDUNAME: db2agntp (BLUDB) 1 FUNCTION: DB2 UDB, table Q services, sqlktclo, probe:30 MESSAGE : DIA0001E An internal error occurred. Report the following error code : "Line=00445, rc1=0x82170001, rc2=0x00000000, rc3=(nil), msg=sqloxltc(tq_latch)". 2020-12-07-21.48.32.877786+060 I26676553E1092 LEVEL: Severe PID : 87113 TID : 17754484568416 PROC : db2sysc 1 INSTANCE: db2inst1 NODE : 001 DB : BLUDB APPHDL : 0-44108 APPID: A.B.C.D AUTHID : AUTH1 HOSTNAME: host101 EDUID : 35270 EDUNAME: db2agntp (BLUDB) 1 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:250 MESSAGE : ZRC=0x82170001=-2112421887=SQLKT_PGM_ERROR "NON-SEVERE TQS internal processing error." DIA8532C An internal processing error has occurred. DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 47 sqlerrmc: probe 030 in sqlktclo(), msg=sqloxltc(tq_latch) sqlerrp : SQLRI14B sqlerrd : (1) 0x82170001 (2) 0x00000001 (3) 0x00000000 (4) 0x00000000 (5) 0xFFFFFCB7 (6) 0x00000001 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: 2020-12-07-21.48.32.896041+060 I26685049E835 LEVEL: Severe PID : 87113 TID : 17754484568416 PROC : db2sysc 1 INSTANCE: db2inst1 NODE : 001 DB : BLUDB APPHDL : 0-44108 APPID: A.B.C.D AUTHID : AUTH1 HOSTNAME: host101 EDUID : 35270 EDUNAME: db2agntp (BLUDB) 1 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_sibling, probe:160 MESSAGE : section stmt DATA #1 : Hexdump, 64 bytes 0x0000100A98F78460 : 5345 4C45 4354 202A 2046 524F 4D20 4F44 SELECT * FROM OD 0x0000100A98F78470 : 535F 4844 502E 565F 544F 5049 435F 5452 S_HDP.V_TOPIC_TR 0x0000100A98F78480 : 414E 5341 4354 494F 4E46 4554 4348 4544 ANSACTIONFETCHED 0x0000100A98F78490 : 5F46 494E 414E 4345 3336 305F 464C 4154 _FINANCE360_FLAT 2020-12-07-21.48.36.812391+060 I26701923E626 LEVEL: Severe PID : 87113 TID : 17754484568416 PROC : db2sysc 1 INSTANCE: db2inst1 NODE : 001 DB : BLUDB APPHDL : 0-44108 APPID: A.B.C.D AUTHID : AUTH1 HOSTNAME: host101 EDUID : 35270 EDUNAME: db2agntp (BLUDB) 1 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:550 RETCODE : ZRC=0x82170001=-2112421887=SQLKT_PGM_ERROR "NON-SEVERE TQS internal processing error." DIA8532C An internal processing error has occurred. 2020-12-07-22.04.24.249028+060 I27474202E884 LEVEL: Info PID : 87113 TID : 17741989736800 PROC : db2sysc 1 INSTANCE: db2inst1 NODE : 001 DB : BLUDB APPHDL : 0-44108 APPID: A.B.C.D AUTHID : AUTH1 HOSTNAME: host101 EDUID : 35267 EDUNAME: db2agntp (BLUDB) 1 FUNCTION: DB2 UDB, base sys utilities, sqeLocalDatabase::ForceDBShutdown, probe:17187 MESSAGE : Regular agent EDU doing ForceDBShutdown. Force DB shutdown agent ID is: DATA #1 : APPHDL, PD_TYPE_SQLZ_APPHDL, 4 bytes 0-44108 DATA #2 : sqeApplication_acbInfo, PD_TYPE_sqeApplication_acbInfo, 4 bytes x0 CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0x0000000000000000 ?unknown + 0x0 [1] 0x0000000000000000 ?unknown + 0x0 On other members as well. 2020-12-07-21.48.32.895271+060 I27039538E1094 LEVEL: Severe PID : 1263 TID : 17727267729760 PROC : db2sysc 11 INSTANCE: db2inst1 NODE : 011 DB : BLUDB APPHDL : 0-44108 APPID:A.B.C.D AUTHID : AUTH1 HOSTNAME: host102 EDUID : 352136 EDUNAME: db2agntp (BLUDB) 11 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:250 MESSAGE : ZRC=0x82170001=-2112421887=SQLKT_PGM_ERROR "NON-SEVERE TQS internal processing error." DIA8532C An internal processing error has occurred. DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 47 sqlerrmc: probe 030 in sqlktclo(), msg=sqloxltc(tq_latch) sqlerrp : SQLRI14B sqlerrd : (1) 0x82170001 (2) 0x00000001 (3) 0x00000000 (4) 0x00000000 (5) 0xFFFFFCB7 (6) 0x0000000B sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) 2020-12-07-21.53.43.593466+060 I27307528E633 LEVEL: Severe PID : 1263 TID : 17727267729760 PROC : db2sysc 11 INSTANCE: db2inst1 NODE : 011 DB : BLUDB APPHDL : 0-44108 APPID: A.B.C.D AUTHID : AUTH1 HOSTNAME: host102 EDUID : 352136 EDUNAME: db2agntp (BLUDB) 11 FUNCTION: DB2 UDB, table Q services, sqlktdrp, probe:20 MESSAGE : DIA0001E An internal error occurred. Report the following error code : "Line=01405, rc1=0x87170007, rc2=0x00000000, rc3=(nil), msg=sqloxltc(tq_latch)". 2020-12-07-21.53.43.625136+060 I27311362E1103 LEVEL: Severe PID : 1263 TID : 17727267729760 PROC : db2sysc 11 INSTANCE: db2inst1 NODE : 011 DB : BLUDB APPHDL : 0-44108 APPID: A.B.C.D AUTHID : AUTH1 HOSTNAME: host102 EDUID : 352136 EDUNAME: db2agntp (BLUDB) 11 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:250 MESSAGE : ZRC=0x87170007=-2028535801=SQLKT_SEVERE_PGM_ERROR "SEVERE TQS internal processing error." DIA8516C A severe internal processing error has occurred. DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 47 sqlerrmc: probe 030 in sqlktclo(), msg=sqloxltc(tq_latch) sqlerrp : SQLRI14B sqlerrd : (1) 0x82170001 (2) 0x00000001 (3) 0x00000000 (4) 0x00000000 (5) 0xFFFFFCB7 (6) 0x0000000B sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) This apar will report debug information into the db2diag.log but will also be handled as a severe error and take down the database. The apar fix will improve the diagnostics and reduce the severity of the error so that here will not be a database wide impact. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.5.6 or higher * **************************************************************** | |
Local Fix: | |
NA | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.5.6 or higher * **************************************************************** | |
Comment | |
Upgrade to Db2 11.5.6 or higher | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.04.2021 30.06.2021 30.06.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |