> ----- Original Message ----- > To: "SQL 7 Discussions" <[EMAIL PROTECTED]> > Sent: Tuesday, February 19, 2002 5:29 PM > > *When txn log fills up, have to just "truncate" the log in order for > processing to continue. Leaves system vulnerable until you get a full DB > backup. > >>>>>> Seems a little like disk space filling up in Oracle. How is this > >>>>>> different?
Interesting. When this happened to us Oracle-wise, I just moved the oldest archives to a mount point that did have enough room. Since we at least had enough forethought to incorporate several redo log groups, the DB never stopped. And since we never actually deleted any archive logs, we were never at great risk of permanent loss of data. Or we could have also duplexed the arches offsite, too. Because we all know that RAID controllers NEVER fail... "Truncate the log." Yeah, right. Ya know, as much as I have whined about the way Oracle does some things (e.g. stupid-ass security-by-obscurity for DBAs and some wierd things with OiD), I still think it's the best yet available. Rich Jesse System/Database Administrator [EMAIL PROTECTED] Quad/Tech International, Sussex, WI USA -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Jesse, Rich INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
