IBM Support

IT33039: DIAGNOSTIC DATA DUMPING AFTER -901 CAUSED TRAP

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

  • In a rare condition, Db2 may run into -901 error:
    2020-03-30-20.53.04.691866+480 I70452A893           LEVEL:
    Severe
    PID     : 39583990             TID : 12338          PROC :
    db2sysc 0
    INSTANCE: db2inst1             NODE : 000           DB   :
    SAMPLE
    APPHDL  : 0-961                APPID:
    36.12.16.13.62772.200330111638
    AUTHID  : DB2INST1             HOSTNAME: myhost1
    EDUID   : 12338                EDUNAME: db2agent (CBUSDB) 0
    FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc,
    probe:250
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 30
    sqlerrmc: Illegal section number : 2560!
    sqlerrp : SQLRA065
    sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 0x00000000
               (4) 0x00000000      (5) 0xFFFFFF38      (6)
    0x00000000
    sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)
               (7)      (8)      (9)      (10)        (11)
    sqlstate:
    
    While dumping the diagnostic data, the engine may trap. The trap
    stack:
    0x090000002E334A28
    sqlrr_dump_sibling__FP8sqlrr_cbP25sqlra_sql_context_siblingiT3 +
    0x218
    0x090000002CBCB998 sqlrr_dump_ffdc__FP8sqlrr_cbiT2 + 0x83C
    0x090000002CBCAFE4 sqlzeDumpFFDC__FP8sqeAgentUiP5sqlcai + 0x28
    0x090000002C9460AC sqlzeSqlCode__FP8sqeAgentUiUlT2P5sqlcaiUsPc +
    0x234
    0x090000002C94583C sqlrrSqlCode + 0xA4
    0x090000002D875B94
    sqlra_find_sect__FP8sqlrr_cbP20sqlra_cached_packageUsiPP20sqlra_
    cached_section@OL@22320 + 0x90
    0x090000002C493A80
    sqlra_get_section__FP8sqlrr_cbPUcsT2T3T2UsUlP16db2UCprepareInfoP
    15db2UCCursorInfoiUi + 0x410
    0x090000002C4A288C
    sqlra_get_section__FP8sqlrr_cbPUcsT2T3T2UsUlP16db2UCprepareInfoP
    15db2UCCursorInfoiUi + 0x274
    0x090000002C4AD9A8
    sqlrr_sql_request_pre__FP14db2UCinterfaceUiiP16db2UCprepareInfoP
    15db2UCCursorInfo + 0x308
    0x090000002C3B4A00
    sqlrr_open__FP14db2UCinterfaceP15db2UCCursorInfo + 0x2F0
    0x090000002CA543B8
    sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC
    interface + 0xD04
    0x090000002CA4B8E0 @72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb
    + 0x11E4
    0x090000002CA4B8E0 @72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb
    + 0x11E4
    0x090000002CA4B4D4 @72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb
    + 0xDD8
    0x090000002D7B94E4
    @72@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xA8
    0x090000002D7B9FF8
    @72@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x5FC
    0x090000002D20995C RunEDU__8sqeAgentFv + 0x40E1C
    0x090000002D17E738 RunEDU__8sqeAgentFv + 0x124
    0x090000002BF93AE4 EDUDriver__9sqzEDUObjFv + 0x130
    0x090000002BC252D4 sqloEDUEntry + 0x3A0
    
    The fix for this APAR corrects the dumping logic so it won't
    crash the server, instead of fixing the -901 error since the
    reason for -901 is still unknown.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * N/A                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 for LUW V11.1 Mod4 Fixpack6 or later.         *
    ****************************************************************
    

Problem conclusion

  • This problem is firstly fixed on V11.1 Mod4 Fixpack6.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT33039

  • 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

    2020-06-01

  • Closed date

    2021-03-21

  • Last modified date

    2021-03-21

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

    IT32844

  • 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:
22 March 2021