IBM Support

IT33218: DB2 SERVER TERMINATES ABNORMALLY IN THE SQLDFETCHLARGEROW FUNCTION WITH DB2_4K_DEVICE_SUPPORT=ON SET.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In rare circumstances, LOB data can be corrupted when a table is
    populated by the LOAD utility when DB2_4K_DEVICE_SUPPORT=ON set.
    
    The corruption can take one of two forms:
    - "extended row" LOB data becomes corrupted.  This is detectable
    by Db2 and causes the abnormal termination.
    - "normal" LOB data becomes corrupted.  This is undetectable by
    Db2.
    
    The following stack will be generated when "extended row"
    corruption is detected:
    
      [0] 0x00007F762CCF476E
    _ZN16sqeLocalDatabase15ForceDBShutdownEi + 0x18E
      [1] 0x00007F7628198AA5
    _Z15sqldDumpContextP9sqeBsuEduiiiiiPKcPvi + 0x935
      [2] 0x00007F762819A30A
    _Z18sqldEndDumpBadPageP8sqeAgentP11SQLB_FIX_CBmiiii + 0x8A
      [3] 0x00007F76281C7D59
    _Z17sqldFetchLargeRowP13SQLD_DFM_WORKP13SQLDX_MINI_LDm + 0x2F9
      [4] 0x00007F76281D7B0B _Z15sqldFetchRowExtP13SQLD_DFM_WORK +
    0x31B
      [5] 0x00007F76281CEF79 _Z12sqldReadNormP13SQLD_DFM_WORKl +
    0x989
      [6] 0x00007F76281D0501 /home/.../sqllib/lib64/libdb2e.so.1 +
    0x2B71501
      [7] 0x00007F76281D1DC8 _Z7sqldfrdP13SQLD_DFM_WORK + 0x4F8
      [8] 0x00007F76281241FA
    _Z12sqldRowFetchP8sqeAgentP8SQLD_CCBmmPP10SQLD_VALUEP8SQLZ_RIDmP
    12SQLD_ID_LISTP9SQLP_LSN8 + 0xFFA
    
    The corruption can be detected by a SELECT query that reads the
    corrupt row/column or a utility such as RUNSTATS that does the
    same.
    The corruption will not be detected by utilities that operate on
    a page-by-page basis, such as BACKUP.
    
    The corruption is unrecoverable and the affected table will need
    to be recreated and repopulated.
    

Local fix

  • The corruption can be prevented, but not reversed, by any of the
    following:
    - Disable the use of DB2_4K_DEVICE_SUPPORT if not strictly
    required for the environment.
    - Use LOAD with the "DISK_PARALLELISM 1" option.
    - Use INSERT or INGEST instead of LOAD.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Upgrade to Db2 version 11.5.4.0 or higher.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 version 11.5.4.0 or higher.                   *
    ****************************************************************
    

Problem conclusion

  • Upgrade to Db2 version 11.5.4.0 or higher.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT33218

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B50

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-06-16

  • Closed date

    2020-06-30

  • Last modified date

    2020-06-30

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

  • 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

  • RB50 PSN

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.5"}]

Document Information

Modified date:
27 August 2021