Re: Problem with long transactions

This problem has been discussed here before. It seems that you are running 4.00 version of OnLine. If your are using any later versions 4.10, 5.00 etc then you can set the HIGHWATER marks in your tbconfig file to avoid running out of logical space. With 4.00, When a long SQL transaction does not find enough logical space then it attempts a rollback. (See status "X" in tbstat -u). Using continuous backup does not help because your transaction being incomplete the logs cannot be written onto the tapes. Only solutions are: 1. Reduce the size of your transactions 2. Provide larger Logical log space 3. Upgrade to 4.10+ versions & use HIGHWATER marks Whatever you choose to do, DO NOT KILL a sqlturbo process which is in "X" state or you will trash your database. ======================================================================== Bharat Shah Voice: (508)-663-7570 Unifi Communications Corp. Fax: (508)-663-7543 4 Federal St, Billerica, Mass 01821, USA uunet!bharat@unifi.com ========================================================================