|
Problem IT06325
|
Status: Closed |
IN One Phase Commit FEDERATION, EVEN SET DB2LOCK_TO_RB=STATEMENT,THE WHOLE TRANSACTION ROLLED BACK,NOT THE STATEMENT ROLLED BACK |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
after set DB2LOCK_TO_RB=STATEMENT , the behaviors in federation
db are not correct as it is in normal db
1. in a normal db, it worked as expected, only the fresh
statement was rolled back, and the returned error is
SQL0913N Unsuccessful execution caused by deadlock or
timeout. Reason code "80".
2. in a federation db, the whole transaction was rolled back.
SQL0911N The current transaction has been rolled back
because of a deadlock or timeout. Reason code "80" |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All Platforms *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* upgrade to V10.1 FP5 *
**************************************************************** |
| Local Fix: |
|
| Solution |
fixed in V10.1 FP5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.01.2015
16.07.2015
16.07.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
