The document describes an unexpected OS error that occurred during prefetching in the buffer pool. It was likely caused by resources being removed unexpectedly from underneath the prefetching routine, possibly due to commands like ipclean or ipcrm. The error is not a problem with the buffer pool itself. Inspecting the OS may reveal what caused the resources to be removed.
The document describes an unexpected OS error that occurred during prefetching in the buffer pool. It was likely caused by resources being removed unexpectedly from underneath the prefetching routine, possibly due to commands like ipclean or ipcrm. The error is not a problem with the buffer pool itself. Inspecting the OS may reveal what caused the resources to be removed.
The document describes an unexpected OS error that occurred during prefetching in the buffer pool. It was likely caused by resources being removed unexpectedly from underneath the prefetching routine, possibly due to commands like ipclean or ipcrm. The error is not a problem with the buffer pool itself. Inspecting the OS may reveal what caused the resources to be removed.
CALLED : OS, -, unspecified_system_function OSERR: EIDRM (43)
DATA #3 : ZRC, PD_TYPE_ZRC, 4 bytes
0x8300002B MESSAGE : Unexpected OS error. This is not a problem within the buffer pool; it most likely means that resources have been torn down from underneath the prefetcher. The routine reporting the error is likely a victim and should not be investigated. Inspect the OS to determine what may have removed the IPC resource. This situation is often caused by running utilities such as ipclean or ipcrm, which may also be called during HA failover or other user-supplied scripts. CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0x00007F45B87F5DC7 _Z17sqlbpfRemoveFromQP12SQLB_pfQUEUEmPP14SQLB_pfRequestP16sqeLoc alDatabasePP12SQLD_OBJ_HDLP12SQLB_GLOBALS + 0x3F7 [1] 0x00007F45B85AEAED _Z26sqlbPFPrefetcherEntryPointP16sqbPrefetcherEdu + 0x39D [2] 0x00007F45B85AE6C4 _ZN16sqbPrefetcherEdu6RunEDUEv + 0x24 [3] 0x00007F45C0DBBC8E _ZN9sqzEDUObj9EDUDriverEv + 0x1BE [4] 0x00007F45BF228B6B sqloEDUEntry + 0x57B [5] 0x00007F45C7D11EA5 /lib64/libpthread.so.0 + 0x7EA5 [6] 0x00007F45B4A8C8CD clone + 0x6D
2020-06-28-05.30.38.823404+000 E7967924E1637 LEVEL: Severe
PID : 5233 TID : 139923667543808 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : BLUDB HOSTNAME: db2wh-1591753516138-db2u-0 EDUID : 140 EDUNAME: db2pfchr (BLUDB) 0 FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, probe:998 MESSAGE : ADM14001C An unexpected and critical error has occurred: "Panic". 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 "/mnt/blumeta0/db2/log/NODE0000/FODC_Panic_2020-06-28- 05.30.37.662812 _0000/". Please look in this directory for detailed evidence about what happened and contact IBM support if necessary to diagnose the problem. DATA #1 : Signal Number Recieved, 4 bytes 6