IBM Support

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

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error 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.
    

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.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Platforms                                                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 v10.5 Fixpack 10 or later.                    *
    ****************************************************************
    

Problem conclusion

  • First Fixed in Db2 v10.5 Fixpack 10
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT22160

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A50

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-08-26

  • Closed date

    2018-07-16

  • Last modified date

    2018-07-16

  • APAR is sysrouted FROM one or more of the following:

    IT22148

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RA50 PSN

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.5","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
05 November 2021