DB2 timeouts or deadlocks occur when two users attempt to access a DB2 page or table that is locked. Data for different models can be stored on the same DB2 page. Because of this, any two users, regardless of the models being accessed or updated, can experience timeouts and deadlocks. Even though it is not easily predictable, certain encyclopedia functions have a tendency to cause timeouts and deadlocks. These functions are:
These functions, especially when run on large models, perform thousands of DB2 inserts, updates, and deletes to key encyclopedia tables such as DOBJ, DASC and DPRP. This amount of activity increases the chance of another user attempting to access the same page of a table or index.
Another group of encyclopedia functions have a tendency to cause timeouts and deadlocks because they are not capable of taking interim commits. Because these functions must force a complete rollback if they fail, they cannot take an interim commit, which causes the DB2 page locks to escalate to tablespace locks when run on a large amount of data. These functions are:
|
Copyright © 2013 CA.
All rights reserved.
|
|