Oracle RMAN 11g Backup and Recovery (105 page)

187 HIGH OPEN 09-JUN-09 One or more non-system

datafiles are missing

Do you really want to change the above failures (enter YES or NO)? yes

changed 1 failures to LOW priority

NOTE

You cannot switch the status of a CLOSED failure to OPEN.

Data Recovery Advisor Data Dictionary Views

Several new views have been added to Oracle Database 11
g
to support the Data Recovery Advisor. These views start with V$IR as seen in this table:

View Name

Description

V$IR_FAILURE

Provides information on the failure. Note that records in this

view can have parent records within this view.

V$IR_FAILURE_SET

This table provides a list of the various advice records

associated with the failure. This allows you to join the view

V$IR_FAILURE to the V$IR_MANUAL_CHECKLIST view.

V$IR_ MANUAL_CHECKLIST

This view provides detailed informational messages related

to the failure. These messages provide information on how to

manually correct the problem.

V$IR_REPAIR

This view, when joined with V$IR_FAILURE and V$IR_

FAILURE_SET, provides a pointer to the physical file created

by Oracle that contains the repair steps required to correct a

detected error.

Here is an example of a query against the DRA views:

-- Do we have an open error reported?

select failure id, time detected, description from v$ir failure

Where status 'OPEN';

FAILURE ID TIME DETE DESCRIPTION

---------- --------- ----------------------------------------

242 19-SEP-07 One or more non-system datafiles are missing

605 19-SEP-07 Datafile 4: '/oracle01/oradata/orcl/user

s01.dbf' is missing

Chapter 12: RMAN Restore and Recovery
303

Summary

In this chapter, we have looked at the basics of recovering your database with RMAN. We have looked at the many different ways that you can recover your control files and SPFILEs. We have also looked at restoring and recovering your databases from RMAN backups with the
restore
and
recover
commands. We have discussed the different recovery options available, from full database recovery to recovery of specific tablespaces or datafiles. Finally, we have provided some workshops for you to practice your newly learned recovery skills.

We want to leave you with one big piece of advice at the end of this chapter. Practice recoveries, over and over and over. Know how RMAN works and how to recover your database without having to use this book. Become the RMAN expert in your place of work. Then you are poised to be the hero!

This page intentionally left blank

PART

III

Using RMAN Effectively

This page intentionally left blank

CHAPTER

13

Using Oracle Enterprise

Manager for Backup and

Recovery

308
Part III: Using RMAN Effectively

p to this point, we have provided guidance on interacting with RMAN strictly from the RMAN client utility. Hopefully, this has enabled you to build some confidence using the RMAN command-line syntax. It is critical to become

U
comfortable with this syntax because you will encounter situations in which the command-line syntax of RMAN is the only thing available to get you through a painful downtime.

Oracle does provide a toolset for monitoring all the databases throughout your business, and this toolset includes a graphical user interface for taking backups and performing recoveries. This product, collectively referred to as Oracle Enterprise Manager (OEM), has existed in one form or another since 1998. For most of its history, it has been available as a Java application that could be installed on a client system and used to monitor and administer remote databases.

However, starting in 10
g,
Enterprise Manager (EM) underwent a radical transformation that moved it from primarily a desktop application to a fully functional web application. From the early 10
g
Release 1 (10
g
R1) days, this new EM has been consistently upgraded so that nearly all functionality that is available at the command line is now also available from any Internet browser. To put it mildly, this changes the game.

Oracle Enterprise Manager: The New Paradigm

Oracle engineered OEM specifically to embrace the new paradigm of enterprise computing, often referred to as the grid. Oracle built OEM to tame the management chaos unleashed by grid computing. Grid computing enables many compelling business advances, providing an always-up, highly redundant, commodity-based, service-oriented environment in which to deploy enterprise computing resources (enough buzzwords for you?). We have already seen its principles deployed at customer sites, and grid computing is powerful. But it is also complicated.

To contrast traditional enterprise computing and grid computing, it helps to look at some example environments. First, consider the simplified scenario of a traditional enterprise environment shown in Figure 13-1. Configuring this database environment includes the following:

■ Requisition as powerful a computer as can be found.

■ Manage as small a list of computers as can be reasonably grouped.

■ Manage multiple databases on a single computer.

■ Segregate data by division and function.

■ Assign a highly ritualized set of responsibilities to each professional segment (network admin, system admin, database admin, etc.).