Oracle8 Backup and Recovery - Troubleshooting and Recovery

Audience

Network Administrators Database Administrators Technical Support Analysts System Administrators Application Developers and MIS Managers. Prior to taking this course participants should be familiar with SQL and PL/SQL using Procedure Builder or have taken courses 61110 61111 61112 and 60113. In addition participants should have taken the Oracle8 Database Administration series courses 61311 61312 61313 61314 and 61315 and have taken the first part of the Oracle8 Backup and Recovery series course 61321.

Objective

• Identify the ways of handling different types of errors.
• Diagnose errors and detect corruption by using different tools.
• Understand the recovery process for a database running in noarchive mode and recover a failed database.
• Understand the complete recovery process for a database in archivelog mode and perform complete recovery in various situations.
• Understand the incomplete recovery process for a database in archive mode and perform incomplete recovery in various situations.
• Identify the uses modes levels and compatibility issues of Export utility and use the Export utility to create an export file.
• Identify the uses modes and NLS considerations of the Import utility and the steps in which a table is imported.
• Import objects into a schema.
• Sequence steps to start an Oracle database with a missing data file.
• Identify the methods to enable parallel recovery recover from lost control file Recovery Catalog data file corruptions.
• Identify the features and usage guidelines of standby database.
• Manage standby database and identify the characteristics of the offline data files in a standby database.

Topics Include

Unit 1: Failures and Troubleshooting

• Identify the ways of resolving statement failure.
• Identify the causes of statement failure.
• Identify the ways of resolving user process failures.
• Identify the causes of user process failures.
• Identify the ways of resolving user error failures.
• Identify the causes of user errors failures.
• Identify the recovery process in an instance failure.
• Identify the causes of instance failure.
• Identify the ways of resolving a media failure.
• Identify the causes of media failure.
• Identify a database failure error condition by diagnosing an alert
• Identify the features of an alert file.
• Identify a database failure error condition by diagnosing a trace
• Identify the features of a trace file.
• Identify the use of the checksum parameters.
• Verify the integrity of a data file by using the DBVERIFY utility.
• Identify the features of the DBVERIFY utility.

Unit 2: Oracle Recovery Methods

• Identify the files to be restored for a database in the noarchivelog mode.
• Identify the implications of recovering a database in the noarchivelog mode.
• Recover a failed database in the noarchivelog mode by using the ServerManager.
• Restore a database in noarchivelog mode by using RMAN.
• Identify the syntax of the RESTORE command.
• Sequence the recovery steps for archivelog mode database failure.
• Identify the recovery structures for an archive mode database.
• Identify the implications of archive mode recovery.
• Restore the archived logs to a new location by using the alter system command.
• Recover from a closed database failure.
• Identify the syntax of the recover data file command.
• Locate the data files needing recovery by using the dynamic performance views.
• Recover from an open database failure.
• Recover tablespace syntax.
• Identify the use of the v$datafile view.
• Recover a database from loss of data file that does not have a backup.
• Recover a failed database that had a file in hot backup mode.
• Identify the use of the v$backup view
• Recover from the loss of an online redo log file.
• Perform a complete recovery on an initially open database by using RMAN.
• Identify the use of the Set Newname command.
• Identify the implications of incomplete recovery.
• Identify the reasons for incomplete recovery.
• Identify the different types of incomplete recovery.
• Sequence the steps to perform an incomplete recovery.
• Perform a time-based recovery operation.
• Identify the syntax of the recover command.
• Perform a cancel-based recovery operation.
• Recover using a backup control file.
• Recover from loss of current redo logs in an open database.
• Recover from loss of current redo logs in a closed database.
• Perform an incomplete recovery on an initially open database by using RMAN.

Unit 3: Additional Backup and Recovery Methods

• Identify the uses of the Export and Import utilities.
• Match the levels of full database export with their purposes.
• Identify the three levels of full database export.
• Create an export file by using the command line interface.
• Identify the compatibility issues associated with the Export utility.
• Identify the characteristics of Direct-Path export and invoke Direct-Path export.
• Identify the characteristics of Direct Path Export.
• Invoke direct path export by using the command line interface.
• Identify the uses of the Import utility for recovery.
• Identify the functions of the modes available in the Import utility.
• Identify the modes available in the Import utility.
• Import objects into a schema by using the command line interface.
• Sequence the steps in which a table is imported.
• Identify the NLS considerations for the Export and Import utilities.
• Sequence the steps to start an Oracle database with missing data files.
• Identify the situations when you can start the database with missing data files.
• Identify the methods to enable parallel recovery activities.
• Identify the internal activities involved in the parallel recovery operations.
• Identify the situations when considerations must be taken for Read-Only tablespace recovery.
• Identify the methods to recover from loss of control file.
• Identify the situations in which a DBA is confronted with recovering or recreating control files.
• Identify the recovery methods for a corrupted data file.
• Identify the methods to recreate a lost recovery catalog.

Unit 4: Oracle Standby Database

• Identify the features of a standby database.
• Identify the need of a standby database.
• Identify the guidelines for using a standby database.
• Create a standby database by using Server Manager.
• Identify the steps of synchronizing the standby and primary databases.
• Activate the standby database by using Server Manager.
• Refresh the standby database control file by using Server Manager.
• Identify the implications on the standby database when the physical structure of the primary database is altered.
• Identify the characteristics of the offline data files in the standby database.

Duration

8

Minimum Requirements

The CDROM version of this course requires:

• At least a 486DX 33Mhz CPU.
• Microsoft Windows 3.1 or higher and a Microsoft compatible mouse.
• At least 8MB RAM.
• At least VGA graphics capability with a minimum 512K video RAM (1MB video RAM recommended).
• At least a double speed CDROM drive.
• An MPC compliant sound card with attached speakers or headphones is recommended (Currently only the CDROM version supports audio).

• At least a 486DX 33Mhz CPU.
• Microsoft Windows 3.1 or higher and a Microsoft compatible mouse.
• At least 8MB RAM and 22MB available hard disk space or file server space.
• At least VGA graphics capability with a minimum 512K video RAM (1MB video RAM recommended).

Media

CDROM