OCP 1Z0 053 180

180.Which command is used to open the database after an incomplete recovery? 
A. alter database open 
B. alter database open repairlog 
C. alter database open resetlogs 
D. alter database open resetlog 
E. alter database resetlogs open 
Answer: C 

D少了个S，汗一个

file:///G:/book/Oracle/E11882_01/backup.112/e10642/osrecvry.htm#i1007175

Performing Cancel-Based Incomplete Recovery

In cancel-based recovery, recovery proceeds by prompting you with the suggested file names of archived redo log files. Recovery stops when you specify CANCEL instead of a file name or when all redo has been applied to the data files.

To perform cancel-based recovery:

1. Follow Step1 through Step 8 in "Performing Closed Database Recovery".

2. Begin cancel-based recovery by issuing the following command in SQL*Plus:

   RECOVER DATABASE UNTIL CANCEL

   Note:

   If you fail to specify the UNTIL clause on the RECOVER command, then the database assumes a complete recovery and does not open until all redo is applied.

   The database applies the necessary redo log files to reconstruct the restored data files. The database supplies the name it expects to find from LOG_ARCHIVE_DEST_1 and requests you to stop or proceed with applying the log file. If the control file is a backup, then you must supply the names of the online redo logs if you want to apply the changes in these logs.

3. Continue applying redo log files until the last log has been applied to the restored data files, then cancel recovery by executing the following command:

   CANCEL

   The database indicates whether recovery is successful. If you cancel before all the data files have been recovered to a consistent SCN and then try to open the database, then you get an ORA-1113 error if more recovery is necessary. You can query V$RECOVER_FILE to determine whether more recovery is needed, or if a backup of a data file was not restored before starting incomplete recovery.

4. Open the database with the RESETLOGS option. You must always reset the logs after incomplete recovery or recovery with a backup control file. For example:

   ALTER DATABASE OPEN RESETLOGS;

   If you attempt to use OPEN RESETLOGS when you should not, or if you neglect to reset the log when you should, then the database returns an error and does not open the database. Correct the problem and try again.

   See Also:

   "About User-Managed Media Recovery Problems" for descriptions of situations that can cause ALTER DATABASE OPEN RESETLOGS to fail

5. After opening the database with the RESETLOGS option, check the alert log.

   Note:

   The easiest way to locate trace files and the alert log is to run the following SQL query:SELECT NAME, VALUE FROM V$DIAG_INFO.

   When you open with the RESETLOGS option, the database returns different messages depending on whether recovery was complete or incomplete. If the recovery was complete, then the following message appears in the alert log:

   RESETLOGS after complete recovery through change scn

   If the recovery was incomplete, then this message is reported in the alert log, where scn refers to the end point of incomplete recovery:

   RESETLOGS after incomplete recovery UNTIL CHANGE scn

   Also check the alert log to determine whether the database detected inconsistencies between the data dictionary and the control file. Table 29-3 describes two possible scenarios.

   Table 29-3 Inconsistencies Between Data Dictionary and Control File

   Data File Listed in Control FileData File Listed in the Data DictionaryResult

   Yes

   No

   References to the unlisted data file are removed from the control file. A message in the alert log indicates what was found.

   No

   Yes

   The database creates a placeholder entry in the control file under MISSINGnnnnn (where nnnnn is the file number in decimal).MISSINGnnnnn is flagged in the control file as offline and requiring media recovery. You can make the data file corresponding to MISSINGnnnnn accessible by using ALTERDATABASE RENAME FILE for MISSINGnnnnn so that it points to the data file. If you do not have a backup of this data file, then drop the tablespace.

   
   

Performing Time-Based or Change-Based Incomplete Recovery