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 IC58990 Status: Closed

ONPARAMS HANGS IF DYNAMIC_LOGS SET TO 0 AND WHEN TRYING TO ADD A LOGICAL
LOG WHILE WAITING FOR NEXT LOG TO BE FREED

product:
IBM IDS ENTRP E / 5724L2304 / B15 - IDS 11.50
Problem description:
Consider LTXHWM and LTXEHWM are configured such that a rollback 
of a long transaction is exhausting the logical log space. If 
DYNAMIC_LOGS is set to 0 and the instance is in a blocked state 
waiting for the next logical log to be freed, onparams cannot 
be used to add a logical log. If such an attempt is made, for 
example by: 
onparams -a -d logspace -i 
it will simply hang.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users on 10.00                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If the user has turned off the Dynamic Log File feature in   * 
* IDS, then its possible that onparams may not be able to add  * 
* a new logical log to the server if the entire logical log    * 
* space in the server is consumed.                             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to 10.00.xC11                                        * 
****************************************************************
Local Fix:
In this situation you need to restart the instance after having 
set DYNAMIC_LOGS parameter in the onconfig file to 1 or 2.
Solution
Problem has been fixed in 10.00.xC11. onparams recognizes this 
condition and will let the user know what needs to be done.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.11.2008
17.06.2009
17.06.2009
Problem solved at the following versions (IBM BugInfos)
10.00.xC11
Problem solved according to the fixlist(s) of the following version(s)
10.0.xC10.W2 FixList
10.0.xC11 FixList