|
Problem IT05816
|
Status: Closed |
LOAD COMMAND WITH 'ALLOW READ ACCESS LOCK WITH FORCE' WILL RETUR N SQL0911N WHEN OTHER APPLICATIONS ARE QUERYING THE SAME TABLE. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When performing a load with 'allow read access lock with force',
instead of forcing out an application doing a select on the same
table, the load command will get a SQL0911N.
Repro:
create db;
update db cfg using LOCKTIMEOUT 1;
create table tab1(c1 int, c2 int);
insert around 500,000 rows
On first window:
db2 "select * from tab1"
On second window:
db2 "load from load.del of del insert into tab1 nonrecoverable
allow read access lock with force"
The load command will get:
SQL0911N The current transaction has been rolled back because
of a deadlock
or timeout. Reason code "68". SQLSTATE=40001
However, if we change the load command to not have 'allow read
access' as follows, then the select gets a SQL1224N and load
completes successfully.
db2 "load from load.del of del insert into tab1 nonrecoverable
lock with force"
Both Online and Offline LOADs should force other apps when LOCK
WITH FORCE is specified. This APAR will resolve the above
observed issue. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V10.1 Fixpack 5 or higher. *
**************************************************************** |
| Local Fix: |
|
| Solution |
Firstly fixed in DB2 V10.1 Fixpack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.11.2014
14.07.2015
14.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
|
 |
