Help! Database stuck

I have an IDS 7.3 database with buffered logging enabled. While running a large update that caused the logs to grow to slightly under the high water mark an onarchive process kicked in and filled up the logs. Neither of the processes have enough log space to abort and the whole engine is hung. What can I do to get out of this alive? I'd rather not restore from a backup and apply logs. If the big update leaves the data in an inconsistant state this is OK because the column we were updating is new. Do I dare take the database down, or is there a signal I can send to abort one of the transactions without rolling-back? Please email as soon as you can if you have ideas! many thanks, Mike Lester USAA

You can try bouncing the engine and hope there is enough space for the fast recovery to complete and free up space. If not you will have to call tech support. They will dial in and truncate the last log file so that there is room for the fast recovery to unroll the open transactions. You will indeed loose some or all of that update. Art S. Kagel Mike Lester wrote: > I have an IDS 7.3 database with buffered logging enabled. > > While running a large update that caused the logs to grow to slightly > under the high water mark an onarchive process kicked in and filled up the > logs. Neither of the processes have enough log space to abort and the > whole engine is hung. > > What can I do to get out of this alive? I'd rather not restore from a > backup and apply logs. If the big update leaves the data in an > inconsistant state this is OK because the column we were updating is new. > > Do I dare take the database down, or is there a signal I can send to abort > one of the transactions without rolling-back? > > Please email as soon as you can if you have ideas! > > many thanks, > Mike Lester > USAA