Topic: 2013 EMEA
Subtopic: DB2 for z/OS
While Locking and other means of concurrency control are essential to any database management system, they are often the cause of problems in today's production systems.
Applications are not always designed with concurrency in mind, so it is not uncommon that with increased transactions volumes concurrency issues start to surface in your production systems.
People dealing with the production systems are not always involved in the design of the applications they manage, so they often have little knowledge of the application locking behavior. This is even more true for applications that are not developed in-house.
Therefore it is important to understand how to detect (potential) locking problems, and how to analyze them to find the root cause of the problem with little or no prior knowledge of the application.
In this session, we discuss:
* Different types of locking and concurrency problems
* Concurrency warning signs
* How to set up periodic monitoring for concurrency problems
We also describe the different tools you have at your disposal to investigate a concurrency problem in order to discover the root cause of the problem. The toolbox consists of:
* DB2 commands
* EXPLAIN statement and the information in the dynamic statement cache
* Standard DB2 traces
* Detailed DB2 traces
* Using online monitor
Lastly we demonstrate how to perform this type of analysis for a simple deadlock scenario.
The target audience are application designers, DBAs and system administrators.
The session assumes that you are familiar with DB2 serialization mechanisms. If that is not the case, please attend also session 'Understanding DB2 for z/OS resource serialization and concurrency control and avoid issues later on' to get up to speed.
Click Here to Download
NOTE: These are only open to members of IDUG. If you are not a member, please CLICK HERE for more information.