|
Problem IT18107
|
Status: Closed |
FAILURE OF USER MAPPING DDL WILL LEADS TO DEADLOCK WHEN ANOTHER TRANSACTION IS PERFORMING ROLLBACK AT THE SAME TIME.
|
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
The lock protocol for federation catalog objects has some
limitation which makes SERVERNAME lock be requested more than
really required.
DDL on user mapping (CREATE/ALTER/DROP USER MAPPING) request
SERVERNAME lock in X mode when the DDL fails, however at the
same
time, there is another transaction doing rollback which request
SERVERNAME lock in X mode too. Note that these 2 transactions
have acquires SERVERNAME S lock before they request X lock, so
cycle dependency
here leads to deadlock. In this case, the two threads are in
wait state,
and not able to be terminated since no response to "force
application". |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* N/A *
**************************************************************** |
| Local Fix: |
None but restart one of the application, the one for user
mapping DDL for instance. |
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.11.2016
02.06.2017
02.06.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
