IBM Support

IT04417: AGENT TRAPS WITH -901 WHILE ATTEMPTING TO CREATE A TEMPORARY TABLE FOR SPILLING.

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

  • Problem Description
    Under certain timing conditions in a DPF environment a query can
    get
    the below given error in the db2diag.log due to multiple SMP/DPF
    subagents trying to update the slestatus field and an update
    gets
    lost without latch protection.
    
    2014-08-26-16.49.46.664500-240 I341038535E644        LEVEL:
    Severe
    PID     : 5334                 TID : 46915722930496  PROC :
    db2sysc 21
    INSTANCE: db2inst1             NODE : 021            DB   :
    Sample
    APPHDL  : 1-32693              APPID: LOCAL.DB2.140819184249
    AUTHID  : Test              HOSTNAME:
    EDUID   : 82033                EDUNAME: db2agntp (Sample) 21
    FUNCTION: DB2 UDB, sort/list services, sqlsmergerec, probe:2050
    MESSAGE : Creating Temporary Table for sort spill, but one
    already exists.
              Aborting sort operation. Contact IBM Support.
    slestatus = 0x50cc0,
              poolID = 6, objectID = 2
    
    2014-08-26-16.49.46.687826-240 I341039180E18992      LEVEL:
    Severe
    PID     : 5334                 TID : 46915722930496  PROC :
    db2sysc 21
    INSTANCE: db2inst1             NODE : 021            DB   :
    Sample
    APPHDL  : 1-32693              APPID: LOCAL.DB2.140819184249
    AUTHID  : Test              HOSTNAME:
    EDUID   : 82033                EDUNAME: db2agntp (Sample) 21
    FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary
    logging function), probe:50
    MESSAGE :
    DATA #1 : Hexdump, 3648 bytes
    0x00002AABFFCB4F40 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    0x00002AABFFCB4F50 : C00C 0500 0000 0000 0000 DD02 0000 0000
    ................
    0x00002AABFFCB4F60 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    0x00002AABFFCB4F70 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    0x00002AABFFCB4F80 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    0x00002AABFFCB4F90 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    0x00002AABFFCB4FA0 : 0000 0000 0000 0000 0000 0000 0000 0000
    ................
    
    Stack can be as given below:-
    
    Stack #1             Signal #12        Timestamp
    2014-09-04-03.29.35.434271
    0        ossDumpStackTraceInternal
    1        ossDumpStackTraceV98
    2        OSSTrapFile::dumpEx
    3        sqlo_trce
    4        sqloDumpDiagInfoHandler
    5        __pthread_mutex_cond_lock
    6        pthread_kill
    7        ossPthreadKill
    8        sqloDumpEDU
    9        sqldDumpContext
    10       sqlrr_dump_ffdc
    11       sqlzeDumpFFDC
    12       sqlzeMapZrc
    13       sqlrrMapZrc
    14       sqlrisr2
    15       sqldDataFetch
    16       sqliScanLeaf2NoLocking
    17       sqlifnxt
    18       sqlirdk
    19       sqldIndexFetch
    20       sqldRowFetch
    21       sqlriFetch
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 10.5 Fix Pack 5                               *
    ****************************************************************
    

Problem conclusion

  • First Fixed in DB2 10.5 Fix Pack 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT04417

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-09-16

  • Closed date

    2017-05-09

  • Last modified date

    2017-05-09

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

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

    IT04458 IT09881

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:
09 May 2017