You are using Recovery Manager (RMAN) for backup and recovery operations with a recovery catalog. You have been taken database backups every evening. On November 15, 2007, at 11:30 AM, you were informed that the USER_DATA tablespace was accidentally dropped.
On investigation, you found that the tablespace existed until 11:00 AM, and important transactions were done after that.
So you decided to perform incomplete recovery until 11:00 AM. All the archive logs needed to perform recovery are intact. In NOMOUNT state you restored the control file that has information about the USER_DATA tablespace from the latest backup. Then you mounted the database.
Identify the next set of commands that are required to accomplish the task?
A.
RMAN> run
{
SET UNTIL TIME ‘Nov 15 2007 11:00:00’;
RESTORE DATABASE;
RECOVER DATABASE;
}
B.
RMAN> run
{
SET UNTIL TIME ‘Nov 15 2007 11:00:00’;
RESTORE DATABASE;
RECOVER DATABASE USING BACKUP CONTROLFILE;
}
C.
RMAN> run
{
RESTORE DATABASE;
RECOVER DATABASE UNTIL TIME ‘Nov 15 2007 11:00:00’;
}
D.
RMAN> run
{
RESTORE TABLESPACE user_data;
RECOVER TABLESPACE user_data UNTIL TIME ‘Nov 15 2007 11:00:00’;
}
Explanation:
Perform the following operations within a RUN block:
1.
Use SET UNTIL to specify the target time, restore point, SCN, or log sequence number for DBPITR. If
specifying a time, then use the date format specified in the NLS_LANG and NLS_DATE_FORMAT environment
variables.
2.
If automatic channels are not configured, then manually allocate disk and tape channels as needed.
3.
Restore and recover the database.
The following example performs DBPITR on the target database until SCN 1000:
RUN
{
SET UNTIL SCN 1000;
RESTORE DATABASE;
RECOVER DATABASE;
}
As shown in the following examples, you can also use time expressions, restore points, or log sequence numbers to specify the SET UNTIL time:
SET UNTIL TIME ‘Nov 15 2004 09:00:00’;
SET UNTIL SEQUENCE 9923;
SET UNTIL RESTORE POINT before_update;