|
Problem IC67128
|
Status: Closed |
IN DPF ENVIRONMENT WITHOUT NODE 0, AN SQL STATEMENT THAT PROCEEDS AN IMPORT WITH ALLOW WRITE ACCESS MAY HANG |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problem description: |
If customer is running a DB2 DPF system without node 0, for
example with a db2diag.log entry like this
365 hotel59 0
512 hotel59 1
758 hotel59 2
(without a 0 in the first column), and customer runs an online
import (IMPORT with ALLOW WRITE ACCESS option), then subsequent
SQL statements that do PREPARE or COMMIT or ROLLBACK may hang. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users on DPF system without node 0 and running online *
* import *
****************************************************************
* PROBLEM DESCRIPTION: *
* If customer is running a DB2 DPF system without node 0, for *
* *
* example with a db2diag.log entry like this *
* *
* 365 hotel59 0 *
* 512 hotel59 1 *
* 758 hotel59 2 *
* *
* (without a 0 in the first column), and customer runs an *
* online *
* import (IMPORT with ALLOW WRITE ACCESS option), then *
* subsequent *
* SQL statements that do PREPARE or COMMIT or ROLLBACK may *
* hang. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.8 Fix Pack 3. *
**************************************************************** |
| Local Fix: |
do not use ALLOW WRITE ACCESS option with IMPORT; reconfigure
DB2 DPF system to include node 0 in db2diag.log |
| available fix packs: |
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
|
| Solution |
Problem was first fixed in Version 9.8 Fix Pack 3. At a
minimum, this fix should be applied on the server. |
| Workaround |
see LOCAL FIX |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.03.2010
20.12.2010
20.12.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.3
|
 |
