Re: Logical Logs problem

richardt@TheMusicStore.co.uk (Richard Thomas) wrote: :Hi, you have my sympathy! :On Thu, 16 Jan 1997 odsharma@hclc.hclc-ggn.hcla.com wrote: :... :> We are facing a problem quite frequently. Informix goes in 'recovery :> mode' fails to become online saying that logical logs are full. Usually :> this happens if server goes down due to some problem. :Had the same thing with OnLine 5.03 (maybe more details in a later :posting). :> :> We have 5 logical logs. Each logical log file is of size 1500K. :> Size of logical log buffers is 32K. :> Size of root dbspace is 20000 pages and a BlobSpace of 10000 pages ( :> page size 2K). :> "tbstat -l" shows 100% full for lal the logs. :> Logical log tape device pathname & Archive tape device pathname is :> /dev/null. :Are you sure about this? If the logical log device is /dev/null, the :logs should trundle away forever without any problem. Even if the logical log tape device is /dev/null the logs can still fill up due to a long transaction as I understand this. I haven't ever tested that. The /dev/null device only says that the engine should work as if continous log backups where run, but the data should be dumped into nowhere land. Even if you do run continous logical log backups (to some tape device) you still can get a long transaction that can't be rolled back and crashes the enging, so there is no reason I can see why you can't get this with /dev/null as the backup device. :> :> When we try to take backup it just goes into a wait state and does not :> come out. The status id shown as 'recovery' all the time. ( Device :> /dev/null is working fine ) It isn't usefull for any purpose (other than if you want to switch loging type on the database) to try a backup, neither logical log backup or a regular backup, if your backup devices are set to /dev/null :> :> Is there a way out? Please help. A detailed reply including some :> information on working Logical Logs would be appreciated. ...previous good answer sniped... Others know more about logical logs than me, but for the future (not to solve your problem of restarting the engine) you have to make sure both that you have enough logical log space, and equally important that the parameters for rollback are set appropriately. There have been many discussions on this that you may be able to find in the archives or at dejanews. Nils.Myklebust@idg.no NM Data AS, P.O.Box 9090 Gronland, N-0133 Oslo, Norway My opinions are those of my company The Informix FAQ is at http://www.iiug.org