IBM Support

LI73845: AFTER DETACHING A TABLE PARTITION, ASYNCHRONOUS INDEX CLEAN UP (AIC) TASK RETURNS ADM13500E ERROR IN DB2DIAG.LOG

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After detaching a table partition, the Asynchronous Index
    Cleanup (AIC) is initiated.  If you alter the table definition
    that affects any of the index column before the AIC task is
    complete, the AIC task return the following error in the
    db2diag.log:
    .
    2008-10-11-11.37.27.605874-240 E513962685E776     LEVEL: Error
    PID     : 18163                TID  : 183046564192PROC :
    db2taskp (PUMA) 6
    INSTANCE: nypxt170             NODE : 006         DB   : PUMA
    APPHDL  : 6-52                 APPID: *N6.DB2.081011153729
    AUTHID  : PCSDB
    FUNCTION: DB2 UDB, ABP,
    ABPDispatcher::updateAssignedTaskProCont, probe:100
    MESSAGE : ADM13500E  An agent executing an asynchronous
              background task
              processor encountered an unrecoverable error. The task
              processor has
              been suspended and diagnostic information was written
              to the
              db2diag.log. Contact IBM Support for assistance. The
              task processor
              context is "0x0000000381B9A480". The task processor
              description is
              "Asynchronous Index Cleaner".
    .
    The problem can be recreated with the following steps:
    .
    *******************************
    - User creates a range-partitioned table.
    - User creates a global index on the same table.
    - User detaches a data partition which triggers asynchronous
      index cleanup (AIC). AIC is the deferred cleanup of indexes
      following operations that invalidate index entries.
    - User alters the table definition, making the indexed column
      bigger in the process (e.g. varchar(10) -> varchar(20)).
    
    Depending on the system load, the above sequence of events may
    cause the error in question if AIC gets deferred and starts
    after the table has been altered.
    *********************************
    

Local fix

  • The workaround is to drop the index before detach, alter the
    table, then recreate the index.
    

Problem summary

  • After detaching a table partition, the Asynchronous Index
    Cleanup (AIC) is initiated.  If you alter the table definition
    that affects any of the index column before the AIC task is
    complete, the AIC task return the following error in the
    db2diag.log:
    .
    2008-10-11-11.37.27.605874-240 E513962685E776     LEVEL: Error
    PID     : 18163                TID  : 183046564192PROC :
    db2taskp (PUMA) 6
    INSTANCE: nypxt170             NODE : 006         DB   : PUMA
    APPHDL  : 6-52                 APPID: *N6.DB2.081011153729
    AUTHID  : PCSDB
    FUNCTION: DB2 UDB, ABP,
    ABPDispatcher::updateAssignedTaskProCont, probe:100
    MESSAGE : ADM13500E  An agent executing an asynchronous
              background task
              processor encountered an unrecoverable error. The task
              processor has
              been suspended and diagnostic information was written
              to the
              db2diag.log. Contact IBM Support for assistance. The
              task processor
              context is "0x0000000381B9A480". The task processor
              description is
              "Asynchronous Index Cleaner".
    .
    The problem can be recreated with the following steps:
    .
    *******************************
    - User creates a range-partitioned table.
    - User creates a global index on the same table.
    - User detaches a data partition which triggers asynchronous
      index cleanup (AIC). AIC is the deferred cleanup of indexes
      following operations that invalidate index entries.
    - User alters the table definition, making the indexed column
      bigger in the process (e.g. varchar(10) -> varchar(20)).
    
    Depending on the system load, the above sequence of events may
    cause the error in question if AIC gets deferred and starts
    after the table has been altered.
    *********************************
    

Problem conclusion

  • Defect => wsdbu00366968
    Module => engn_abp
    Fixed in => V9.1 FP7 (s090308)
    

Temporary fix

  • The workaround is to drop the index before detach, alter the
    table, then recreate the index.
    

Comments

APAR Information

  • APAR number

    LI73845

  • Reported component name

    DB2 UDE ESE LIN

  • Reported component ID

    5765F4104

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-10-17

  • Closed date

    2009-04-24

  • Last modified date

    2009-04-24

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

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

    LI73846

Fix information

  • Fixed component name

    DB2 UDE ESE LIN

  • Fixed component ID

    5765F4104

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:
15 October 2021