IBM Support

IT31071: SQLKD_PARTNER_ERR LEADS TO SQELOCALDATABASE::FORCEDBSHUTDOWN

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • On multi member instances it is possible to run out of FCM
    buffers which may lead to applications receiving an
    SQLKD_PARTNER_ERROR return code.  This may result in
    sqeLocalDatabase::ForceDBShutdown() being called to force the DB
    to be shut down.
    
    The following probes can show this progression:
    
    2019-09-12-04.04.02.646238+540 I10349500A538        LEVEL:
    Severe
    PID     : 9113572              TID : 337018         PROC :
    db2sysc 0
    INSTANCE: db2inst1             NODE : 000           DB   :
    SAMPLE
    APPHDL  : 0-13710              APPID:
    XXXXXXXXXXXXXXX201124042143
    AUTHID  : YMS                  HOSTNAME: xxxxxxxxxxxx
    EDUID   : 337018               EDUNAME: db2agent (SAMPLE) 0
    FUNCTION: DB2 UDB, fast comm manager,
    sqkfChannel::SendControlBuffer, probe:15
    RETCODE : ZRC=0x85590027=-2057764825=SQLKF_NO_BUFFER "No FCM
    Buffer available"
    
    2019-09-12-04.04.02.646556+540 I10350039A598        LEVEL: Error
    PID     : 9113572              TID : 337018         PROC :
    db2sysc 0
    INSTANCE: db2inst1             NODE : 000           DB   :
    SAMPLE
    APPHDL  : 0-13710              APPID:
    XXXXXXXXXXXXXXX201124042143
    AUTHID  : YMS                  HOSTNAME: xxxxxxxxxxxx
    EDUID   : 337018               EDUNAME: db2agent (SAMPLE) 0
    FUNCTION: DB2 UDB, buffer dist serv, sqlkdDispatchRequest,
    probe:240
    RETCODE : ZRC=0x85590027=-2057764825=SQLKF_NO_BUFFER "No FCM
    Buffer available"
    DATA #1 : Codepath, 8 bytes
    1:4:6:7:9:11:14:15:22:23:26:27:33:34:43:50
    
    :
    
    2019-09-12-04.04.02.649247+540 I10353403A598        LEVEL: Error
    PID     : 30543428             TID : 45512          PROC :
    db2sysc 2
    INSTANCE: db2inst1             NODE : 002           DB   :
    SAMPLE
    APPHDL  : 0-13710              APPID:
    XXXXXXXXXXXXXXX201124042143
    AUTHID  : YMS                  HOSTNAME: xxxxxxxxxxxx
    EDUID   : 45512                EDUNAME: db2agntp (SAMPLE) 2
    FUNCTION: DB2 UDB, buffer dist serv, sqlkdReceiveData,
    probe:1714
    RETCODE : ZRC=0x87580089=-2024275831=SQLKD_PARTNER_ERR
              "BDS partner error.  BDS receiver error because BDS
    sender halted in middle of sending"
    
    2019-09-12-04.04.02.649559+540 I10354002A591        LEVEL:
    Severe
    PID     : 30543428             TID : 45512          PROC :
    db2sysc 2
    INSTANCE: db2inst1             NODE : 002           DB   :
    SAMPLE
    APPHDL  : 0-13710              APPID:
    XXXXXXXXXXXXXXX201124042143
    AUTHID  : YMS                  HOSTNAME: xxxxxxxxxxxx
    EDUID   : 45512                EDUNAME: db2agntp (SAMPLE) 2
    FUNCTION: DB2 UDB, global services, sqlzeMapZrc, probe:45
    MESSAGE : ZRC=0x87580089=-2024275831=SQLKD_PARTNER_ERR
              "BDS partner error.  BDS receiver error because BDS
    sender halted in middle of sending"
    
    :
    
    2019-09-12-04.04.13.218621+540 E10782072A1131       LEVEL:
    Severe
    PID     : 30543428             TID : 45512          PROC :
    db2sysc 2
    INSTANCE: db2inst1             NODE : 002           DB   :
    SAMPLE
    APPHDL  : 0-13710              APPID:
    XXXXXXXXXXXXXXX201124042143
    AUTHID  : YMS                  HOSTNAME: xxxxxxxxxxxx
    EDUID   : 45512                EDUNAME: db2agntp (SAMPLE) 2
    FUNCTION: DB2 UDB, relation data serv, sqlrr_subagent_router,
    probe:1200
    MESSAGE : ZRC=0x87580089=-2024275831=SQLKD_PARTNER_ERR
              "BDS partner error.  BDS receiver error because BDS
    sender halted in middle of sending"
    DATA #1 : String, 31 bytes
    UCstate terminate bit is raised
    DATA #2 : unsigned integer, 4 bytes
    67109184
    DATA #3 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -902   sqlerrml: 3
    sqlerrmc: 137
    sqlerrp : SQLRI503
    sqlerrd : (1) 0x87580089      (2) 0x00000089      (3) 0x00000000
               (4) 0x00000000      (5) 0xFFFFEB12      (6)
    0x00000002
    sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)
               (7)      (8)      (9)      (10)        (11)
    sqlstate:
    
    2019-09-12-04.04.13.219066+540 I10783204A1246       LEVEL: Info
    PID     : 30543428             TID : 45512          PROC :
    db2sysc 2
    INSTANCE: db2inst1             NODE : 002           DB   :
    SAMPLE
    APPHDL  : 0-13710              APPID:
    XXXXXXXXXXXXXXX201124042143
    AUTHID  : YMS                  HOSTNAME: xxxxxxxxxxxx
    EDUID   : 45512                EDUNAME: db2agntp (SAMPLE) 2
    FUNCTION: DB2 UDB, base sys utilities,
    sqeLocalDatabase::ForceDBShutdown, probe:16254
    MESSAGE : Regular agent EDU doing ForceDBShutdown.  Force DB
    shutdown agent ID
              is:
    DATA #1 : APPHDL, PD_TYPE_SQLZ_APPHDL, 4 bytes
    0-13710
    DATA #2 : sqeApplication_acbInfo,
    PD_TYPE_sqeApplication_acbInfo, 4 bytes
    x0
    CALLSTCK: (Static functions may not be resolved correctly, as
    they are resolved to the nearest symbol)
      [0] 0x09000000289B5E6C ForceDBShutdown__16sqeLocalDatabaseFi +
    0xBC8
      [1] 0x090000002A7CF360
    SubAgentPostProcessing__8sqeAgentFPiPUiPUli + 0x203C
      [2] 0x090000002883B320 RunEDU__8sqeAgentFv + 0x33A90
      [3] 0x0900000028877A70 RunEDU__8sqeAgentFv + 0x124
      [4] 0x0900000029B469F4 EDUDriver__9sqzEDUObjFv + 0x130
      [5] 0x0900000028B5A434 sqloEDUEntry + 0x38C
      [6] 0x0900000000567E10 _pthread_body + 0xF0
      [7] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1 Mod 4 Fixpack 6 or higher                *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.1 Mod 4 Fixpack 6
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT31071

  • 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

    2019-11-25

  • Closed date

    2021-03-15

  • Last modified date

    2021-03-15

  • 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

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

Document Information

Modified date:
16 March 2021