Re: Recovery FAilure!!!

From: Mark Bluemel <markb_at_pyramid.com>
Date: 1995/06/27
Message-ID: <1995Jun27.082734.20481_at_pyra.co.uk>#1/1


: In comp.databases.oracle gmccalman_at_ivory.trentu.ca (Grace McCalman, Box
: 524, Trent University, Peterborough, (705)740-2337) said: 
:  
:  

: >Enter message text; type CTRL/Z when done.
: >Hi there,
: >I guess you missed the last notice so I sent it again. I have a problem.
: >( this e-mail is really being accessed from South America too!!!)
: >I have a database that is dated Jun 17th. However , the disk with the
 control
: >and redo log files crashed and could not be recovered.
: >So now I have have a database that is more recent than my control and redo
 log
: >files. Have you ever had this problem or have you ever solved this
 problem? I
: >need some answers because I have tried everything! It seems to me that
 Oracle
: >should not have such a control (database dependent on the redo log files)
 when
: >one knows that their database is intact and that redo logs are not
 required for
: >recovery of anykind.
: >A reply or comment would be greatly appreciated.

The comment is - "why did you have a single control file, or multiple control files on a single disk ?".

This is not a flame, more in the hope of reminding people that multiple control files on separate physical disks are essential.

As other posters have suggested, you should be able to use the RESETLOGS option to get around the problems with the redo logs, and you may be able to recover "USING BACKUP CONTROLFILE" - alternatively, if you are using ORACLE 7, you can use "CREATE CONTROLFILE", AFAIR.

When you've got it fixed - take the database down, copy the control file to multiple physical disks and set the INIT.ORA file to point to all the copies ! If you're on ORACLE 7, consider using redo log groups (a mirroring system for redo log files).

--
Mark Bluemel	Unix/Oracle Trainer and Consultant
		My opinions are my own, but I'll share them
		All solutions to problems are offered "as is"
		and without warranty - you have been warned :-)
Received on Tue Jun 27 1995 - 00:00:00 CEST

Original text of this message