Performing Database Recovery

Copyright © 2007, Oracle. All rights reserved.

 Objectives

After completing this lesson, you should be able to:

• Determine the need for performing recovery
• Access different interfaces (such as Enterprise
Manager and command line)
• Describe and use available options, such as Recovery
Manager (RMAN) and the Data Recovery Advisor
• Perform recovery:
– Control file
– Redo log file
– Data file

16 - 2 Copyright © 2007, Oracle. All rights reserved.

 Opening a Database

To open a database:
• All control files must be present and synchronized
• All online data files must be present and synchronized
• At least one member of each redo log group must be
present

OPEN
STARTUP
MOUNT

NOMOUNT

SHUTDOWN

16 - 3 Copyright © 2007, Oracle. All rights reserved.

 Keeping a Database Open

After the database is open, it fails in the case of the loss

of:
• Any control file
• A data file belonging to the system or undo tablespaces
• An entire redo log group
(As long as at least one member of the group is
available, the instance remains open.)

16 - 4 Copyright © 2007, Oracle. All rights reserved.

 Data Recovery Advisor

• Fast detection, analysis, and repair of failures

• Down-time and run-time failures
• Minimizing disruptions for users
• User interfaces:
– Enterprise Manager
GUI (several paths)
– RMAN command line
• Supported database configurations:
– Single instance
– Not RAC
– Supporting failover to standby, but not analysis and
repair of standby databases

16 - 5 Copyright © 2007, Oracle. All rights reserved.

16 - 6 Copyright © 2007, Oracle. All rights reserved.
 Loss of a Redo Log File

If a member of a redo log file group is lost and if the group

still has at least one member, note the following results:
• Normal operation of the instance is not affected.
• You receive a message in the alert log notifying you
that a member cannot be found.
• You can restore the missing log file by copying one of
the remaining files from the same group.

16 - 7 Copyright © 2007, Oracle. All rights reserved.

 Loss of a Data File
in NOARCHIVELOG Mode

If the database is in NOARCHIVELOG mode and if any data

file is lost, perform the following tasks:
1. Shut down the instance if it is not already down.
2. Restore the entire database—including all data and
control files—from the backup.
3. Open the database.
4. Have users reenter all changes that were made
since the last backup.

User User User User User

16 - 8 Copyright © 2007, Oracle. All rights reserved.

 Loss of a Noncritical Data File
in ARCHIVELOG Mode

If a data file is lost or corrupted, and if that file does not

belong to the SYSTEM or UNDO tablespace, you restore and
recover the missing data file.

Users

16 - 9 Copyright © 2007, Oracle. All rights reserved.

 Loss of a System-Critical Data File
in ARCHIVELOG Mode

If a data file is lost or corrupted, and if that file belongs to

the SYSTEM or UNDO tablespace, perform the following
tasks:
1. The instance may or may not shut down automatically.
If it does not, use SHUTDOWN ABORT to bring the
instance down.
2. Mount the database.
3. Restore and recover the missing data file.
4. Open the database.

Users

16 - 10 Copyright © 2007, Oracle. All rights reserved.

16 - 11 Copyright © 2007, Oracle. All rights reserved.
 Assessing Data Failures

1 Database instance health 3 Problem details

... 2 Error link

16 - 12 Copyright © 2007, Oracle. All rights reserved.

 Data Failures

16 - 13 Copyright © 2007, Oracle. All rights reserved.

 Data Failure: Examples

• Inaccessible components: Missing data

files at the OS level, incorrect access
permissions, offline tablespace
• Physical corruptions: Block checksum failures,
invalid block header field values
• Logical corruptions: Inconsistent dictionary;
corrupt row piece, index entry, or transaction
• Inconsistencies: Control file older or newer
than the data files and online redo logs
• I/O failures: Limit on the number of open files
exceeded, inaccessible channels, network or I/O error

16 - 14 Copyright © 2007, Oracle. All rights reserved.

 Listing Data Failures

16 - 15 Copyright © 2007, Oracle. All rights reserved.

 Advising on Repair

(1) After manual repair

(2) Automatic repair

2a

2b

16 - 16 Copyright © 2007, Oracle. All rights reserved.

 Executing Repairs

. . . in less than
1 second

16 - 17 Copyright © 2007, Oracle. All rights reserved.

16 - 18 Copyright © 2007, Oracle. All rights reserved.
 Summary

In this lesson, you should have learned how to:

• Determine the need for performing recovery
• Access different interfaces (such as Enterprise
Manager and command line)
• Describe and use available options, such as Recovery
Manager (RMAN) and the Data Recovery Advisor
• Perform recovery:
– Control file
– Redo log file
– Data file

16 - 19 Copyright © 2007, Oracle. All rights reserved.

 Practice 16 Overview:
Performing Database Recovery

This practice covers recovering from the loss of a:

• Control file
• Redo log file
• Noncritical data file
• System-critical data file

16 - 20 Copyright © 2007, Oracle. All rights reserved.