Re: Turn Transactions on?

In article <321A00ED.37AF@qadas.com>, Bill Bounds <billb@qadas.com> writes >Darin Strait wrote: >> > > >The question about why the transaction log was not already turned on is >has to do with the standard engine not purging the transaction log >automatically. If the log is left unmonitored in a relatively active >database environment, it can easily fill up available disk space (the >largest I have seen thus far was approx 970 MGs!). > (I've seen 1.8Gb on a 2Gb partition - took > 30 secs to cat /dev/null into it.) >To start transactions, all you have to do is to go into isql or >dbaccess. When prompted for a database name, press <DEL> (or your local >interrupt key) - both dbaccess and isql will then take you into the >query language without a database being selected (you can also use the >close database statement if the database is already selected). The SQL >statement to turn on the transaction log in the standard engine is >simply "start database <databasename> with log in "<full pathname of >logfile>". > For Online first version the version (tbstat -V or onstat -V) if this is 6.00 or above then commands start with 'on' rather than 'tb'. First su to informix then run tbmonitor (or onmonitor), select Paramaters/Archive/Tape Parameters and check all the parameters are correct - - The Tape Device is used for transaction logs. - The Archive Tape Device which is for archives (complete backups). Once tape devicename/sizes are correct run tbtape -s -U <database name> Press 0 for a level-0 (complete archive) then transaction logging will be enabled to the Tape Device. -- David Williams