|
Problem IC69999
|
Status: Closed |
INCORRECT BEHAVIOUR OF UPDATE DB CFG COMMAND EXECUTING FROM NON-DB2 LUW CLIENTS IN DPF |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
****************************************************************
* 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. *
**************************************************************** |
| Local Fix: |
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. |
| available fix packs: |
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
|
| Solution |
Problem is first fixed in DB2 Version 9.7 Fix Pack 3 and all
subsequent Fix Packs. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC70025
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.07.2010
16.09.2010
16.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
