01.09.2016 Views

Beginning Oracle Database 11g Administration From Novice to Professional

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

292<br />

CHAPTER 13 RECOVERY<br />

Figure 13-2. SQL Developer error dialog<br />

The <strong>Oracle</strong>- recommended action was “Try <strong>to</strong> res<strong>to</strong>re the segment containing the<br />

block indicated. This may involve dropping the segment and re- creating it. If there is a<br />

trace file, report the error in it <strong>to</strong> your <strong>Oracle</strong> representative.” But DRA makes short work<br />

of the problem.<br />

First, let’s check whether any other blocks are also corrupted. That seems like the<br />

smart thing <strong>to</strong> do—if one block has somehow been corrupted, then other blocks might<br />

also have been corrupted, and we could fix all of them at the same time. We use the<br />

command <strong>to</strong> check the entire database. (Note that checking the entire<br />

database may take a lot of time, and Recovery Manager does provide the ability <strong>to</strong> check<br />

individual data files.) Fortunately, we find that the only block that is corrupted is block 88<br />

in the file :

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!