suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT22148 Status: Closed

SEVERE ERRORS IN THE DB2DIAG.LOG RELATED TO
INGEST(SQLUDISHM::CLEANFORMATTERBLOCK)

product:
DB2 FOR LUW / DB2FORLUW / B10 - 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 v11.1 Mod3 Fixpack 3 or Later.               * 
****************************************************************
Local Fix:
You can also avoid this by running the following before the 
INGEST: 
 
db2 ingest set shm_max_size 8 GB
available fix packs:
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
First Fixed in Db2 v11.1 Mod3 Fixpack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.08.2017
15.03.2018
15.03.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)