|
Problem IC65846
|
Status: Closed |
LOCK TABLE CREATES AN IS LOCK ON SYSIBM.SYSUSERAUTH IN ADDITION TO THE TABLE LOCK REQUESTED |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - 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 AFFETCED:
All
PROBLEM DESCRIPTION:
See ERROR DESCRIPTION
PROBLEM SUMMARY:
See ERROR DESCRIPTION |
| Local Fix: |
Executing the LOCK TABLE statement as DBADM will not create the
additional lock on SYSUSERAUTH. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.5 Fix Pack 6. |
| Workaround |
See LOCAL FIX. |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC66073 IC66074
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.01.2010
10.09.2010
10.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
