You are using recovery Manager (RMAN) with a recovery catalog to backup up your production
database. The backups and the archived redo log files are copied to a tape drive on a daily basis.
The database was open and transactions were recorded in the redo logs. Because of fire in the
building you lost your servers having the production database and the recovery catalog database.
The archive log files generated after the last backup are intact on one of the remote locations.
While performing a disaster recovery of the production database what is the next step that you
must perform after restoring the data files and applying archived redo logs?
A.
Open the database in NORMAL mode
B.
Open the database in read-only mode
C.
Open the database in RESTRICTED mode
D.
Open the database with the RESETLOGS option
Why D?
Is to generate a new incarnation of the database?
Executing the ALTER DATABASE OPEN Statements
To preserve the log sequence number when opening a database after media recovery, execute either of the following statements:
ALTER DATABASE OPEN NORESETLOGS;
ALTER DATABASE OPEN;
To reset the log sequence number when opening a database after recovery and thereby create a new incarnation of the database, execute the following statement:
ALTER DATABASE OPEN RESETLOGS;
If 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_SID.log file:
RESETLOGS after complete recovery through change scn
If the recovery was incomplete, then this message is reported in the alert_SID.log file, where scn refers to the end point of incomplete recovery:
RESETLOGS after incomplete recovery UNTIL CHANGE scn
If you attempt to 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.