|
Problem IT19676
|
Status: Closed |
LOAD SHOULD FAIL WITH SQL6103C IF THE LOCK ESCALATION HAPPENS TO AVOID THE CONCURRENCY ISSUE
|
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
The row lock is required on the catalog table for the current
LOAD code and LOAD should fail with SQL6103C error if the lock
escalation happens and row lock is cleared on the catalog table
to avoid the concurrency issue.
LOAD fails with the following SQL6103C error if the lock
escalation happens after this APAR fix is applied.
SQL6103C An unexpected utility error occurred. Reason code =
"Unable to lock SYSTABLES."
This may happen with small LOCKLIST and LOAD data onto the
partitioned table, specially when it consists of so many
partitions because LOAD requires the partitions number times
rows lock on the catalog tables and the objects.
Therefore, it is recommended to configure enough large
LOCKLIST to avoid SQL6103C on LOAD utility usage. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* LOAD tool user *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.5 FixPack 5 or later *
**************************************************************** |
| Local Fix: |
To configure enough large LOCKLIST to avoid the concurrency
issue with lock escalation during LOAD operation. |
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.03.2017
09.05.2017
09.05.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
