A database is configured in ARCHIVELOG mode.
A full RMAN backup exists but no control file backup to trace has been taken.
A media failure has occurred.
In which two scenarios is incomplete recovery required? (Choose two.)
A database is configured in ARCHIVELOG mode.
A full RMAN backup exists but no control file backup to trace has been taken.
A media failure has occurred.
In which two scenarios is incomplete recovery required? (Choose two.)
Incomplete recovery is typically necessary under two conditions in the given scenarios: if all members of the current online redo log group are lost, and if all copies of the control file are lost. Losing all members of the current online redo log group means that crucial transaction data is lost, preventing a complete recovery. Similarly, losing all copies of the control file, which holds essential metadata about the database structure and state, typically requires using a backup control file, leading to incomplete recovery.
C & D is correct. C & D is correct because if you lose all control the required incomplete recovery. if incomplete recovery then db must be open in resetlog option. E: undo tablespace. >> (Incorrect) http://oracle-help.com/backup-and-recovery/recovery-recover-loss-system-critical-undo-tablespace-original-location/ D: (correct see the details) http://oracle-help.com/backup-and-recovery/recovery-restore-loss-current-control-files-default-location/
You are right about the undo, and also the resetlog after restore the control file, but even in that case, you can do a complete recovery while you have all the redo and archives (check link) ..., I don't know which other option could be correct, so I suppose that "D" its the more accuracy. https://web.stanford.edu/dept/itss/docs/oracle/10gR2/backup.102/b14191/rcmrecov003.htm
C D is correct
CD for me
(E) Undo is used for rolling BW DB. And that is useful when you want to do PITR. But in this case, UNDO does not have any role. Incomplete recovery uses a backup to produce a noncurrent version of the database. In other words, you do not apply all of the redo records generated after the most recent backup. You usually perform incomplete recovery of the whole database in the following situations: Media failure destroys some or all of the online redo logs. A user error causes data loss, for example, a user inadvertently drops a table. You cannot perform complete recovery because an archived redo log is missing. You lose your current control file and must use a backup control file to open the database. In our case the qestion said there is not backup to trace for control file. So, exist a backup of CF included. My opinion is C and D.
C, D Even tough D, the redo are not lost, so the recovery would be complete. but you will need to reset the logs to open the database
I think C and E
Don't think it's D as since yo have all the redo files . you just create a new control file and recover the database. Its not incomplete recovery
It IS, since you do not have the information about the last valid LSN -- it was lost with the controlfiles.
C D correct
I agreed C&D too!
https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/user-managed-recovery-advanced.html#GUID-B798CEB4-E8BE-467A-B17D-DBB993E912BE
See you1234
Teoretically find the right answers is simple but ... what if we really lost all copies of control files? Does we recover the database? In my opinion: it is not easy way but possible and it is not incomplete recovery but recreate controlfile from somewhere. But if we lost active UNDO TABLESPACE during active big transaction then we need do incomplete recovery ... I think A. FALSE B. FALSE C. TRUE D. FALSE E. TRUE
Contents of the undo tablespace spans the transaction's DML until commit. So even if the UNDO tablespace gets lost, there is no incomplete recovery because the transaction was never committed in the first place. That was my argument for choosing answers C and D.
If you restore the controlfile, it is called an incomplete recovery since the database does not have the information of the last valid SCN. And you have to open the database with resetlogs.
D is true cause when you lose all copies of control files and assuming control file autobackup is ON, then the only way to recover the control file is to go back to a previous backup(which has the control file) and restore it then you can roll forward your database using archive logs.
sorry no need to roll forward the database since adding this last part will make it a complete recovery.