DB2 FOR LUW / DB2FORLUW / A10 - DB2

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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 Fixpack 5 or higher.                    * 
****************************************************************

Firstly fixed in DB2 V10.1 Fixpack 5.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

27.11.2014
14.07.2015
14.07.2015