DB2 - Problem description
Problem IT22160 | Status: Closed |
SEVERE ERRORS IN THE DB2DIAG.LOG RELATED TO INGEST(SQLUDISHM::CLEANFORMATTERBLOCK) | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
When attempt to run the INGEST at the end of the command you may see the following entry in the db2diaglog: 2017-08-14-15.21.41.599121+180 I3652E1137Â Â Â Â Â Â Â Â Â Â Â LEVEL: Severe PIDÂ Â Â Â : 22343Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â TID : 140556552341248 PROC : db2bp INSTANCE: db2inst1Â Â Â Â Â Â Â Â Â Â Â Â NODE : 000Â Â Â Â Â Â Â Â Â Â Â DBÂ Â : CONTENT APPIDÂ Â : *N0.db2inst1.170814122003 HOSTNAME: BIG FUNCTION: DB2 UDB, Ingest utility, SqludiShm::cleanFormatterBlock, probe:2008 DATA #1 : String, 184 bytes NON-FATAL ASSERTION FAILED!!!ASSERTION EXPRESSION: (fieldSetNumHoldByFmt + fieldSetNumInQ == m_pShmOffset->m_fieldSetCount) SOURCE FILE NAME: sqludi_shm.C SOURCE FILE LINE NUMBER: 2008 DATA #2 : Codepath, 8 bytes 0 DATA #3 : unsigned integer, 8 bytes 52763 DATA #4 : unsigned integer, 8 bytes 4827856 DATA #5 : unsigned integer, 8 bytes 2319641 DATA #6 : Boolean, 1 bytes true CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) Â [0] 0x00007FD5E9A563B7 _ZN9SqludiShm19cleanFormatterBlockEv + 0x277 Â [1] 0x00007FD5E9A553EA _ZN9SqludiShm26destroyShmAndControlBlocksEv + 0x4A Â [2] 0x00007FD5E9A29438 _Z19sqludiJobControllerPv + 0xD8 Â [3] 0x0000003AF0407AA1 /lib64/libpthread.so.0 + 0x7AA1 Â [4] 0x0000003AF00E8AAD clone + 0x6D The message can safely be IGNORED. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All Platforms * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 v10.5 Fixpack 10 or later. * **************************************************************** | |
Local Fix: | |
You can also avoid this by increasing INGEST's shared memory limit before running an INGEST: db2 ingest set shm_max_size 8 GB A fix for ingest's memory usage is under IT21593. | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : IT22148 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.08.2017 16.07.2018 16.07.2018 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |