home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
14.10.xC11 FixList
12.10.xC16.X5 FixList
11.70.xC9.XB FixList
11.50.xC9.X2 FixList
11.10.xC3.W5 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

Informix - Problem description

Problem IT08572 Status: Closed

DYNAMICALLY MODIFYING AUTO_TUNE AFFECTS THE SETTINGS OF OTHER AUTO_* CONFIG
PARAMS, EVEN IF THEY WERE EXPLICITLY SET IN THE CONF

product:
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10
Problem description:
If an AUTO_* config parameter such as AUTO_REPREPARE is not 
present in the config file--not explicitly set by the user, in 
other words--it is supposed to take the value of AUTO_TUNE, even 
if AUTO_TUNE is modified dynamically. However, if an AUTO_* 
parameter is explicitly set by the user in the config file, the 
value of AUTO_TUNE is not supposed to affect it, even if 
AUTO_TUNE is changed dynamically. 
 
Currently if you have the following in your config file: 
 
AUTO_TUNE 1 
AUTO_REPREPARE 1 
 
and the user runs this command: 
 
onmode -wm AUTO_TUNE=0 
 
the effective value of AUTO_REPREPARE is also set to 0. Because 
it was present in the config file, we should instead continue to 
honor the value set explicitly by the user.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* IDS users who modify AUTO_TUNE dynamically                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to IBM Informix Server 12.10.xC6                      * 
****************************************************************
Local Fix:
Solution
Problem Fixed In IBM Informix Server 12.10.xC6
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.04.2015
09.12.2016
09.12.2016
Problem solved at the following versions (IBM BugInfos)
12.10.xC6
Problem solved according to the fixlist(s) of the following version(s)
12.10.xC6 FixList