Re: How to 'clear' the full log dbspace?

On 21 Jan 1997 04:55:54 GMT, vfraenkle@aol.com wrote: >Im Artikel <5buu1g$16o@cssun.mathcs.emory.edu>, xiaodong@secom.co.cn >("alex") schreibt: > >>I'm using Informix Online 5.01 on the SCO 3.2.4. >> >>Yesterday I executed an big transaction process that exceeded my log >>volume, the log was full and everything halted, then I killed the process >>and use 'tbstat -l' to check my log info, finding that almost all log >space >>are 100% full, when I use 'tbtape -s' to backup(the tape device pointed >to >>/dev/null) the log, but the program waits forever... and online server >>could not be brought to online or quiescent mode, only the recovery mode. >> >>Under this situation, how can I init the logspace and bring the server to >>normal state? Maybe I got lucky but I managed to get out of the situation mentioned above. An Informix Online 7.20.UC2 running on SCO Unix halted when it's logical logs where full. I tried logical logs backup using ontape, ontape refused to work, it just went bezerk. I could not kill the ontape process, even Online refused to go into Quiscent mode. I took a chance : I killed the Master Daemon (kill -9 of oninit which has init as it's parent), changed the onconfig file to use /dev/null as the logical log tape device, restarted the engine. Informix restarted in Quiscent mode, telling me the logical logs where full. Then I launched a full database backup (level 0 archive), using ontape -s -L 0. After the backup, I downed Informix, changed the logical log tape device and restared the engine. Informix was back online, everything worked fine, no data lost. Any comments ... Koen Van der Elst Systems Engineer