Identifying the dynamic SQL statement which is causing a lock escalation in DB2 for z/OS
Document Author:
Richard Corrihons
Document ID:
TD105172
Doc. Organization:
Systems and Technology Group
Document Revised:
05/29/2009
Product(s) covered:
DB2 for z/OS and OS/390; Tivoli OMEGAMON XE for DB2 on z/OS; Tivoli OMEGAMON XE for DB2 Performance Expert on z/OS; Tivoli OMEGAMON XE for DB2 Performance Monitor on z/OS
Abstract: This document details a methodology you can use to identify the dynamic SQL statement that generated a lock escalation. It describes which traces to start, and which jobs to run to analyze the collected traces. It also explains how to analyze the trace report to find the culprit SQL statement. This methodology works for lock escalation that occurs with DB2® for z/OS V8 or above. It is based on the IFCID 337 instrumentation record and on the capability to extract statements from the dynamic statement cache.
Classification:
Software
Category:
Performance
Platform(s):
IBM System z Family
S/W Pillar(s):
Information Management
O/S:
z/OS
Keywords:
lock escalation IFCID DB2 z/OS dynamic SQL
The Techdocs Library
Is this your first visit to Techdocs (the Technical Sales Library)?
