Re: Running SE with log files linked to /dev/null

Ron Whiteleather writes: >Jack G. Jolly (jjolly@jjolly.b24b.ingr.com) wrote: >: I have found that an SE db can be run with the transaction log file >: symbolically linked to /dev/null to avoid it "growing without bound." >: Anyone else doing this?? Any "bad things" that coudl happen?? >: >If your main concern is to limit the size of the log file, then simply >cat(1) /dev/null redirected to the log file periodically. If this is >done during a period when no transactions are being processed, no harm >will be done. This alternative will allow you to rollback a transaction, >which in my opinion is 95% of the value of a transaction log, but not >rollforward a database. If you don't need the rollback capability then >get rid of transaction logging and the associated overhead. It seems to me the most sensible approach is to null out your log file immediately after archiving your database to a backup media (since rolling forward your database should be done against a database restored from backup). This gives you appropriate recovery capability, and keeps the log from becoming too large (once you have the database backed up, you do not really need the current contents of the log file anymore). Dave -- Disclaimer: These opinions are not those of Informix Software, Inc. ************************************************************************** "I look back with some satisfaction on what an idiot I was when I was 25, but when I do that, I'm assuming I'm no longer an idiot." - Andy Rooney