Oracle9i Database Administration: Recover Databases

Audience

The intended audience for this course include Database Administrators IT managers and technical professionals. There are no required prerequisites.

Objective

• Identify the files to be restored for a database in the NOARCHIVELOG mode.
• Store the archived logs in a new location using the ALTER SYSTEM command.
• Perform a offline database recovery.
• Recover a database that failed due to the loss of a data file without a backup.
• Perform a timebased recovery operation.
• Recover a database that has failed due to the loss of current redo logs in an online database.
• Create an export file using the command line interface.
• Import objects into a schema by using the command line interface function.

Topics Include

Unit 1: 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 database in the NOARCHIVELOG mode by using SQL*Plus.
• Restore a database in the NOARCHIVELOG mode by using RMAN.
• Sequence the steps to recover a failed database when it is in the ARCHIVELOG mode.
• Store the archived logs in a new location by using the ALTER SYSTEM command.
• Perform a offline database recovery by using SQL*Plus.
• Perform an online database recovery by using SQL*Plus.
• Recover a database that failed due to the loss of a data file that does not have a backup by using SQL*Plus.
• Recover a database that contained a file in the hot backup mode by using SQL*Plus.
• Recover a database that failed due to the loss of an online redo log file by using SQL*Plus.
• Perform a complete recovery on an online database by using RMAN.
• Identify the implications of an incomplete recovery.
• Sequence the steps to perform an incomplete recovery.
• Perform a time-based recovery operation by using SQL*Plus.
• Perform a cancel-based recovery operation by using SQL*Plus.
• Recover from a backup control file by using SQL*Plus.
• Recover a database that has failed due to the loss of current redo logs in an online database by using SQL*Plus.
• Recover a offline database that has failed due to the loss of current redo logs by using SQL*Plus.
• Identify the key features of RMAN.
• Match the Recovery Manager command to its corresponding description.
• Identify the naming structure used by RMAN when automatic channels are created.
• Identify Oracle compliant media management software.
• Match the recovery manager database with its corresponding description.
• Identify the difference between the RMAN batch mode and interactive mode.
• Identify the packages RMAN uses to maintain and query information in the recovery catalog and control file.
• Enter the appropriate stand-alone command at the RMAN prompt.
• Recover a specific data file using the UNTIL TIME method.
• Perform a cancel-based recovery using the UNTIL TIME method.

Unit 2: Additional Backup and Recovery Methods

• Identify the uses of the Export and Import utilities.
• Identify the functions of the modes available in the Export utility.
• Match the full database export levels with their purposes.
• Create an export file by using the command line interface.
• Identify the compatibility issues associated with the Export utility when used with other versions.
• Perform a tablespace point in time recovery (TSPITR) using a transportable tablespace.
• Match the recovery command with its description.
• Identify the characteristics of the Direct-Path export.
• Invoke the Direct-Path export by using the command line interface.
• Identify the uses of the Import utility for recovering data.
• Identify the functions of the Import utility modes.
• Import objects into a schema by using the command line interface function.
• Sequence the steps in which a table is imported.
• Identify National Language Set considerations for the Import utility.
• Set the fast-start rollback parameter to HIGH using the Enterprise Manager Console.
• Sequence the steps to start an Oracle database with a missing data file.
• Identify the methods to begin parallel recovery operations.
• Identify the considerations to be taken when performing a read-only tablespace recovery.
• Identify the methods used to recover the control file.
• Identify the recovery methods used to recover a corrupted data file.
• Identify the methods used to re-create a lost recovery catalog.
• Generate a report with the given requirements by using the REPORT command.
• Generate a report with the given requirements by using the LIST command.
• Select the situations in which a recovery catalog is used.
• Identify the guidelines for creating a recovery catalog.
• Sequence the steps to create a recovery catalog.
• Select the control file characteristics that help in backup and recovery.
• Register a database in the recovery catalog by using RMAN.
• Reset the recovery catalog information to reflect the current state of the target database by using RMAN.
• Select the situations in which the recovery catalog must be resynchronized.
• Record information in the recovery catalog by using the CATALOG command.
• Maintain a recovery catalog by using the CHANGE command.
• Perform the operations to manage channel allocations.
• Identify the options for re-creating a recovery catalog.
• Write the commands to display information from the recovery catalog by using data dictionary views.

Unit 3: Failures and Troubleshooting

• Identify the methods for resolving statement failure.
• Identify the manner in which a user process failure is resolved.
• Identify the methods for resolving user error failures.
• Identify the recovery process for an instance failure.
• Set the FAST_START_MTTR_TIME and query the results.
• Identify the tasks to be performed to ensure easy and quick recovery from media failure.
• Identify a database failure error condition.
• Diagnose a trace file to identify a database failure error condition.
• Identify the characteristics of the DB_BLOCK_CHECKSUM parameter.
• Verify the integrity of a data file by using the DBVERIFY utility.
• Match the DBMS_REPAIR utility procedures to their role in the recovery of a table with block corruption.
• Analyze a log file by using the LOGMINER utility.

Duration

6

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