IBM Support

IT21924: MEMBER PANIC DUE TO INVALID MEMORY SIZE IN SQLEINITWLDISPATCHER()

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Memory allocation failure due to request size 0 called by
    sqleInitWLDispatcher() at sqle_workload_disp.C : 872.
    This caused the member to crash. This happens during the startup
    of the member.
    
    The following is db2diag.log snippet:
    <timestamp> I31154119A1984       LEVEL: Warning
    PID     : 1234567               TID : 123            PROC :
    db2sysc 1
    INSTANCE: db2inst1              NODE : 001
    HOSTNAME: node1
    EDUID   : 123                  EDUNAME: db2sysc 1
    FUNCTION: DB2 UDB, SQO Memory Management, sqlogmblkEx,
    probe:1000
    MESSAGE : ZRC=0x820F0004=-2112946172=SQLO_MEM_SIZE "Mem Mgt
    invalid size"
              DIA8563C An invalid memory size was requested.
    DATA #1 : String, 43 bytes
    Memory management block allocation failure.
    DATA #2 : Codepath, 8 bytes
    2
    DATA #3 : Memory pool handle pointer,
    PD_TYPE_MEM_POOL_HANDLE_PTR, 8 bytes
    0x0780000000023788
    DATA #4 : Requested size, PD_TYPE_MEM_REQUESTED_SIZE, 8 bytes
    0
    DATA #5 : Adjusted block size, PD_TYPE_MEM_ADJUSTED_SIZE, 8
    bytes
    0
    DATA #6 : Options for requested block, PD_TYPE_GET_MEM_OPTIONS,
    4 bytes
    0x00000202
    DATA #7 : Pointer to address that will be set by new allocation,
    PD_TYPE_PTR_TO_ADDRESS_OUT, 8 bytes
    0x0a00000003ffbe50
    DATA #8 : File name, PD_TYPE_OSS_MEM_FILE_NAME, 20 bytes
    sqle_workload_disp.C
    DATA #9 : Line of code, PD_TYPE_OSS_MEM_LINE_NUM, 8 bytes
    872
    DATA #10: Resource binding pointer,
    PD_TYPE_RESOURCE_BINDING_PTR, 8 bytes
    0x0000000000000000
    CALLSTCK: (Static functions may not be resolved correctly, as
    they are resolved to the nearest symbol)
      [0] 0x09000000069EFE00 sqlogmblkEx + 0x698
      [1] 0x09000000069B46E0 sqlogmblkEx + 0x1158
      [2] 0x0900000007F389BC sqleInitWLDispatcher__Fv + 0x7DC
      [3] 0x0900000007F39850 sqleInitWLDispatcher__Fv + 0xDC
      [4] 0x0000000100008FEC
    sqlePreInitSysCtlr__FPUlPUsPP15sqleResyncAgtCBPi + 0xACC
      [5] 0x0000000100003A04 sqleSysCtlr__Fv + 0x644
      [6] 0x09000000068F7380 sqloRunInstance + 0x1208
      [7] 0x09000000068F34D0 sqloRunInstance + 0xF84
      [8] 0x0000000100002040 DB2main + 0xDA0
      [9] 0x09000000078BF678 sqloEDUMainEntry__FPcUi + 0x78
      [10] 0x09000000078BA250 sqloEDUEntry + 0x114
      [11] 0x090000000053FE10 _pthread_body + 0xF0
      [12] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF
    
    <timestamp> I31156104A524        LEVEL: Error
    PID     : 5832760               TID : 123            PROC :
    db2sysc 1
    INSTANCE: db2inst1              NODE : 001
    HOSTNAME: node1
    EDUID   : 123                  EDUNAME: db2sysc 1
    FUNCTION: DB2 UDB, global services, sqzObject::new, probe:20
    MESSAGE : ZRC=0x820F0004=-2112946172=SQLO_MEM_SIZE "Mem Mgt
    invalid size"
              DIA8563C An invalid memory size was requested.
    DATA #1 : String, 20 bytes
    sqle_workload_disp.C
    DATA #2 : unsigned integer, 4 bytes
    872
    
    <timestamp> E31156629A633        LEVEL: Error
    PID     : 1234567              TID : 123            PROC :
    db2sysc 1
    INSTANCE: db2inst1             NODE : 001
    HOSTNAME: node1
    EDUID   : 123                  EDUNAME: db2sysc 1
    FUNCTION: DB2 UDB, base sys utilities, sqle_panic, probe:30
    MESSAGE : ADM14005E  The following error occurred: "Panic".
    First Occurrence
              Data Capture (FODC) has been invoked in the following
    mode:
              "Automatic".  Diagnostic information has been recorded
    in the
              directory named
              "/QX60/dump/FODC_Panic_<timestamp>_1234567_123_001/".
    

Local fix

  • unset DB2_RESOURCE_POLICY
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1 Mod 3 Fix Pack 3 or higher               *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.1 Mod 3 Fix Pack 3
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT21924

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-08-09

  • Closed date

    2018-03-19

  • Last modified date

    2018-03-19

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

    IT21236

  • 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

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
19 March 2018