SAP Knowledge Base Article - Preview

2133738 - DIA5000C or DIA8003C "AGENT TERMINATING" was detected.

Symptom

  • The short dump of an ABAP program shows a failure. 
  • The dev_w* trace shows sql error -1224. 
  • When the date and time is matched in the db2diag.log, an entry similar to the following can be found:

    2015-02-04-17.37.32.259884-360 E51866381A578 LEVEL: Error
    PID : 00000000 TID : 63997 PROC : db2sysc 0
    INSTANCE: db2<SID> NODE : 000 DB : <SID>
    APPHDL : 0-35609 APPID:
    AUTHID : SAP<SID>
    EDUID : 63997 EDUNAME: db2agent (<SID>) 0
    FUNCTION: DB2 UDB, DRDA Application Server, sqljsTermAgentReply, probe:10
    MESSAGE : DIA5000C A DRDA AS token "AGENT TERMINATING" was detected. The
    diagnostic data returned is (SRVDGN): "SQLERRP:sqlpgRes
    SQLCODE:-1224".

    2015-02-04-17.37.32.260192-360 E51866960A829 LEVEL: Error
    PID : 00000000 TID : 63997 PROC : db2sysc 0
    INSTANCE: db2<SID> NODE : 000 DB : <SID>
    APPHDL : 0-35609 APPID:
    AUTHID : SAP<SID>
    EDUID : 63997 EDUNAME: db2agent (<SID>) 0
    FUNCTION: DB2 UDB, DRDA Application Server, sqljsTermAgentReply, probe:11
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1224 sqlerrml: 0
    sqlerrmc:
    sqlerrp : sqlpgRes
    sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x007F551E
    (4) 0x00000000 (5) 0x00000000 (6) 0x00000000
    sqlwarn : (1) (2) (3) (4) (5) (6)
    (7) (8) (9) (10) (11)
    sqlstate:

  • Additionally the issue can manifest in the db2diag.log for 10.5 fixpack 8 showing an"Interrupt from application".
    2016-07-11-03.37.02.506283+120 I1924A614            LEVEL: Error
    <<<----
    PID     : xxx                TID : 17590466310624 PROC :
    db2sysc 0
    INSTANCE: xxxxxx             NODE : 000           DB   :
    SAMPLE
    APPHDL  : 0-28242              APPID:
    *LOCAL.xxxxxxxxxx
    AUTHID  : db2xxxxx           HOSTNAME:xxxxxxx.net
    EDUID   : 9539                 EDUNAME: db2agent (SAMPLE) 0
    FUNCTION: DB2 UDB, catalog services,
    sqlrlCatalogScan::postUpdateCacheHandling, probe:10
    RETCODE : ZRC=0x80100003=-2146435069=SQLP_LINT "Interrupt from
    application"
    DIA8003C The interrupt  has been received.
  • Further checking the db2optstats you can see a more detailed overview of the table access
    2016-07-11-03.37.02.524436+120 I1126219A885         LEVEL: Warning
    PID     : xxx               TID : 17590497833440 PROC :
    db2acd 0
    INSTANCE: db2xxxx         NODE : 000
    HOSTNAME: xxxxxxx.net
    FUNCTION: DB2 UDB, Automatic Table Maintenance,
    JitsDaemon::runstats, probe:70
    MESSAGE : ZRC=0xFFFFFB38=-1224
    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, 171 bytes
    AutoStats: Non zero code from Runstats commit, typically
    indicating that Runstats was forced because another command (for
    example DROP TABLE) needed exclusive table access
    DATA #2 : String, 10 bytes
    RTS Daemon
    DATA #3 : String, 70 bytes
    ROLLBACK Failed - issuing disconnect/connect to release the
    locks held


Read more...

Environment

Db2 IBM

Keywords

  • DB6 DIA5000C "AGENT TERMINATING" "SQLCODE:-1224" -1224
  • The diagnostic data returned is (SRVDGN): "SQLERRP:sqlpgRes SQLCODE:-1224".
  • DIA8003C The interrupt  has been received, db2optstats, ZRC=0x80100003=-2146435069=SQLP_LINT "Interrupt from
    application"

, KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.