Re: to many logical logs: cannot restart database

Fred Bon <fred@toplog.fr> wrote: >-- >on informix online v5.05.uc2, >when I try to restart the database in quiescent mode, the database is in >recovery mode and stop. It seems there is too many logical logs. >Previously, a process has last very long and was killed (kill -9) >How can I erase these logs ?? >please send me the answer by mail fred@toplog.fr, thanks >------------------------------------------------------------------------------ >Fred BON - Top Log Technologies >Mail: fred@toplog.fr - URL:<http://www.toplog.fr>; >------------------------------------------------------------------------------ If this is caused due to a long transaction then Informix can dial in and run a utility to get you out of this. They will not insure data Integrity when they do this though. To prevent this in the future I would check my long transaction high water mark in the tbconfig file with 5.x the default is 90/80 which is not the recommended setting from Informix. With the newer products it is set at 60/50 for the long transaction exclusive high water mark and the long transaction high water mark respectively. If it is a transaction you must run you can add more logical logs. To do this you need to make sure you have room in the logical log dbspace or add some space to it. Bring the engine into quiesent mode. Use the tbparams or tbmonitor to add logical logs (as many as you have room for) and then do a level 0 backup and bring the enging online. (For 5.x you must make sure that the logsmax parameter is big enough for the number you want to add. If not update the logsmax parameter and bring the engine offline and then bring it to quiescent before attempting to add the logs.) -- Tolly Brumbelow, Informix DBA email:tolly.brumbelow@bridge.bellsouth.com