DB2 FOR LUW / DB2FORLUW / 970 - DB2

Attempting to update database configuration parameters from 
non-DB2 LUW clients will not update as expected in database 
partitioning feature (DPF) environments.  Specifying the 
database partition number in the update statement will not take 
any effect, as well, the update will not propagate to all 
database partitions as it is supposed to by default. 
 
For example, a JDBC application using the JCC Type 4 connection 
to a DB2 v9.7 server that issues UPDATE DB CFG USING 
MON_UOW_DATA BASE via the SYSPROC.ADMIN_CMD() procedure, will 
not have all database partitions updated with the new value. 
Only the single database partition to which the application 
connected will get updated. 
 
The Type 4 connection does not make use of the DB2 LUW client in 
this case, however, if using a Type 2 connection, the problem 
will not be seen since it does make use of the DB2 LUW client, 
and updates will occur as expected.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Non-DB2 LUW clients connecting to DB2 Version 9.7 GA through * 
* to Fix Pack 2 servers using the database partitioning        * 
* feature (DPF) on Linux, Unix and Windows, issuing UPDATE DB  * 
* CFG commands.                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The DB2 Version 9.7 server was not properly checking the     * 
* levels for pre-Version 9.5 clients, hence, inappropriately   * 
* executing logic to treat non-DB2 LUW clients as pre-Version  * 
* 9.5 clients.                                                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply DB2 Version 9.7 Fix Pack 3 or see local fix for other  * 
* suggestions.                                                 * 
****************************************************************

If impacted by this APAR due to the Type 4 connection, switch to 
using the Type 2 connection if possible. Otherwise, update the 
required database configuration parameter on all db partitions 
manually.

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 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
 

Problem is first fixed in DB2 Version 9.7 Fix Pack 3 and all 
subsequent Fix Packs.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC70025 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

16.07.2010
16.09.2010
16.09.2010

9.7.FP3