Jag wrote:
can anyone tell me what is SQL0911 reason code 68
This is a lock timeout:
----------------------------------------------------------------
$ db2 "? sql0911n"
SQL0911N The current transaction has been rolled back because of
a deadlock or timeout. Reason code "<reason-code>".
Explanation:
The current unit of work was involved in an unresolved contention
for use of an object and had to be rolled back.
The reason codes are as follows:
2 transaction rolled back due to deadlock.
68 transaction rolled back due to lock timeout.
72 transaction rolled back due to an error concerning a DB2 Data
Links Manager involved in the transaction.
Note: The changes associated with the unit of work must be
entered again.
The application is rolled back to the previous COMMIT.
User Response:
To help avoid deadlock or lock timeout, issue frequent COMMIT
operations, if possible, for a long-running application, or for
an application likely to encounter a deadlock.
Federated system users: the deadlock can occur at the federated
server or at the data source. There is no mechanism to detect
deadlocks that span data sources and potentially the federated
system. It is possible to identify the data source failing the
request (refer to the problem determination guide to determine
which data source is failing to process the SQL statement).
Deadlocks are often normal or expected while processing certain
combinations of SQL statements. It is recommended that you
design applications to avoid deadlocks to the extent possible.
sqlcode : -911
sqlstate : 40001
----------------------------------------------------------------
You can avoid this by setting an appropriate value for the
LOCKTIMEOUT database config param, and making sure that your
apps commit (to release locks).
-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----
