|
Problem IT15499
|
Status: Closed |
DEADLOCK/LOCKTIMEOUT RECEIVED ON REMOTE MEMBER IN XA-PURESCALE ENVIRONMENT, EVEN AFTER XA-COMMIT ON THE COORD MEMBER |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
On pureScale system with multiple member, an XA transaction
running some DDL/DML may fail with locktimeout/deadlock error on
the catalog cache lock on remote member even after the
XA-transaction running the SQL is committed or rolled back.
A simple scenario would be
1. create a table on member 1 using XA-TM
2. commit changes for the transaction.
3. select from table using a connection on a different member
The Lock Event Monitor output would indicate the locking
contention happen on the catalog cache lock, as
the original transaction hasn't released the locks on
the remote member.
A deadlock or lock-timeout would be returned on the select
statement. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 10.5 Fix Pack 8 *
**************************************************************** |
| Local Fix: |
Disconnect the application holding the locks, so the locks are
released as part of the implicit rollback as the connection is
lost. |
| Solution |
First fixed in DB2 10.5 Fix Pack 8 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.05.2016
13.03.2017
13.03.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
