DB2 - Problembeschreibung
Problem IT07513 | Status: Geschlossen |
EXCESSIVE DUMPING FROM SQLILATCHPINNED() ON NON-SEVERE ERROR RC | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
There are excessive and unnecessary diagnostics dumped from the DB2 function sqliLatchPinned for non-severe errors such as user interrupts. This includes both db2diag.log entries and binary dump files. This APAR will limit the diagnostic dumping in that function to severe errors. If the problem is hit, the db2diag.log will show errors similar to the following for a non-severe error: 2015-02-23-10.56.03.352046+540 I1200502A577 LEVEL: Severe PID : 2425690 TID : 114863 PROC : db2sysc 1 INSTANCE: dbusr1 NODE : 001 DB : MYDB APPHDL : 1-32534 APPID: *LOCAL.dbusr1.150304223317 AUTHID : DB2USR1 HOSTNAME: host1 EDUID : 114863 EDUNAME: db2agent (MYDB) 1 FUNCTION: DB2 UDB, index manager, sqliLatchPinned, probe:382 RETCODE : ZRC=0x80100003=-2146435069=SQLP_LINT "Interrupt from application" DIA8003C The interrupt has been received. 2015-02-23-10.56.03.358069+540 I1201080A595 LEVEL: Severe PID : 2425690 TID : 114863 PROC : db2sysc 1 INSTANCE: dbusr1 NODE : 001 DB : MYDB APPHDL : 1-32534 APPID: *LOCAL.dbusr1.150304223317 AUTHID : DBUSR1 HOSTNAME: host1 EDUID : 114863 EDUNAME: db2agent (MYDB) 1 FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary logging function), probe:50 MESSAGE : latch_mode DATA #1 : Hexdump, 4 bytes 0x0A000003B5BF6250 : 0000 0003 .... 2015-02-23-10.56.03.359105+540 I1201676A185 LEVEL: Severe PID:2425690 TID:114863 NODE:001 Title: SQLI_PAGE_DESC Dump File:/db2/dump/DIAG0001/2425690.114863.001.dump.bin 2015-02-23-10.56.03.365879+540 I1201862A178 LEVEL: Severe PID:2425690 TID:114863 NODE:001 Title: SQLI_CB Dump File:/db2/dump/DIAG0001/2425690.114863.001.dump.bin 2015-02-23-10.56.03.366786+540 I1202041A179 LEVEL: Severe PID:2425690 TID:114863 NODE:001 Title: sqeAgent Dump File:/db2/dump/DIAG0001/2425690.114863.001.dump.bin 2015-02-23-10.56.03.367846+540 I1202221A187 LEVEL: Severe PID:2425690 TID:114863 NODE:001 Title: SQLI_GLOBAL_area Dump File:/db2/dump/DIAG0001/2425690.114863.001.dump.bin 2015-02-23-10.56.03.368385+540 I1202409A451 LEVEL: Severe PID : 2425690 TID : 114863 PROC : db2sysc 1 INSTANCE: dbusr1 NODE : 001 DB : MYDB APPHDL : 1-32534 APPID: *LOCAL.dbusr1.150304223317 AUTHID : DBUSR1 HOSTNAME: host1 EDUID : 114863 EDUNAME: db2agent (MYDB) 1 FUNCTION: DB2 UDB, index manager, sqliDumpGlobalArea, probe:400 2015-02-23-10.56.03.369551+540 I1202861A191 LEVEL: Severe PID:2425690 TID:114863 NODE:001 Title: SQLD_KEY pGlobalKey1 Dump File:/db2/dump/DIAG0001/2425690.114863.001.dump.bin 2015-02-23-10.56.03.370458+540 I1203053A190 LEVEL: Severe PID:2425690 TID:114863 NODE:001 Title: SQLD_KEY_Key-part 0 Dump File:/db2/dump/DIAG0001/2425690.114863.001.dump.bin | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.5 Fix Pack 7. * **************************************************************** | |
Local-Fix: | |
Lösung | |
First fixed in Version 10.5 Fix Pack 7. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 05.03.2015 25.01.2016 25.01.2016 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.7 |