IBM Support

IC69999: INCORRECT BEHAVIOUR OF UPDATE DB CFG COMMAND EXECUTING FROM NON-DB2 LUW CLIENTS IN DPF

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

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

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.
    

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

Problem conclusion

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

Temporary fix

Comments

APAR Information

  • APAR number

    IC69999

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-07-16

  • Closed date

    2010-09-16

  • Last modified date

    2010-09-16

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    IC70025

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 September 2010