Re: Can't free logical logs

Sorry but I can't agree with this. Why is the instance down in the first place? Because the DBA did not = configure the system right, or did not keep an eye on it. High water mark = was set too high else the system would have rolled back nicely. It is *not* informix's fault that this has happened. The tbzero facility is a ambulance that Informix has devised simply = because people are always getting themselves into this state. It dives = beneath the covers and directly writes to the underlying system, so there = is no QA, anything could happen, which is why there is no warranty for = it's use and they won't leave it on a client machine, or publish it. But it is *not* informix's problem. It is a DBA issue. If this is = happening often to a production server, then the server is underconfigured,= or incorrectly configured. rgds Peter Tashkoff <tashkop@iname.com> Zespri International Limited Std Disclaimers Apply All rights reserved. No party may use this document to vilify another. Zespri New Zealand Kiwifruit, The World's Finest >>> "Terry R. Gauchat" <tgauchat@jps.net> 21/11/98 12:37:53 >>> This can happen so often that Informix should publish the "tbzero" or = other utility required to terminate the offending transaction and bring up the instance. If a production server is down, 30+ minutes for tech support to fix the problem is too long. ...Terry. -----Original Message----- From: Sunil Thakkar <sunil0@hotmail.com> To: informix-list@iiug.org <informix-list@iiug.org>; sanjit@ccu-sn.in.dhl.com <sanjit@ccu-sn.in.dhl.com> Date: May 20, 1998 10:33 Subject: Re: Can't free logical logs >Sanjit, > >I dont think this will work. > >Once the system is in long transaction - recovery mode then it will >never complete the recovery as there are no free logs to log the >recovery, and till the system completes the recovery we cannot do >anything like this. > >The only alternative is to get the informix tech support to help us out. >I had faced it twice before and both the times they had helped me out in >about 30 minutes. >(this goes against all the theories about informix tech supprt not >providing any support). > >Thanks, >Sunil. > > >From: Sanjit Chakraborty <sanjit@ccu-sn.in.dhl.com> >Date: Wed, 20 May 98 10:48:35 +0530 >To: informix-list@iiug.org=20 >Subject: Can't free logical logs > >Hi Diane, > >Try the following steps - >1. Login as 'informix' and Set proper TBCONFIG. > >2. tbstat -u > take all 'PID' for all users other than root and informix users. > >3. tbmode -z PID > use this individually for all the PIDs. > >4. Login as 'root' and kill and PIDs with -15 option. > kill -15 PIDs > >5. Login as informix , set your TBCONFIG and increase the 'Logical > Log number' with some handful number from 'tbmonitor' for time > being. > >6. tbtape -a > take logical log backup. > >7. tbmode -ky > stop your informix > >8. tbinit > restart informix > >9. Change the logical log number to the previous status. > > >Bye, >Sanjit. >20/05/1998. > >************************ START OF FORWARDED MESSAGE >********************** > >>From : mail>diane.houston@bbc.co.uk=20 >To : informix-list@iiug.org=20 >Subject : Can't free logical logs >Date : 19/05/98 23:44 > > >I am running OnLine 5.01 UDS on HP-UX 9.04. > >I had a problem with all logical logs full due to long transaction. I >was unable to resolve problem by methods from manual and unable take >off-line so I rebooted the system. OnLine now stuck in Recovery mode >although log shows: > > >Tue May 19 17:43:17 1998 > >17:43:17 INFORMIX-OnLine Initialized -- Shared Memory Initialized >17:43:18 Physical Recovery Started >17:43:18 Checkpoint Completed >17:43:18 Physical Recovery Complete: 0 Pages Restored >17:43:18 Logical Log Files are Full -- Backup is Needed > >17:43:19 Logical Log Files are Full -- Backup is Needed > >17:43:20 Logical Log Files are Full -- Backup is Needed > >17:43:21 Logical Log Files are Full -- Backup is Needed> >OnLine seems to think user dianeh still logged in > > USER INFORMATION > > Locks Disk Disk User > PID User Held Reads Writes >Status > > 383 root 0 6 >2 ------D > 0 root 0 0 0 >------D > 0 dianeh 0 0 0 >--T---- > 595 root 0 0 0 >------M > 571 root 0 0 0 >------M > >I have tried tbmode -c since status of log was U-B-L. > >Any other suggestions before I restore. > >Thanks in Advance > > > >Regards >Diane Houston >MedAS >OASIS Application Support >Villiers House, Room 135 >Tel: 19575 > > > > > >______________________________________________________ >Get Your Private, Free Email at http://www.hotmail.com=20 >