IBM Support

IC95573: DB2 INSTANCE MIGHT CRASH WHEN USING INCORRECT TABLE DESIGNATOR VALUE FOR RID SCALAR FUNCTIONS.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • db2diag.log might show entries like below :
    
    2013-08-22-09.30.31.013191+480 I188500886A569     LEVEL: Error
    PID     : 418204               TID  : 2572        PROC : db2sysc
    0
    INSTANCE: db2inst1             NODE : 000         DB   :  SAMPLE
    APPHDL  : 0-1226               APPID:
    *LOCAL.db2inst1.130822012830
    AUTHID  : DB2INST1
    EDUID   : 2572                 EDUNAME: db2agent ( SAMPLE) 0
    FUNCTION: DB2 UDB, buffer pool services, sqlbLatchPoolRange,
    probe:20
    MESSAGE : ZRC=0x84020009=-2080243703=SQLB_RC_PG_NUM_ERR
                        "Page number exceeds max -8100"
                         DIA8709E Segmented table page number was
    too high.
    
    Stack of trapping db2agent might look like below :
    
    
    <StackTrace>
    -------Frame------ ------Function + Offset------
    0x09000000004B16BC pthread_kill + 0x88
    0x09000000080B6244 sqloDumpEDU + 0x54
    0x09000000072F6ECC sqle_panic__Fv + 0x88
    0x0900000007F59C6C sqlb_panic + 0xB4
    0x09000000082DCB70 sqlb_panic@glue55F + 0x78
    0x0900000006F73704
    sqlbLatchPoolRange__FP12SQLB_GLOBALSUsUiT3PiT5ib + 0x3C8
    0x090000000760EF0C sqlbReadPageInternal + 0x384
    0x090000000760D4DC sqlbReadPage + 0x16C
    0x0900000007601CEC
    .sqlbGetPageFromDisk.fdpr.clone.133__FP11SQLB_FIX_CBi + 0x11C
    0x090000000760558C sqlbfix__FP11SQLB_FIX_CB + 0xB24
    0x0900000007604A08 @71@118317@sqlbFixPage__FP11SQLB_FIX_CBiUiT2
    + 0x48
    0x09000000086E1EA4
    sqldCheckExternalRid__FP8sqeAgentP13SQLD_DFM_WORKP9sqlri_rid +
    0x4C
    0x09000000082122A8
    sqldRowFetch__FP8sqeAgentP8SQLD_CCBUlT3PP10SQLD_VALUEP8SQLZ_RIDT
    3P12SQLD_ID_LISTP9SQLP_LSN8 + 0xC
    0x09000000076268AC sqlriFetch__FP8sqlrr_cbP9sqlri_taol + 0x38
    0x09000000091FD690 sqlriita__FP8sqlrr_cb + 0x3C
    0x0900000007629AA4 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm +
    0x30
    0x09000000075B588C
    sqlrr_process_fetch_request__FP14db2UCinterface + 0x1A0
    0x0900000008ABA5F8
    sqlrr_open__FP14db2UCinterfaceP15db2UCCursorInfo + 0x8C
    0x09000000075B6E10
    sqljs_ddm_opnqry__FP14db2UCinterfaceP13sqljDDMObject + 0xAC0
    0x090000000759FD60
    sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC
    interface + 0x7C
    0x09000000075A0164
    .sqljsParse.fdpr.clone.52__FP13sqljsDrdaAsCbP14db2UCinterfaceP8s
    qeAgentb + 0x260
    0x090000000759EB84 @63@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb
    + 0x2A4
    0x09000000073FBA4C
    @63@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xA4
    0x09000000073FB7E4
    @63@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x264
    0x09000000073FB2C0 sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T +
    0xE0
    0x090000000745E030 RunEDU__8sqeAgentFv + 0x2FC
    0x09000000074608FC EDUDriver__9sqzEDUObjFv + 0xD8
    0x090000000747431C sqloEDUEntry + 0x260
    </StackTrace>
    

Local fix

  • Use correct table designator value for RID scalar functions.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * all                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 version 9.7.0.9.                              *
    ****************************************************************
    

Problem conclusion

  • The problem is first fixed in DB2 version 9.7.0.9.
    

Temporary fix

  • N/A
    

Comments

APAR Information

  • APAR number

    IC95573

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-08-28

  • Closed date

    2014-04-08

  • Last modified date

    2014-04-08

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

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

    IC96485 IC96825

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
08 April 2014