DB2 - Problem description
Problem IT29398 | Status: Closed |
DUMP FILE GENERATED AFTER "UNEXPECTED ISVALID() STATUS. RECOVERING." MESSAGE IN DB2DIAG.LOG | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
This problem only occurs in pureScale. There is no impact to applications, but sometimes these messages can occur multiple times, producing many dump files in the db2dump directory. The following is an example: 2019-03-16-22.20.37.048680+540 I55828528A2166 LEVEL: Severe PID : 18022522 TID : 29864 PROC : db2sysc 1 INSTANCE: db2inst1 NODE : 001 DB : DB1 HOSTNAME: hostname EDUID : 29864 EDUNAME: db2loggw (DB1) 1 FUNCTION: , , , probe:700 MESSAGE : Unexpected isValid() status. Recovering. DATA #1 : Hex integer, 4 bytes 0xCFA2C0A4 DATA #2 : SQLP_LRB, PD_TYPE_SQLP_LRB, 128 bytes state Hu (0x82) next 0 rsInfoIdx 0 lockname 000E0000000000000000000076 SQLP_VALLOCK (SQLP_GLFH_NAME) groupmode .IN lrbHeaderFlag 0x0000 lrbHeaderFlag2 0x00 numConv 0 notAwareAttributes 0x00 numSLSInFlight 0 numAgentsWithoutLrb 0 holdingLLM 1 cmrrIID 0 aggregatedrrIID 0 lastGranted a00040016494fe0 lrb_list a00040016494fe0 hash_ptr a000400025b9c40 PLockDataPtr a000400001af1e8 currentALS : seq=1200634, ss=1, H=.IN, G=.IN, SLSInFlags1=00(........), bcp=0, cma=00, coa=00, SLSOutFlags=00, ALSPad=00 00 00 00, SLSInFlags2=00, CH=NON, F=.IN, C=.IN, M=.IN, p=2, fa=00, ca=00 inTransitALS : seq=1200634, ss=0, H=.IN, G=.IN, SLSInFlags1=00(........), bcp=0, cma=00, coa=00, SLSOutFlags=02, ALSPad=00 00 00 00, SLSInFlags2=00, CH=..S, F=.IN, C=.IN, M=.IN, p=2, fa=00, ca=00 confirmedALS : seq=1200634, ss=1, H=.IN, G=.IN, SLSInFlags1=00(........) DATA #3 : SQLP_LRB, PD_TYPE_SQLP_LRB, 128 bytes state Lu (0x84) next 0 rsInfoIdx 0 prev 0 tranChainPrev 0 status G (0x01) mode .IN dur 1 convMode NON tran_handl 1 holdcount 0 wantrrIID 0 rrIID 0 lrbFlag 0x0 chainNum 0 lsoFeedback 0 tran_chain 0 head_ptr a00040016494f60 awb_ptr 0 cursorBitmap 0x40000000 hashResult 531305 wantAttributes 00 priority 2 pad2 00 CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0x090000000D98A5CC get__17@157@sqlpValLotchFCUlT1CPCiCPCcT1 + 0x560 ... 2019-03-16-22.20.37.070959+540 I55834915A504 LEVEL: Info PID : 18022522 TID : 29864 PROC : db2sysc 1 INSTANCE: db2inst1 NODE : 001 DB : DB1 HOSTNAME: hostname EDUID : 29864 EDUNAME: db2loggw (DB1) 1 FUNCTION: DB2 UDB, lock manager, sqlpLMERDumpOnEvent, probe:400 MESSAGE : LMEVENTS successfully dumped to file DATA #1 : String, 86 bytes /log/db2dump/DIAG0001/18022522.001.DB1.2019-03-16-22.20. 37.049780.lmevents.bin | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 11.06.2019 18.01.2020 18.01.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |