« The Grid Control Implementation Challenge | Main | Rman Behaviour with Transported Tablespaces Plugged -In Read-Only »

Back to Work, Crash Scenario 1 Datafile loss

We had Holidays in Israel and after that I have attended an Application Server 10g R2 Administration course in Barcelona.

Now back to work I started to recover and document a set of Crash Scenarios that were destroyed during a round of implementation.

The Crash Scenarios were developed to be run by DBA's that are not familiar with RAC 10g and Rman, so they can test and solve production situations later, with confidence.

The crash scenarios consist of a crash script, that actually executes the scenario, produces the crash, and a set of guidelines to recover from it.

Crash Scenario 1 is simple:

  • The database crash,
  • A tablespace is deleted from ASM while the database is down,
  • The database fail to start
  • The datafiles from the tablespace needs to be recovered using an rman backup.
The recover steps includes
  • Startup mount
  • Invoke rman
  • Restore datafile
  • Recover datafile
  • Open the database
Complete details on this document: Crash Scenario 1: Datafile Loss

TrackBack

TrackBack URL for this entry:
http://blogs.oracle.com/mte1521/mt-tb.cgi/4332

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

About This Entry

This page contains a single entry from the blog posted on April 30, 2007 3:54 AM.

The previous post in this blog was The Grid Control Implementation Challenge.

The next post in this blog is Rman Behaviour with Transported Tablespaces Plugged -In Read-Only.

Many more can be found on the main index page or by looking through the archives.

Top Tags

Powered by
Movable Type and Oracle