less7_数据库恢复.pptVIP

* UNTIL TIME Recovery Example Let’s look at a typical scenario employing UNTIL TIME recovery. Assume the following facts: The current time is 12:00 p.m. on May 28, 2004. The OE.ORDERS table has been dropped. The table was dropped at approximately 11:45 a.m. Database activity is minimal because most staff are currently in a meeting. The table must be recovered. * UNTIL TIME Recovery Steps Because the approximate time of the failure is known and the database structure has not changed since 11:44 a.m., you can use the UNTIL TIME method: 1. If the database is open, shut it down by using either the NORMAL, IMMEDIATE, or TRANSACTIONAL options. 2. Restore all data files from backup (the most recent if possible). You may also need to restore archived logs. If there is enough space available, restore to the LOG_ARCHIVE_DEST location or use the ALTER SYSTEM ARCHIVE LOG START TO LOCATION command or the SET LOGSOURCE LOCATION command to change the location. 3. Mount the database. 4. Recover the database: SQL recover database until time 2004-05-28:11:44:00 ORA-00279: change 148448 … 05/27/04 17:04:20 needed for thread ... Media recovery complete. * Incomplete Recovery Using UNTIL CANCEL You are concerned about block corruption in the ORDERS table resulting from disk error. Because the redo log files are contained on the same disk as the data file in which the ORDERS table resides, you decide to check the status of the redo log and archived log files: SQL SELECT group#, status, member FROM v$logfile; GROUP# STATUS MEMBER 2 /u01/ora10i/ORADATA/log2a.rdo 1 /u01/ora10i/ORADATA/log1a.rdo SQL ALTER SESSION SET nls_date_format=YYYY-MM-DD:HH24:MI:SS; Session altered. SQL SELECT * FROM v$log; GROUP# ... SEQ# BYTES MEMBERS ARC STATUS ... FIRST_TIME ... ... 1 ... 49 15360 1 NO CURRENT ... 2004-05-28:11:55 2 ... 48 15360 1 NO INACTIVE... 2004-05-28:11:34 * Incomplete Recovery Us