|
Problem IC97635
|
Status: Closed |
SOME COMPILER REGISTRY VARIABLES MAY NOT TAKE EFFECT IMMEDIATELY WHEN UPDATED WITH THE IMMEDIATE OPTION |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Applications that are already connected while a compiler
registry variable is updated dynamically may see the update only
for the first subsequent statement and loose the update
afterwards. These application needs to disconnect and reconnect
for the update to take effect permanently. A database or
instance restart is not required.
The documented variables affected by this APAR are :
DB2_RESOLVE_CALL_CONFLICT
DB2_SELECTIVITY
DB2_SELUDI_COMM_BUFFER |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users or tools dynamically updating the *
* DB2_RESOLVE_CALL_CONFLICT, DB2_SELECTIVITY or *
* DB2_SELUDI_COMM_BUFFER registry variables. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 LUW Version 10.1 Fix Pack 4 or 10.5 Fix Pack *
* 4. *
**************************************************************** |
| Local Fix: |
Applications that are already holding a connection while an
affected variable is updated dynamically will permanently see
the update only once they disconnect and reconnect. This issue
can also be resolved by installing DB2 LUW 10.1 Fix Pack 4 or
10.5 Fix Pack 4. |
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
|
| Workaround |
The new registry variable value will take effect the next time
the application connects to the database. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.11.2013
19.09.2014
19.09.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
