DB2 - Problem description
Problem IT29233 | Status: Closed |
INSTANCE PANIC WHEN PAGE CLEANER AIO FAILS DUE TO OUT-OF-MEMORY ERROR. | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
If a Page Cleaner is returned an out-of-memory error (SQLO_MEM) while collecting outstanding AIO it will cause the instance to panic on DPF and pureScale environments. The follow messages can be seen in db2diag.log: EDUID : 122 EDUNAME: db2pclnr (XXXX) 6 FUNCTION: DB2 UDB, oper system services, sqloLioAIOCollect, probe:100 MESSAGE : ZRC=0x870F0024=-2029060060=SQLO_MEM "out of memory" DIA8533C The system memory limit was reached. EDUID : 122 EDUNAME: db2pclnr (XXXX) 6 FUNCTION: DB2 UDB, buffer pool services, sqlbClnrAsyncWriteCompletion, probe:40 MESSAGE : ZRC=0x870F0024=-2029060060=SQLO_MEM "out of memory" DIA8533C The system memory limit was reached. EDUID : 122 EDUNAME: db2pclnr (XXXX) 6 FUNCTION: DB2 UDB, buffer pool services, sqlbClnrAsyncWriteCompletion, probe:300 EDUID : 122 EDUNAME: db2pclnr (BLUDB) 6 FUNCTION: DB2 UDB, buffer pool services, sqlbClnrAsyncWriteCompletion, probe:301 DATA #1 : Buffer page descriptor, PD_TYPE_SQLB_BPD, 256 bytes Pagekey: {pool:1;obj:12;type:128} PPNum:53238 EDUID : 122 EDUNAME: db2pclnr (XXXX) 6 FUNCTION: DB2 UDB, RAS/PD component, pdStartFODC, probe:10 MESSAGE : ADM14001C An unexpected and critical error has occurred: "Panic". | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher * **************************************************************** | |
Local Fix: | |
Ensure there is sufficient memory and swap available to Db2. | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.05.2019 16.01.2020 16.01.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |