01.09.2016 Views

Beginning Oracle Database 11g Administration From Novice to Professional

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

CHAPTER 13<br />

Recovery<br />

These Officers, with the Men belonging <strong>to</strong> the Engine, at their Quarterly Meetings,<br />

discourse of Fires, of the Faults committed at some, the good Management in some<br />

Cases at others, and thus communicating their Thoughts and Experience they grow<br />

wise in the Thing, and know how <strong>to</strong> command and <strong>to</strong> execute in the best manner<br />

upon every Emergency.<br />

—Benjamin Franklin, in a letter <strong>to</strong> the Pennsylvania Gazette,<br />

following a disastrous fire in Philadelphia in the 18th century<br />

In the previous chapter, you learned how <strong>to</strong> make backup copies of the database. You<br />

will now turn your attention <strong>to</strong> repairing the database if it gets damaged. For the purposes<br />

of this chapter, you should assume the availability of backup copies made using<br />

Recovery Manager (RMAN) but you will discover that backup copies are not the only<br />

repair option available. You will also get acquainted with a powerful <strong>to</strong>ol called Data<br />

Recovery Advisor (DRA), which greatly simplifies the database administra<strong>to</strong>r’s job.<br />

Horror S<strong>to</strong>ries<br />

The following are true s<strong>to</strong>ries based on personal experiences.<br />

Sometimes we make a mountain out of a molehill. Early in my career, in the days of<br />

<strong>Oracle</strong> 7, a few blocks of data in the company’s most critical database were found <strong>to</strong> be<br />

corrupted. Any transaction that <strong>to</strong>uched the affected blocks could not complete, but the<br />

database was otherwise functional. This was a large Enterprise Resource Planning (ERP)<br />

database that the business depended on for all aspects of its functioning, so the application<br />

administra<strong>to</strong>rs went in<strong>to</strong> high gear. There were no disk backups because of the sheer size<br />

of the database, so the application administra<strong>to</strong>rs recalled the tapes from the offsite s<strong>to</strong>rage<br />

facility. They shut down the database at the end of the day and began res<strong>to</strong>ring it from<br />

tapes, hoping <strong>to</strong> have the database ready for business the next day. However, three- quarters<br />

of the way in<strong>to</strong> the res<strong>to</strong>re operation, a defect was found in the tapes and the application<br />

administra<strong>to</strong>rs had <strong>to</strong> requisition the previous set of tapes from the offsite s<strong>to</strong>rage facility.<br />

The offsite s<strong>to</strong>rage facility was 100 miles away, and this necessitated a substantial delay.<br />

279

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

Saved successfully!

Ooh no, something went wrong!