|
Problem IC79465
|
Status: Closed |
AVOID DEADLOCK BETWEEN CONCURRENT LOADS WHEN DB2_LOAD_COPY_NO_OVERRIDE IS USED |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
A LOAD using COPY NO option (which is the default option on a
recoverable database) calls an internal DB2 function
sqlrlGetTSContents(). Currently sqlrlGetTSContents() is called
even when DB2_LOAD_COPY_NO_OVERRIDE is used -- i.e. even when
the LOAD is not truly a COPY NO LOAD. With this APAR fix, we
will no longer call sqlrlGetTSContents() when
DB2_LOAD_COPY_NO_OVERRIDE is used. This avoids certain deadlock
scenarios between concurrent LOADs into tables that require
integrity checking. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 6 *
**************************************************************** |
| Local Fix: |
SET INTEGRITY ... OFF to the table before performing LOAD |
| available fix packs: |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 Version 9.7 Fix Pack 6 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.10.2011
14.06.2012
14.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
