Re: Current Redo got deleted
Date: Tue, 24 Mar 2015 05:27:28 -0500
Message-ID: <CAHSa0M3WEcJk8kzwXkpffDM17t18FX5L52ZuKUCqh100dAi1Pg_at_mail.gmail.com>
Maybe I should have phrased it differently. I fully agree that #2 in Gopal's steps is needed, especially while recovering from a big error. I am trying to learn how to do this for big DBs or even medium DBs where there is only space for the DB and the backup only in the server.
Years ago we hit a scenario where we had to do the recovery. We did the #2.
Files were in cooked FS visible in the OS. Making copies was easy. The DB
was also very small (IIRC about 40GB).
The same DB has grown bigger and is now inside ASM. I have not even
thought about how I would go about copying files in an emergency.
On Mon, Mar 23, 2015 at 11:33 PM, MARK BRINSMEAD <mark.brinsmead_at_gmail.com> wrote:
> That one can be a tough call, to be sure.
>
> But the screams of the users will be *nothing* compared to the screams of
> management (or investors) if somebody makes a mistake while "recovering"
> from this error and renders the entire database unusable, and there is no
> way to undo it because somebody was in too big a hurry to make a backup.
>
> At the very least, the backup gives you something to do (and something you
> can show your manager/client/users you are doing) while you wait for
> Oracle Support to respond to your SEV-1 SR. At best, it might save you
> from turning an "accident" into an outright "catastrophe".
>
>
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Mar 24 2015 - 11:27:28 CET