Re: BAARF - true life story

  • From: Jared Still <jkstill@xxxxxxxxxx>
  • To: Oracle-L Freelists <oracle-l@xxxxxxxxxxxxx>
  • Date: Sun, 08 Aug 2004 15:26:10 -0700

On Sat, 2004-08-07 at 12:18, solbeach@xxxxxxx wrote:

> We now have to move this whole database (178GB) to a new 
> system, with minimal downtime.
> 
...
> What would YOU do given this history & requirements?
> 

Just off the top of my head, without giving it a 
great deal of thought ( that's your job :)

* hot backup the database to another server ( manual 
scripts or RMAN, your choice )

* recover it to the current set of arhive logs, 
shut it down, and run dbverify on all data files

* continue if all is ok.  If not ok, well then,
you gotta figure out which blocks are bad and
attempt to recover them

* recover the new database to the current set of 
archive logs, shutdown the old database, startup
restrict, switch logfiles, shutdown the database
and apply the final archive log file to the
new database.

* this doesn't cause much downtime.  10 minutes or
so if you test it first and write down exact
instructions.

* test this before doing it for real


Jared


----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to:  oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Other related posts: