IBM Support

IC80476: AUTOMATIC STATISTICS COLLECTIONS CAN BE FORCED DUE TO LOCK CONFLICT WITH THE LASTUSED DAEMON.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Automatic statistics collections, enabled via AUTO_RUNSTATS and
    AUTO_STMT_STATS database configuration parameters, can be forced
    due to lock conflict with the LASTUSED daemon.  When the problem
    occurs, the statistics logs will contain entries that suggest it
    was interrupted, for example:
    
    2011-11-29-01.01.09.503020-300 I994796A576        LEVEL: Severe
    PID     : 39059596             TID  : 27114       PROC : db2sysc
    0
    INSTANCE: db2inst1             NODE : 000         DB   : TSMDB1
    APPHDL  : 0-13649              APPID:
    *LOCAL.db2inst1.123456789123
    AUTHID  : DB2INST1
    EDUID   : 27114                EDUNAME: db2agent (TSMDB1) 0
    FUNCTION: DB2 UDB, relation data serv, sqlrLocalRunstats,
    probe:9950
    MESSAGE : ZRC=0x80090003=-2146893821=SQLI_INTRP "User interrupt
    detected"
              DIA8003C The interrupt  has been received.
    DATA #1 : unsigned integer, 8 bytes
    8989
    
    2011-11-29-01.01.09.505467-300 I995373A1138       LEVEL: Warning
    PID     : 14352572             TID  : 1098        PROC : db2acd
    0
    INSTANCE: db2inst1             NODE : 000
    APPID   : *LOCAL.db2inst1.123456789123
    EDUID   : 1098                 EDUNAME: db2acd 0
    FUNCTION: DB2 UDB, Automatic Table Maintenance,
    JitsDaemon::runstats, probe:60
    MESSAGE : SQL2310N  The utility could not generate statistics.
    Error "" was
              returned.
    DATA #1 : String, 250 bytes
    AutoStats: Non zero code from Runstats, typically indicating
    that Runstats was forced because another command (for example
    DROP TABLE) needed exclusive table acceess
    SQL2310N  The utility could not generate statistics.  Error
    "-1224" was
    returned.
    
    DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
     sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -2310   sqlerrml: 5
     sqlerrmc: -1224
     sqlerrp : SQLJRERM
     sqlerrd : (1) 0x000004C8      (2) 0x8037006D      (3)
    0x00000000
               (4) 0x00000000      (5) 0x00000000      (6)
    0x00000000
     sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)
    
               (7)      (8)      (9)      (10)        (11)
     sqlstate:
    
    2011-11-29-01.01.09.506314-300 I996512A725        LEVEL: Warning
    PID     : 14352572             TID  : 1098        PROC : db2acd
    0
    INSTANCE: db2inst1             NODE : 000
    EDUID   : 1098                 EDUNAME: db2acd 0
    FUNCTION: DB2 UDB, Automatic Table Maintenance,
    JitsDaemon::runstats, probe:70
    MESSAGE : SQL1224N  The database manager is not able to accept
    new requests,
              has terminated all requests in progress, or has
    terminated the
              specified request because of an error or a forced
    interrupt.
    DATA #1 : String, 172 bytes
    AutoStats: Non zero code from Runstats commit, typically
    indicating that Runstats was forced because another command (for
    example DROP TABLE) needed exclusive table acceess
    
    2011-11-29-01.01.09.506829-300 E997238A566        LEVEL: Event
    PID     : 14352572             TID  : 1098        PROC : db2acd
    0
    INSTANCE: db2inst1             NODE : 000
    EDUID   : 1098                 EDUNAME: db2acd 0
    FUNCTION: DB2 UDB, Automatic Table Maintenance,
    JitsDaemon::runstats, probe:80
    COLLECT : TABLE AND INDEX STATS : Object name with schema : AT
    "2011-11-29-01.01.09.506753" : BY "Asynchronous" : failure
    OBJECT  : Object name with schema, 31 bytes
    DB2INST1  .XXXXXXX
    IMPACT  : None
    DATA #1 : String, 26 bytes
    ZRC=0x90000002=-1879048190
    

Local fix

  • Disable the LASTUSED daemon by setting the
    DB2_SYSTEM_MONITOR_SETTINGS=LAST_USE_INTERVAL:0.    This change
    does not require instance restart.  Once disabled, LASTUSED
    information will not be updated for all databases in the
    instance.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * AUTOMATIC STATISTICS COLLECTIONS CAN BE FORCED DUE TO LOCK   *
    * CONFLICT WITH THE LASTUSED DAEMON.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 9.7 Fix Pack 6.                       *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 Version 9.7 Fix Pack 6.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC80476

  • 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

    2011-12-16

  • Closed date

    2012-06-05

  • Last modified date

    2012-06-05

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

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

    IC84327

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:
05 June 2012