Re: Logical Logs full, can not be freed!!! Need Help, Urgent!!!

Since there is no mention of when you are backing up your logical logs, I think you need to set up a mechanism to do it. Normally, that means running tbtape -a on a terminal (or terminal window) somewhere; it ties up the terminal permanently. Alternatively, if your database isn't important, you can set the logical log backup device to /dev/null, but that is *NOT* recommended for production systems. (However, if you do use /dev/null, you don't have to run tbtape.) Yours, Jonathan Leffler (johnl@informix.com) #include <disclaimer.h> }From ilist@rmy.emory.edu Fri Mar 28 04:57 PST 1997 }From: bipin@sdt.com (Enigma) }Date: Fri, 28 Mar 1997 06:46:18 -0600 }To: Shen Xiaohui <sxh@project-hope.cydf.edu.cn>, informix-list@rmy.emory.edu }Subject: Re: Logical Logs full, can not be freed!!! Need Help, Urgent!!! }X-Informix-List-Id: <list.13761> } }it might be a factor of multiple things. since increasing ur }logs or changing the waterwarks is not helping ur cause, i guess } the problem has more to do with the transactions that ur running. }its my guess that ur running transactions involving lotsa data }manipulation at the same time, which is causes the logs to overflow. }it might not be a product of just one large transaction because }otherwise the long transaction high watermark should have taken care }of it, it has to be multiple transactions involving lotsa inserts/ }updates etc being run at the same time. try to reschedule a few of }ur jobs or turn off the logging on the database while ur doing this }or commit more often. the logs can be cleared off using either }tbtape -a or tbtape -c , but they're only going to get cleared off }if all transactions in them have been committed/rolled back. } } }On Mar 28, 3:56pm, Shen Xiaohui wrote: }} Subject: Logical Logs full, can not be freed!!! Need Help, Urgent!!! }} Dear Sir, }} }} Our Informix Online 5.0 server's logical logs got full abnormally and frequently, }} the whole system was then stopped and we can do nothing to continue but restore }} the whole system and data from Level 0 tape!!! At first, we suspected the }} "inadequate" logical logs. But, when we add logical logs from 20 to 60, the }} situation was the same. We then adjusted Long Transaction high-water mark for 80% }} to 40% and Long Transaction exclusive high-water mark from 90% to 45%, but we can }} not solve the problem. From Administrator's Guide, we know that a logical log can }} be freed only when 1) it has been backed up; 2) All records within the log file }} are associated with closed transactions; 3) The log file does not contain the }} most recent checkpoint record. We suspected the existence of Long Transaction }} which was not closed. But how can we deal with them? Are there any ways that we }} can force the logs cleared? }} }} Any of your suggestions will be greatly appreciated! Also, please tell me the }} email or fax number of Informix headquarters or technique supporter in the US }} that I can contact. }} }} Thanks in advance }} }} Xiaohui Shen }} email: autodept@public2.bta.net.cn }}-- End of excerpt from Shen Xiaohui } } }