《les》-公开·课件设计.pptVIP

Recovering from Noncritical Losses Objectives After completing this lesson, you should be able to: Recover temporary tablespaces Recover a redo log group member Recover from a lost index Re-create the password file Causes of File Loss File loss can be caused by: User error Application error Media failure Critical Versus Noncritical Losing a TEMPFILE Recovering from a TEMPFILE Loss Log Group Status: Review A redo log group has a status of one of the following values at any given time: CURRENT: The LGWR process is currently writing redo data to it. ACTIVE: It is no longer being written to, but it is still required for instance recovery. INACTIVE: It is no longer being written to, and it is no longer required for instance recovery. Losing a Redo Log Group Member The alert log and the archiver process (ARCn) trace file record an error when a redo member file is missing. Re-creating Redo Log Files Recreating Redo Log Files(notes only slide) Recreating Redo Log Files(notes only slide) Re-creating Redo Log Files Re-creating Indexes Use options to reduce the time it takes to create the index: PARALLEL NOLOGGING Recreating Indexes(notes only slide) Authentication Methodsfor Database Administrators Re-creating a Password Authentication File Log in to the database by using OS authentication. Set the REMOTE_LOGIN_PASSWORDFILE parameter to NONE and restart the database. Re-create the password file by using orapwd. Set REMOTE_LOGIN_PASSWORDFILE to EXCLUSIVE. Add users to the password file and assign appropriate privileges to each user. Restart the instance. Summary In this lesson, you should have learned how to: Recover temporary tablespaces Recover a redo log group member Recover from a lost index Re-create the password file Practice Overview: Recovering from Lost TEMPFILE and Redo Log File This practice covers the following topics: Starting the database with a missing tempfile Creating a new temporary tablespace Altering the default temporary tablespace for a database