|
Problem IC64905
|
Status: Closed |
Load utility with COPY YES can trap in rare timing scenarios. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
The Load utility when invoked with the COPY YES option, may trap
or fail in very rare timing scenarios. The trap or failure may
have different signatures, but one such signature would be a
db2diag.log message such as:
2009-11-24-11.03.18.377754-300 I541128E585 LEVEL:
Error
PID : 12286 TID : 47630323280192 KTID :
15378
PROC : db2sysc 0
EDUID : 360 EDUNAME: db2lbm0 0
FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0
DATA #1 : String, 149 bytes
LOADID: 171.2009-11-24-11.03.02.577583.0 (65530;32768)
Cannot set direct write CB - logic error. , 32, 0x8000, Detected
in file:sqlulbuf.C, Line:2513
A higher probability of hitting the problem with MDC/RP tables,
low available memory, and logical DPF setup/high
system CPU load. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* The Load utility when invoked with the COPY YES option, may *
* trap *
* or fail in very rare timing scenarios. The trap or failure *
* may *
* have different signatures, but one such signature would be a *
* *
* db2diag.log message such as: *
* *
* *
* *
* 2009-11-24-11.03.18.377754-300 I541128E585 LEVEL: *
* *
* Error *
* *
* PID : 12286 TID : 47630323280192 KTID : *
* *
* 15378 *
* *
* PROC : db2sysc 0 *
* *
* *
* *
* EDUID : 360 EDUNAME: db2lbm0 0 *
* *
* FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0 *
* *
* DATA #1 : String, 149 bytes *
* *
* LOADID: 171.2009-11-24-11.03.02.577583.0 (65530;32768) *
* *
* Cannot set direct write CB - logic error. , 32, 0x8000, *
* Detected *
* in file:sqlulbuf.C, Line:2513 *
* *
* *
* *
* A higher probability of hitting the problem with MDC/RP *
* tables, *
* low available memory, and logical DPF setup/high *
* *
* system CPU load. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to product version 9.7 fixpack 2 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.7 fixpack 2
The fix should be applied on the server |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.12.2009
26.01.2010
26.01.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
