Shrinking Informix transaction logs?
Posted in 1997
Topics: Storage & Space Management, Transactions, Locking & Isolation
We want to use Informix SE in our monitoring application which runs in a 24 hour by 7 day a week environment. In examining the literature it appears that the Informix SE transaction log consumes ever increasing amounts of disk space. This space is only controlled by shutting down and restarting the database. We really don't want to have to periodically shut down the database just to shrink the transaction log. We can live without roll-forward recovery. That is, in the event of a media failure, we are willing to experience data loss by not being able to roll forward from a backup copy of the database. However, we do want to retain roll-back recovery in the event of an application abort or system failure. That is, when the database is opened for the first time after a system crash, we want partial transactions to be rolled-back or backed out of the database. Does anyone know of a way to periodically "shrink" the Informix SE transaction log without actually shutting the database down? Thanks for any replies to: Steve Aldrich aldrich@pacbell.net