Re: OnArchive and logging

> > Here's what we want to do: currently we have logging on, use OnArchive > > to archive different dbspaces to different tapes, turn logging off, > > processes the large amount of data, then turn logging on and do a > > level 0 archive off all dbspaces and continue normal processing. I've > > done this without any problems using OnTape, but I'm unsure how > > OnArchive will deal with this. Also, we're a little concerned about > > there being problems during the weekend processing and having to > > restore from the archive prior to turning logging off. > > See above. Changing the value of LTAPEDEV (from onmonitor--Archive, Tape) to /dev/null and re-initializing (if possible) will throw a "backup" of the log to /dev/null which prevents the necessity of backing up to tape. [I do not know if you actually change the logging status of the database, effectively disallowing transactions (I doubt this is what you mean), or if you just stop backing up the transaction logs.] If you can not afford to re-initialize, then a "nohup ontape -c &" will do it. You can use ontape all you want with onarchive as long as you don't plan to use the tapes/lack of tapes together. The previous response should be thought about: Buy a big, fast tape drive and don't use onarchive, but ontape/onbar. Look at the Exabyte Mammoth. 20 GB native (I get 60) in about 2-3 hours for an ontape. Hope this helps, Rob Donat. -- _________________________________ | Robert Donat | | rdonat@sigg.com | | http://sashimi.wwa.com/~donat | |_______________________________|