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

In article <5hggnq$m84@cssun.mathcs.emory.edu>, Enigma <bipin@sdt.com> writes >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. Correct. Someone must be starting a transaction and not closing it. E.g. A user is in a transaction whilst the screen it waiting for them to type something and then they go to lunch... the logical log containing the open transaction can then not be freed. Try settting Long Transaction high-water mark to 20% and Long Transaction exclusive high-water mark to 25%. IF this doesn't help then use 10% and 15%. Also run onstat -u, ps -ef and who -u to see which users are holding locks whilst idle for a long time. Hopefully you should be able to work out which program has the long transaction. >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 > > -- David Williams