DB2 - Problem description
Problem IC64335 | 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 / 970 - 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 Version 9.7 Fix Pack 2. * **************************************************************** | |
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.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 9.7 Fix Pack 2. At a minimum, this fix should be applied on the server. | |
Workaround | |
see LOCAL FIX | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC67128 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 03.11.2009 08.04.2010 08.04.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 |