dbTalk Databases Forums  

it happened, lost database and recovery catalog. starting distasterrecovery research

comp.databases.oracle.misc comp.databases.oracle.misc


Discuss it happened, lost database and recovery catalog. starting distasterrecovery research in the comp.databases.oracle.misc forum.



Reply
 
Thread Tools Display Modes
  #21  
Old   
Frank van Bortel
 
Posts: n/a

Default Re: it happened, lost database and recovery catalog. starting distasterrecovery research - 05-16-2008 , 03:28 AM






neil kodner wrote:
Quote:
On May 14, 8:57 am, Ben <balve... (AT) gmail (DOT) com> wrote:
10.2.0.2 EE, aix5L

had a storm this weekend and power went out to the disk cabinet on our
development machine. I was just informed by our sys admin that we
might be having to recover from disk to get everything back.

Luckily it is just our development machine but we do have critical
data in that database. The recovery catalog was located on the same
machine and filesystem. Now I'm setting forth with the research on how
to get it back. I have documentation of control file backups, the
dbid, and the last hot backup of the database. I don't have a backup
for the recovery catalog that we were using. Correct me if I'm wrong,
but I guess I'll be recovering the control file(s) then recovering the
database from those instead of the catalog. I've practiced recovery in
the past but never without the recovery catalog.

Wish me luck. Any pointers?

Have you tried running an RMAN restore without first connecting to any
catalog? The backup information is also stored in the control files.
We've performed restores while bypassing the recovery catalog.
Which makes sense, as the catalog is no more than
a copy of your control file.

Both of which should be backed up!!!

FvB


Reply With Quote
  #22  
Old   
Frank van Bortel
 
Posts: n/a

Default Re: it happened, lost database and recovery catalog. starting distasterrecovery research - 05-16-2008 , 03:31 AM






Ben wrote:
Quote:
Just curious as to why I would
be better off using a non-recovered control file?

Because it has the latest changes written to it, which
your backed up control file does not. E.g. it knows
it still misses those 13 archived redo log files, due
to log switches *after* the former backup.

FvB


Reply With Quote
  #23  
Old   
Frank van Bortel
 
Posts: n/a

Default Re: it happened, lost database and recovery catalog. starting distasterrecovery research - 05-16-2008 , 03:31 AM



Ben wrote:
Quote:
Just curious as to why I would
be better off using a non-recovered control file?

Because it has the latest changes written to it, which
your backed up control file does not. E.g. it knows
it still misses those 13 archived redo log files, due
to log switches *after* the former backup.

FvB


Reply With Quote
  #24  
Old   
Frank van Bortel
 
Posts: n/a

Default Re: it happened, lost database and recovery catalog. starting distasterrecovery research - 05-16-2008 , 03:31 AM



Ben wrote:
Quote:
Just curious as to why I would
be better off using a non-recovered control file?

Because it has the latest changes written to it, which
your backed up control file does not. E.g. it knows
it still misses those 13 archived redo log files, due
to log switches *after* the former backup.

FvB


Reply With Quote
  #25  
Old   
Frank van Bortel
 
Posts: n/a

Default Re: it happened, lost database and recovery catalog. starting distasterrecovery research - 05-16-2008 , 03:31 AM



Ben wrote:
Quote:
Just curious as to why I would
be better off using a non-recovered control file?

Because it has the latest changes written to it, which
your backed up control file does not. E.g. it knows
it still misses those 13 archived redo log files, due
to log switches *after* the former backup.

FvB


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.