1. 5 Copyright © 2006, Oracle. All rights reserved. Database Recovery

2. 5-2 Copyright © 2006, Oracle. All rights reserved. Objectives After completing this lesson, you should be able to: Perform complete or incomplete user-managed recovery Identify situations where incomplete recovery is necessary Perform complete or incomplete recovery by using RMAN Perform incomplete recovery based on time, SCN, log sequence, restore points, or the cancel method Recover an automatically backed up control file Use Enterprise Manage to perform recovery Recover read-only tablespaces User man. RMAN CLI EM Complete Incomplete Control file RO TBS

3. 5-3 Copyright © 2006, Oracle. All rights reserved. Recovery Methods There are two methods for performing recovery: User-managed recovery –Files must be maintained and moved into place manually. –Use SQL*Plus commands. RMAN recovery –Files are managed automatically. –Use RMAN functionality including all repository maintenance and reporting capabilities. –This can be done by using Enterprise Manager. –Oracle Corporation recommends using this method.

4. 5-4 Copyright © 2006, Oracle. All rights reserved. User-Managed Recovery: RECOVER Command Restore all database files from a backup and then recover the database: Restore the damaged data files from a backup and then recover the data files: Or: SQL> RECOVER DATABASE SQL> RECOVER TABLESPACE index_tbs SQL> RECOVER DATAFILE 2> '/oradata/indx01.dbf'

5. 5-5 Copyright © 2006, Oracle. All rights reserved. RMAN Recovery: RESTORE and RECOVER Commands run{ sql "ALTER TABLESPACE inv_tbs OFFLINE IMMEDIATE"; RESTORE TABLESPACE inv_tbs; RECOVER TABLESPACE inv_tbs DELETE ARCHIVELOG; sql "ALTER TABLESPACE inv_tbs ONLINE"; } User man. >RMAN CLI EM Complete Incomplete Control file RO TBS

6. 5-6 Copyright © 2006, Oracle. All rights reserved. Recovery Using Enterprise Manager With the Enterprise Manager Recovery Wizard, you can create and run an RMAN script to perform the recovery. RMAN> RECOVER DATABASE … User man. RMAN CLI >EM Complete Incomplete Control file RO TBS

7. 5-7 Copyright © 2006, Oracle. All rights reserved. Complete Versus Incomplete Recovery There are two types of recovery: Complete recovery brings the database up to the present, including all data changes made to the point in time when the recovery was requested. Incomplete recovery brings the database up to a specified point in time in the past, before the recovery operation was requested. Recovery task started at this time Complete recovery Incomplete recovery Missing transactions after incomplete recovery Restore from this backup

8. 5-8 Copyright © 2006, Oracle. All rights reserved. Complete Recovery Restored data files Data files containing committed and uncommitted transactions Recovered data files Changes applied Undo applied 6 5 3 2 1 Archived log Online Redo log User man. RMAN CLI EM >Complete Incomplete Control file RO TBS 4 Database opened

9. 5-9 Copyright © 2006, Oracle. All rights reserved. Incomplete Recovery Data files containing committed and uncommitted Transactions up to PIT PIT-recovered data files Undo applied 6 5 3 2 1 Archived log Online Redo log 4 Database opened X X Changes applied to point in time (PIT) Restored data files from as far back as necessary User man. RMAN CLI EM Complete >Incomplete Control file RO TBS

10. 5-10 Copyright © 2006, Oracle. All rights reserved. Incomplete Recovery (notes only slide)

11. 5-11 Copyright © 2006, Oracle. All rights reserved. Situations Requiring Incomplete Recovery Complete recovery fails because of a missing archived log file. One or more unarchived redo log files and a data file are lost. A backup of the control file is used to open or recover the database.

12. 5-12 Copyright © 2006, Oracle. All rights reserved. Types of Incomplete Recovery There are four types of incomplete recovery: Time-based recovery Cancel-based recovery Change-based recovery Log sequence recovery

13. 5-13 Copyright © 2006, Oracle. All rights reserved. Types of Incomplete Recovery (notes only slide)

14. 5-14 Copyright © 2006, Oracle. All rights reserved. Performing User-Managed Incomplete Recovery Recover a database until time: Recover a database until cancel: Recover using the backup control file: SQL> RECOVER DATABASE UNTIL CANCEL; SQL> RECOVER DATABASE UNTIL 2 TIME '2005-12-14:12:10:03'; SQL> RECOVER DATABASE 2 UNTIL TIME '2005-12-14:12:10:03' 3 USING BACKUP CONTROLFILE;

15. 5-15 Copyright © 2006, Oracle. All rights reserved. Performing User-Managed Incomplete Recovery To perform user-managed incomplete recovery, follow these steps: 1.Shut down the database. 2.Restore data files. 3.Mount the database. 4.Recover the database. 5.Open the database with the RESETLOGS option.

16. 5-16 Copyright © 2006, Oracle. All rights reserved. User-Managed Time-Based Recovery: Example SQL> SHUTDOWN IMMEDIATE $ cp /BACKUP/* /u01/db01/ORADATA SQL> STARTUP MOUNT SQL> RECOVER DATABASE UNTIL TIME '2005-11-28:11:44:00'; SQL> ALTER DATABASE OPEN RESETLOGS; This is the scenario: A job ran in error, and its effects have to be undone. This happened 15 minutes ago, and there has been little database activity since then. You decide to perform incomplete recovery to restore the database back to its state as of 15 minutes ago.

17. 5-17 Copyright © 2006, Oracle. All rights reserved. User-Managed Time-Based Recovery Steps (notes only slide)

18. 5-18 Copyright © 2006, Oracle. All rights reserved. User-Managed Cancel-Based Recovery: Example The scenario is the same as the one for the time-based example, except for these findings: Redo logs are not multiplexed. One of the online redo logs is missing. The missing redo log is not archived. The redo log contained information from 11:34 a.m. Twenty-six minutes of data are lost. Users can reenter their data manually.

19. 5-19 Copyright © 2006, Oracle. All rights reserved. User-Managed Cancel-Based Recovery: Example Recover the database as follows: 1.Shut down the database. 2.Restore all data files from the most recent backup. 3.You already have a valid backup, so mount the database. 4.Execute RECOVER DATABASE UNTIL CANCEL. 5.Execute ALTER DATABASE OPEN RESETLOGS to open the database.

20. 5-20 Copyright © 2006, Oracle. All rights reserved. Performing Incomplete Recovery by Using RMAN 1.Mount the database. 2.Allocate multiple channels for parallelization. 3.Restore all data files. 4.Recover the database by using UNTIL TIME, UNTIL SEQUENCE, or UNTIL SCN. 5.Open the database by using RESETLOGS.

21. 5-21 Copyright © 2006, Oracle. All rights reserved. Time-Based Recovery Using RMAN: Example RMAN> RUN { 2> SET UNTIL TIME = '2005-11-28:11:44:00'; 3> RESTORE DATABASE; 4> RECOVER DATABASE; 5> ALTER DATABASE OPEN RESETLOGS; }

22. 5-22 Copyright © 2006, Oracle. All rights reserved. Time-Based Recovery Using RMAN: Example (notes only slide)

23. 5-23 Copyright © 2006, Oracle. All rights reserved. Log Sequence Recovery Using RMAN: Example RMAN> RUN { 2> SET UNTIL SEQUENCE 120 THREAD 1; 3> ALTER DATABASE MOUNT; 4> RESTORE DATABASE; 5> RECOVER DATABASE; # recovers through log 119 6> ALTER DATABASE OPEN RESETLOGS; 7> }

24. 5-24 Copyright © 2006, Oracle. All rights reserved. Incomplete Recovery Using Enterprise Manager

25. 5-25 Copyright © 2006, Oracle. All rights reserved. Incomplete Recovery and the Alert Log The following are some best practices regarding the alert log in incomplete recovery scenarios: Check the alert log before and after recovery. Look for error information, hints, and SCNs. Confirm that steps in the recovery process were successful.

26. 5-26 Copyright © 2006, Oracle. All rights reserved. Restore Points A restore point: Serves as an alias for an SCN or a specific point in time Is stored in the control file Can be used with: – RECOVER DATABASE – FLASHBACK DATABASE – FLASHBACK TABLE SQL> CREATE RESTORE POINT before_load; before_load RMAN> RECOVER DATABASE UNTIL RESTORE POINT before_load; 2 1

27. 5-27 Copyright © 2006, Oracle. All rights reserved. Incomplete Recovery: Best Practices Plan for and practice scenarios ahead of time. Investigate and verify that incomplete recovery is necessary. Follow all steps carefully. Take whole database backups before and after recovery. Always verify that the recovery was successful. Take advantage of restore points.

28. 5-28 Copyright © 2006, Oracle. All rights reserved. Incomplete Recovery Best Practices (notes only slide)

29. 5-29 Copyright © 2006, Oracle. All rights reserved. Recovering a Control File Autobackup Recovery Manager (RMAN) Flash recovery area Database Control file RECOVER DATABASE; ALTER DATABASE OPEN RESETLOGS; ALTER TABLESPACE temp ADD TEMPFILE...; RMAN> RESTORE CONTROLFILE TO 2> '/oradata/ctlfile.bak' FROM AUTOBACKUP; User man. RMAN CLI EM Complete Incomplete >Control file RO TBS

30. 5-30 Copyright © 2006, Oracle. All rights reserved. Recovering a Control File Autobackup (notes only slide)

31. 5-31 Copyright © 2006, Oracle. All rights reserved. Creating a New Control File SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE; Password file Parameter file SYSTEM SYSAUX UNDO TEMP USERS INDEX Redo log file 1B Redo log file 1A Redo log file 2B Redo log file 2A Control files

32. 5-32 Copyright © 2006, Oracle. All rights reserved. Creating a New Control File

33. 5-33 Copyright © 2006, Oracle. All rights reserved. Recovering Read-Only Tablespaces Change Tablespace State Crash and perform recovery Case 1 Case 2 Case 3 Backup Read-only Read/write Read-only Read/write * * * * Control file backup to be used for recovery if current one lost User man. RMAN CLI EM Complete Incomplete Control file >RO TBS

34. 5-34 Copyright © 2006, Oracle. All rights reserved. Recovering Read-Only Tablespaces (notes only slide)

35. 5-35 Copyright © 2006, Oracle. All rights reserved. Read-Only Tablespace Recovery Issues Special considerations must be taken for read-only tablespaces when: Re-creating a control file Renaming data files Using a backup control file

36. 5-36 Copyright © 2006, Oracle. All rights reserved. Read-Only Tablespace Recovery Issues (notes only slide)

37. 5-37 Copyright © 2006, Oracle. All rights reserved. Summary In this lesson, you should have learned how to: Perform complete or incomplete user-managed recovery Perform complete or incomplete recovery by using RMAN Identify situations where incomplete recovery is necessary Perform incomplete recovery based on time, SCN, log sequence, restore points, or the cancel method Recover a control file autobackup Use Enterprise Manage to perform recovery Recover read-only tablespaces

38. 5-38 Copyright © 2006, Oracle. All rights reserved. Practice Overview: Performing Incomplete Recovery This practice covers the following topics: Point-in-time recovery using RMAN Recovery from the loss of control files