RE: Inheriting a "interesting" recovery process
- From: "Bobak, Mark" <Mark.Bobak@xxxxxxxxxxxxxxx>
- To: <Rodd.Holman@xxxxxxxxx>, <niall.litchfield@xxxxxxxxx>
- Date: Fri, 4 Aug 2006 12:30:51 -0400
Hmm...in this case, since you already have EMC, I'd look at doing a
re-startable snapshot (EMC takes a copy of all datafiles, controlfiles
and on-line redo). On restore, Oracle does instance recovery and you're
up and running. If you take one of these snapshots daily, after each
data load, and you're covered. No archivelog mode necessary.
Just a thought....
-Mark
--
Mark J. Bobak
Senior Oracle Architect
ProQuest Information & Learning
Ours is the age that is proud of machines that can think and suspicious
of men who try to. --H. Mumford Jones, 1892-1980
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Rodd Holman
Sent: Friday, August 04, 2006 12:26 PM
To: niall.litchfield@xxxxxxxxx
Cc: stephenbooth.uk@xxxxxxxxx; jkstill@xxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: Re: Inheriting a "interesting" recovery process
Here's a different situation for you:
1.5TB Data warehouse. Loads are the only transaction activity on the
db. These happen once a day every night. Disk system is EMC
Symetrix/DMX on fibre channel. It is quicker and easier to do a
shutdown and BCV split once a week than to maintain the db in ARCHIVELOG
mode. We can recover a from a BCV split and run loads quicker than
applying logs back to the db. Also don't have the space issue of logs
then. Not running arch process either. (Yes the BCV cut is taken to
tape after it's made -- we're not nuts yet).
Niall Litchfield wrote:
> On 8/4/06, stephen booth <stephenbooth.uk@xxxxxxxxx> wrote:
>>
>> On 04/08/06, Jared Still <jkstill@xxxxxxxxx> wrote:
>> > On 8/4/06, Guerra, Abraham J <AGUERRA@xxxxxxxxx> wrote:
>> >
>> > >
>> > > Your very best friends are: 'Cold Backup' (hot whenever you
>> > > can't do
>> > > colds) and make sure your database is in archivelog mode if you
>> > > want full recovery...
>> >
>> >
>> > Please explain why a cold backup is necessary.
>> >
>>
>> Clearly you have never heard a system administrator utter the phrase:
>> "But, they were only logfiles. We needed to clear some space."
>> coupled with "We don't backup logs."
>>
>> With a cold backup you *know* that you can get the database back in a
>> working state, even if some sysadmin has gone nuts and earned
>> themselves a place in a large body of water encased in chicken wire
>> with some heavy weights for company.
>
>
>
> With a hot backup you also *know* that you can get the database back.
> There is no difference. Now if you are going to suggest that after
> sysadmins delete part or all of a backup to save space then you have
> problems, well obviously I agree. The same however surely applies to
cold backups as well.
>
>
>
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
