|
Problem IC66073
|
Status: Closed |
LOCK TABLE CREATES AN IS LOCK ON SYSIBM.SYSUSERAUTH IN ADDITION TO THE TABLE LOCK REQUESTED |
| product: |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 |
| Problem description: |
A LOCK TABLE statement does not only lock the table in
question. In addition an IS lock is created on
SYSIBM.SYSUSERAUTH, which will be kept till the end of
transaction.
This APAR will avoid the additional IS lock on SYSUSERAUTH. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Problem Description above. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V9.1 Fix Pack 10. *
**************************************************************** |
| Local Fix: |
Executing the LOCK TABLE statement as DBADM will not create the
additional lock on SYSUSERAUTH. |
| available fix packs: |
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Solution |
First fixed in DB2 V9.1 Fix Pack 10. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.02.2010
16.06.2011
16.06.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.FP10
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.10
|
 |
