Results 1 to 6 of 6

Thread: db2 diaglog

  1. #1
    Join Date
    Aug 2011
    Location
    Mumbai,India
    Posts
    49

    Unanswered: db2 diaglog

    Hi,

    I am getting below warning in diaglog.

    2011-09-29-14.52.47.075227+330 I20845288A514 LEVEL: Warning
    PID : 5964118 TID : 312366 PROC : db2sysc 0
    INSTANCE: db2ins11 NODE : 000
    APPHDL : 0-30653 APPID: *LOCAL.db2ins11.110929115340
    AUTHID : DB2INS11
    EDUID : 312366 EDUNAME: db2agent (instance) 0
    FUNCTION: DB2 UDB, database monitor, sqm_snap_appl_locks, probe:10
    MESSAGE : Snapshot cannot obtain lock information for application with app
    handle 34922. Application in rollback.

    Any specific reason because of which db2 not able to gather lock information??

  2. #2
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Quote Originally Posted by shore View Post

    Any specific reason because of which db2 not able to gather lock information??
    Yes, it's right there in the error message. You may want to read it to the end.

  3. #3
    Join Date
    Aug 2011
    Location
    Mumbai,India
    Posts
    49
    LOCK TIMEOUT REPORT

    Date: 29/09/2011
    Time: 16:35:38
    Instance: db2ins11
    Database: SW_UV_DB
    Database Partition: 0


    Lock Information:

    Lock Name: 00020004000000000296000852
    Lock Type: Row
    Lock Specifics: Tablespace ID=2, Table ID=4, Row ID=x0000000002960008


    Lock Requestor:
    System Auth ID: DB2INS11
    Application Handle: [0-55257]
    Application ID: GA010676.PC74.110929172807
    Application Name: db2jcc_application
    Requesting Agent ID: 118838
    Coordinator Agent ID: 118838
    Coordinator Partition: 0
    Lock timeout Value: 30000 milliseconds
    Lock mode requested: ..X
    Application Status: (SQLM_UOWEXEC)
    Current Operation: (SQLM_EXECUTE)
    Lock Escalation: No

    Context of Lock Request:
    Identification: UOW ID (1); Activity ID (1)
    Activity Information:
    Package Schema: (NULLID )
    Package Name: (SYSSN300NULLID )
    Package Version: ()
    Section Entry Number: 1
    SQL Type: Dynamic
    Statement Type: DML, Insert/Update/Delete
    Effective Isolation: Read Stability
    Statement Unicode Flag: No
    Statement: UPDATE UVUSER.T_USERINFO SET IN_USE = ? WHERE USER_ID=? AND APP_ID = 'GLA'


    Lock Owner (Representative):
    System Auth ID: DB2INS11
    Application Handle: [0-55213]
    Application ID: GA010676.FB47.110929172723
    Application Name: db2jcc_application
    Requesting Agent ID: 371747
    Coordinator Agent ID: 371747
    Coordinator Partition: 0
    Lock mode held: NON

    List of Active SQL Statements: Not available

    List of Inactive SQL Statements from current UOW: Not available

    In my locktimeout report also db2 is not able to catch lock holder query.
    Why so???

  4. #4
    Join Date
    Apr 2006
    Location
    Belgium
    Posts
    2,514
    Provided Answers: 11
    how about : "Application in rollback."
    Best Regards, Guy Przytula
    Database Software Consultant
    Good DBAs are not formed in a week or a month. They are created little by little, day by day. Protracted and patient effort is needed to develop good DBAs.
    Spoon feeding : To treat (another) in a way that discourages independent thought or action, as by overindulgence.
    DB2 UDB LUW Certified V7-V8-V9-V9.7-V10.1-V10.5 DB Admin - Advanced DBA -Dprop..
    Information Server Datastage Certified
    http://www.infocura.be

  5. #5
    Join Date
    Aug 2011
    Location
    Mumbai,India
    Posts
    49
    I thnk the application which will rollback is the lock waiter application not the lock holder application. Then logically it should capture statement which is causing locks. But here somethng revers is happening. What say??

  6. #6
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,369
    I believe the warning in the db2diag.log can be ignored, can be due to:
    https://www-304.ibm.com/support/docv...id=swg1IC71040


    In the lock timeout report: Lock mode held is NON. NON mode means the lock in not actually held so it can't be holding up anyone else:
    IBM DB2 9.5 Information Center for Linux, UNIX, and Windows


    If this happens frequently, try using db2pd with -locks to catch the locks. Another option is to enable statement history on the deadlock event monitor:
    Lock events for DB2 for Linux, UNIX, and Windows, Part 2: New options for analyzing lock timeouts in DB2 9.5

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •