Re: exp and archive available.... recover table

From: Alexander Skwar <usenet_at_alexander.skwar.name>
Date: Fri, 13 Jul 2007 22:43:42 +0200
Message-ID: <5177969.gtR94mhV5X@m-id.message-center.info>

· joel garry <joel-garry_at_home.com>:

> On Jul 13, 3:00 am, Alexander Skwar <alexan..._at_skwar.name> wrote:
>

>>
>> What I'm now considering to do is, that I'd copy all the .dbf files and
>> also the redo log files. When I have the archived redo log files available,
>> I am able to do a media recovery, aren't I? And I (might) need to do a
>> media recovery, when I try to startup the database and give it .dbf files,
>> which are "hot". Or am I overlooking something again?

>
> NONONONO! Please google about until you find an explanation as to why
> you do not backup redo log files (as opposed to archived log files).

Will do. And I understood, that it makes no sense at all, to not at least put the tablespaces into backup mode.

> The essential problem is that it is unexpectedly easy to get into a
> situation where you overwrite current redo with older, and lose
> transactions you otherwise wouldn't have.

Thanks for the warning. It's warnings like these, which make me turn my head into the RMAN direction even more ;)

>> > To do a hot backup, you need to put the tablespace in backup mode.

>

>> What would happen, if I would NOT do this?

>
> [ long explanation, easy enough to understand ]

Thanks. It really seems that RMAN or at the very least backup mode of tablespaces is the way to go. Thanks again

Alexander Skwar

-- 
I did this 'cause Linux gives me a woody.  It doesn't generate revenue.
(Dave '-ddt->` Taylor, announcing DOOM for Linux)

Received on Fri Jul 13 2007 - 15:43:42 CDT