RE: Question concerning log files

Thanks, I guess I should have made it clear I was talking about SE. Agreed, Online has various interesting ways of dealing with it. Here's the paradox: How to do a humungous load or re-index one table while others are using the database in loggin mode? Looks like you have to manage the logsize, as in the online /dev/null scenario with logging continuous or in SE by nulling the log every so often. Yours, Nick At 11:47 AM 3/26/98 +-1000, you wrote: >>From the Informix-Online Administrator's Guide Version 5.0 (pg. 3-31) > >To end logging for a database from the command line, execute the following command: > >tbtape -N database > >Also, from what I remember you can also set the LTAPEDEV to /dev/null so that when you execute 'tbtape -c' the logs get cleared out when they are full. > >Rick Pearson. > > >---------- >From: Nick Nobbe[SMTP:nnob@loc.gov] >Sent: Thursday, 26 March 1998 8:46 >To: Leffler, Jonathan; 'informix-list@iiug.org'; 'David Barnish' >Subject: RE: Question concerning log files > >To add more fuel to the fire: > I noticed in some stray Informix documentation for SE 7+ that there is >also the possibility of doing a "start database with no log" feature. Would >this work with SE 5+? It's a much cleaner way. > >Yours, > Nick > >At 11:16 AM 3/25/98 -0800, Leffler, Jonathan wrote: >> >> >>---------- >>From: David Barnish[SMTP:dbarnish@onel.com] >>Sent: Wednesday, March 25, 1998 9:43 AM >> >> >> >> I wonder if someone can help me. I am supporting a product using >>Informix-SE version 5.06.UC1 running on SCO Unix. The logging is enabled >>and it is getting in the way. We don't need any logging but I don't want >>to have to recreate the database without logging. >> My question is this, is it safe to copy /dev/null to the logging >>file in order to clear it out on a periodic basis? Example: "cp >>/dev/null /u/stuff/stuff.log". >> >>JL: Yes, it will be safe enough provided there are no transactions active >>at the time when you clean the transaction log. In other words, if you >>clear out the transaction log when the system is idle, there won't be a >>problem. If you do it while a transaction is active and that transaction >>needs to be rolled back, there will be problems. You should also consider >>whether you should be backing up the log before destroying it. It sounds >>as if you don't think you'll need it, but it should improve your >>recoverability if you do - in theory, at any rate. >> >>Yours, >>Jonathan Leffler (jleffler@visa.com) #include <bother.ms-exchange.h> >> >> >> >********************* >Nick Nobbe >NLS/BPH >Library of Congress >nnob@loc.gov > > > > ********************* Nick Nobbe NLS/BPH Library of Congress nnob@loc.gov