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

In article <01bc07df$ecbad560$0101a8c0@pentium133>, "B. Wippermann" <b_wippermann@compuserve.com> wrote: >I had the same problem with 4.1 on SNI MX500 two years ago. >There was NO method to restart the database engine without loosing data. > >the 'tbtape -s' solves nothing because it backups only log files with no >open transactions in it. I think In your case all of your log files were >used. the main problem is imho that Online still needs log space to >rollback a transaction, and if there is no space you can restore your >database from your last backup. > >Now I use 7.12 with AIX 4.1.4 and there are some Parameters to avoid this >situation. There is a 'long transaction high watermark' and if your >transaction tries to use more log space it is rolled back. if you set this >parameter too high you get the same problem as with the old version. I >think INFORMIX should write a version where I can roll back ANY >transaction. ( I never heard such problems from ORACLE users ! ) > > > Version > 7.1* has two ways around this: 1- ontape will now allow you to backup the logs even when they are full. 2- If you are using onarchive you must use the ondatartr utility to backup the logs and then catalog them so onarchive will know about them. Matt Bentley mbentley@xmission.com