Re: Logical Logs problem
Posted in 1997
Topics: Storage & Space Management, Logging & Checkpoints
In article <5buuv0$2bae$2@news-s01.ny.us.ibm.net>, chaiw@ibm.net (Chaiw Kok Kee) wrote: > Don't use tbmonitor to backup logical logs. > Instead, login into informix and run tbtape -a. This won't help if the logs are already full and Online is in recovery state. > > In article <5bksl9$8np@cssun.mathcs.emory.edu>, > odsharma@hclc.hclc-ggn.hcla.com says... > > > >Hi all, > > > >We are developing a project using Informix 5.0 Online and Visual Basic > >4.0. > >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. > > > >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. > > > >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 ) > > > >Is there a way out? Please help. A detailed reply including some > >information on working Logical Logs would be appreciated. > > > >Thanks in advance. > >O D Sharma First things first...first you need to contact Informix to get them to help zap the logical logs for you. After that has been fixed, try to increase the number of logs. If you have a chance to rebuild your online, increase the size of the logs as well. There is no ballpark figure that I know of. What you have to do is monitor the logs as you run your query. Note how long it takes to fill a logical log and how many logs it needs. If it fills up very quickly, create larger logs. If it is a long running transaction, increase the number of logs as well. Next experiment with the long transaction highwater mark setting in the tbconfig. Look out for potential long transaction jobs. Also when using temp files, try specifying WITH NO LONG. Hope this helps. Rgds Alvin -- Alvin Koh <Alvin_Koh@PTS.MOT.COM>