IBM Support

LI72064: AFTER A DROP DATABASE PARTITION OPERATION, THE EXECUTION OF SOME STATIC PACKAGE CAN RESULT IN SQL0901N AND SUBSEQUENT SEGV

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • After a drop database partition operation, static packages
    containing calls to parallel table UDFs are not invalidated
    properly.  Their subsequent execution can lead to a SQL0901N
    error.  For example, when executing the
    SYSPROC.GET_DBSIZE_INFO() stored procedure, one could observe
    error entries in the db2diag.log reporting invalid node number.
    In addition, it the associated error processing can hit SEGV and
    bring down the DB2 server.
    
    Example: The following errors occurred when executing CALL
    SYSPROC.GET_DBSIZE_INFO() after partition number 2 had been
    dropped:
    
    2007-02-19-13.58.15.989675-300 I6273A451          LEVEL: Error
    PID     : 4829302              TID  : 1           PROC :
    db2agent (SAMPLE) 0
    INSTANCE: dpf2                 NODE : 000         DB   : SAMPLE
    APPHDL  : 0-51                 APPID: *N0.dpf2.070219185748
    AUTHID  : DPF2
    FUNCTION: DB2 UDB, buffer Q services, sqlkqopn, probe:70
    MESSAGE : DIA0001E An internal error occurred. Report the
    following error code : "Invalid node#=2".
    
    2007-02-19-13.58.15.995585-300 I6725A512          LEVEL: Error
    PID     : 4829302              TID  : 1           PROC :
    db2agent (SAMPLE) 0
    INSTANCE: dpf2                 NODE : 000         DB   : SAMPLE
    APPHDL  : 0-51                 APPID: *N0.dpf2.070219185748
    AUTHID  : DPF2
    FUNCTION: DB2 UDB, table Q services, sqlktopn, probe:160
    MESSAGE : DIA0001E An internal error occurred. Report the
    following error code : "Line=01763, rc1=0x82180001,
    rc2=0x00000001, rc3=0, msg=sqlkqopn()".
    
    ...........................................
    
    
    2007-02-19-13.58.16.030818-300 I8163A518          LEVEL: Severe
    PID     : 4829302              TID  : 1           PROC :
    db2agent (SAMPLE) 0
    INSTANCE: dpf2                 NODE : 000         DB   : SAMPLE
    APPHDL  : 0-51                 APPID: *N0.dpf2.070219185748
    AUTHID  : DPF2
    FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:20
    RETCODE : ZRC=0x82180001=-2112356351=SQLKQ_PGM_ERROR
              "BQS NON-SEVERE internal processing error."
              DIA8532C An internal processing error has occurred.
    
    2007-02-19-13.58.16.031823-300 I8682A742          LEVEL: Severe
    PID     : 4829302              TID  : 1           PROC :
    db2agent (SAMPLE) 0
    INSTANCE: dpf2                 NODE : 000         DB   : SAMPLE
    APPHDL  : 0-51                 APPID: *N0.dpf2.070219185748
    AUTHID  : DPF2
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
     sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 39
     sqlerrmc: probe 160 in sqlktopn(), msg=sqlkqopn()
     sqlerrp : SQLRI0E7
     sqlerrd : (1) 0x82180001      (2) 0x00000001      (3)
    0x00000000
               (4) 0x00000000      (5) 0xFFFFFF9D      (6)
    0x00000000
     sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)
               (7)      (8)      (9)      (10)        (11)
     sqlstate:
    .........................................
    
    2007-02-19-13.58.17.604964-300 E128546A1330       LEVEL: Severe
    PID     : 4829302              TID  : 1           PROC :
    db2agent (SAMPLE) 0
    INSTANCE: dpf2                 NODE : 000         DB   : SAMPLE
    APPHDL  : 0-51                 APPID: *N0.dpf2.070219185748
    AUTHID  : DPF2
    FUNCTION: DB2 UDB, SQO Memory Management,
    sqloDiagnoseFreeBlockFailure, probe:999
    MESSAGE : Memory validation failure, diagnostic file dumped.
    DATA #1 : String, 28 bytes
    Corrupt pool free tree node.
    DATA #2 : File name, 26 bytes
    p4829302t0_diagnostics.mem
    CALLSTCK:
      [0] 0x090000001C56FF5C
    diagnoseMemoryCorruptionAndCrash__8SMemPoolFUlCPCc + 0x218
      [1] 0x090000001C56FC70
    diagnoseMemoryCorruptionAndCrash__8SMemPoolFUlCPCc@glue219 +
    0x74
      [2] 0x090000001D2DB674 sqlogmblkEx + 0x0
      [3] 0x000000001C0A0025 ?unknown + 0x11C0A0028
      [4] 0x090000001D2E3EF8 sqlogmblkEx + 0x94
      [5] 0x090000001D2CC308 sqlmoAllocBlock + 0x408
      [6] 0x090000001D2E5B5C sqlogmblkEx + 0xFFFFFFFFFFFFF9B8
      [7] 0x090000001D032BC8
    sqlra_sqlC_mem_get_block_ex__FP8sqlrr_cbUlPPvPCcCUl +
    0xFFFFFFFFFFFFFF78
      [8] 0x090000001D09CAC0
    sqlra_sqlC_insert_section_entry__FP8sqlrr_cbiPP31sqlra_sql_conte
    xt_section_entry + 0x20
      [9] 0x090000001CF7DCD4
    sqlra_sqlC_get_sibling__FP8sqlrr_cbiUlP13db2UCCursorIDP15db2UCCu
    rsorInfoN22PP25sqlra_sql_context_sibling + 0xFFFFFFFFFFFFFF24
    .......................................
    
    2007-02-19-13.58.24.311002-300 E163844A881        LEVEL: Severe
    PID     : 4882552              TID  : 1           PROC :
    db2ipccm 0
    INSTANCE: dpf2                 NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqloEDUSIGCHLDHandler,
    probe:50
    DATA #1 : <preformatted>
    Detected the death of an EDU with process id 4829302
    The signal number that terminated this process was 11
    Look for trap files (t4829302.*) in the dump directory
    
    ............................................
    

Local fix

  • After adding or dropping a database partition, run the following
    query.  It will generate a series of rebind commands that need
    to be executed to rebind packages affected by this problem.
    
    db2 connect to <database name>
    
    db2 +w -x -zrebind_script.clp "select distinct 'REBIND PACKAGE '
    || RTRIM(pd.pkgschema) || '.' || pd.pkgname || ' RESOLVE
    CONSERVATIVE;' from syscat.packagedep pd, syscat.routines r
    where pd.btype='F' and r.specificname = pd.bname and
    r.functiontype='T' and r.parallel='Y'"
    
    db2 -tvf rebind_script.clp
    

Problem summary

  • AFTER A DROP DATABASE PARTITION OPERATION, THE EXECUTION OF SOME
    STATIC PACKAGE CAN RESULT IN SQL0901N AND SUBSEQUENT SEGV
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    LI72064

  • Reported component name

    DB2 UDE ESE LIN

  • Reported component ID

    5765F4104

  • Reported release

    910

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-02-22

  • Closed date

    2009-10-26

  • Last modified date

    2009-10-26

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

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

Fix information

Applicable component levels

  • R910 PSY

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
17 October 2021