RE: Logical log sizing

If you are at a late enough version the alarm program to do ontape -a for you. ontape -c doesn't requre a dedicated terminal. You can do an at nowof a script which starts ontape for you send all output and errors to a log file, and when you want it to stop send it a kill -15, do an onmode -l, when you are done backing up the current log it will stop. This has been successful in my experience. Will <carlson1@bellsouth.net> ===== >So then conventional wisdom is to backup early and often when keeping >transaction logs? Makes sense then to create smaller logical log >files. How small should one go and how would this affect performance? >My guess is that performance would be affected a bit like LRU writes vs. >checkpoint writes in this area; a little bit all along as opposed to the >big write after a 10MB (or so) log file gets written to tape or disk. > >BTW, I'd like to fully implement transaction logging . . . . . just need >a way around that onstat -c (dedicated terminal) requirement. > > > >-- >John Carlson >Informix DBA >WHSmith USA > >#include std_disclaimer.h /* These are my opinions, not my company's >opinion */ ------------------------------------------------------------ This e-mail has been sent to you courtesy of OperaMail, as a free service from Opera Software, makers of the award-winning Web Browser, Opera. Visit us at http://www.opera.com/ or our portal at: http://www.myopera.com/ Your free e-mail account is waiting at: http://www.operamail.com/ ------------------------------------------------------------