Re: Oracle archive mode and hot backups
Date: Fri, 7 Aug 2009 08:55:12 -0700 (PDT)
On Aug 7, 4:52 am, "stevedhow..._at_gmail.com" <stevedhow..._at_gmail.com> wrote:
> On Aug 6, 8:05 pm, Palooka <nob..._at_nowhere.com> wrote:
> > What a load of bollocks. Sybrand is entirely right. What on earth is the
> > point of putting the database into archivelog mode, and then throwing
> > away the archived logs?
> One case is performance/stress testing a database prior to go-live.
> We didn't care about recovery, but wanted to make sure it looked as
> much like to-be production as possible (other than backing up the logs
> after archiving).
And perhaps they really didn't know the arc volume until they tested. For a new load that may be something only determinable by testing. I've had the same situation. You find out by testing, then you either load in noarchivelog, switch to archivelog and backup, or get more disk, or just don't worry about it and delete them and take a baseline backup when done. Personally, I usually just do the noarchivelog route because it goes much faster, but the DBA may also have other legitimate issues, like measuring I/O saturation. Just like with a DW or any non-transaction based situation, if it takes longer to recover than just reload, recovery can be inappropriate. Which is a polite term for stupid.
-- _at_home.com is bogus. At least at Motel 6, they don't take the light bulbs... http://www3.signonsandiego.com/stories/2009/aug/07/1b7rancho211244-19-youll-get-nothing-and-it/?business&zIndex=145404Received on Fri Aug 07 2009 - 10:55:12 CDT