BTLKCONT TIMEOUT OCCURRED AT Fields

BTLKCONT TIMEOUT OCCURRED AT Fields - the date and time of the event in MM/DD/YY HH:MM:SS format
caidb2
The date and time of the event (in
MM/DD/YY HH:MM:SS
format).
  • Number of Threads
    Displays the number of threads involved in the timeout.
  • Victim
    Displays the task that was rolled back in the timeout. Valid values are as follows:
    • AUTH
      The Db2 Authorization ID.
    • CORR
      The threads correlation ID.
    • PLAN
      The plan name. If blank, a Db2 command thread.
    • CONN
      The name of the connection.
  • Ntwk
    (DBATs only) Displays the name of the network in which the conversation took place.
  • LU
    (DBATs only) Displays the logical unit name of a VTAM network node.
  • Inst
    (DBATs only) Displays the unique number that identifies this DBAT across all Db2 sites. Use this number to match the allied distributed thread at the requesting site with all its related DBATs that ran at remote sites.
  • Seq#
    (DBATs only) Displays the LUW sequence number. This identifies the last commit scope that the logical unit participated in. This number is incremented whenever a thread commits or is rolled back.
  • Tokn
    (DBATs only) Db2 assigns a token to each thread it creates. This token is the decimal number that appears after the equal sign in all Db2 messages that display a Logical Unit of Work ID (LUWID).
  • Lock request
    Displays information which shows lock attributes and identifies the locked resource.
  • Resource
    Identifies the resource. See BTSQLTRL - Trace all SQL Statements for a description.
  • Type
    Identifies the lock type. See BTSQLTRL - Trace all SQL Statements for a description.
  • Mode
    Also known as the lock state, this field shows the type of access permitted to concurrent applications that wish to process the same resource.
    • ANY
      A mode used for IRLM CHANGE or UNLOCK requests.
    • US (Unprotected Share)
      An index tree is locked and lock escalation occurs.
    • IS (Intent Share)
      A tablespace lock in which the lock owner can read but not update data. Other applications can both read and update data. IS tablespace locks are only used with page locks.
    • IX (Intent Exclusive)
      A tablespace lock in which both the lock owner and concurrent applications processes can read and update the data. When the lock owner reads a specific page, a S or U page lock is obtained on that page. Other applications can read and update other pages, but not the locked page. When the owner updates data, an X lock is obtained on the updated page and other applications cannot even read the locked page. IX locks are only used with page locks.
    • S (Share)
      Used for both page and tablespace locks. The owner and concurrent applications can read but not update the data.
    • U (Update)
      Used for both page and tablespace locks. The owner and concurrent applications can read data and intend to change it. Only one application can hold a U lock on the locked resource (be it a page, table or tablespace). When the application is ready to change the data, it must wait until there are no S locks on the resource, at which time the lock will be promoted to an X lock.
    • SIX (Shared Intent Exclusive)
      A tablespace lock in which the lock owner can read and update the data. Other application processes can only read data. This lock is only used with page locks. When the lock owner updates data, an X lock is obtained on the updated page and other applications cannot read the locked page.
    • NSU (Nonshare Update Lock)
      An update lock used when an index tree is updated without lock escalation.
    • X (Exclusive)
      Used for both page and tablespace locks. Only the lock owner can read or update data.
  • Dur
    Indicates when a lock is released. Valid values are as follows:
    • ALLOC
      When the resource is deallocated.
    • COMMIT
      When the lock holder issues a COMMIT.
    • COMT+1
      Locks needed to maintain the position of a cursor opened WITH HOLD, which are held past commit.
    • MANUAL
      For plans that were bound with isolation level CS, Db2 does not wait until the next commit point to release locks on pages that were not updated.
    • MANL+1
      Temporary change of consistency level from CS to RR during bind and DDL (RDS changes back internally).
    • PLAN
      The lock is released when the plan is deallocated.
    • FREE
      Duration to free all.
  • EndUsr
    Displays the end user ID of the thread holding the resource. This field contains blanks if the client did not supply this information.
  • WrkStn
    Displays the workstation name of the thread holding the resource. This field contains blanks if the client did not supply this information.
  • Trans
    Displays the transaction name of the thread holding the resource. This field contains blanks if the client did not supply this information.