Which three types of failures are detected by the Data Recovery Advisor (DRA)?
A.
loss of a non-critical data file
B.
loss of a control file
C.
physical data block corruption
D.
logical data block corruption
E.
loss of an archived redo log file
Explanation:
Reference:
http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmrepai.htm#BRADV89728
A B C
http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmrepai.htm
Components such as datafiles and control files that are not accessible because they do not exist, do not have the correct access permissions, have been taken offline, and so on
–> B
Physical corruptions such as block checksum failures and invalid block header field values–>
–> C
Inconsistencies such as a datafile that is older than other database files
–> D
I/O failures such as hardware errors, operating system driver failures, and exceeding operating system resource limits (for example, the number of open files)
–> D
I would say B,C,D
A B C
same quotes and document as above, critical or not it’s still a data file gone 🙂
ABCE
http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmrepai.htm
BCE:
Failures with CRITICAL priority require immediate attention because they make the whole database unavailable. For example, a disk containing a current control file may fail. Failures with HIGH priority make a database partly unavailable or unrecoverable and usually have to be repaired quickly. Examples include block corruptions and missing archived redo logs.
A:
Just because a data file is non-critical doesn’t mean the failure isn’t detected.
Not D:
Note that Data Recovery Advisor may detect or handle some logical corruptions. But in general, corruptions of this type require help from Oracle Support Services.
So, in general, it doesn’t handle logical corruptions.
Poor question, but if I had to pick 3, then
BCE
ABC
I am with Steve on this, first I picked
ABCE seems right to me but I will go with BCE.
Why E, DRA checks for all files and backups for recovery
According to Oracle Docs, I would say ABC as well.
Reference:
Data Recovery Advisor can diagnose failures such as the following:
Components such as datafiles and control files that are not accessible because they do not exist, do not have the correct access permissions, have been taken offline, and so on
Physical corruptions such as block checksum failures and invalid block header field values
ABC
I Think A is not a right answer, DRA can detect and repair “system” datafile failure, then A restrect the capabilities to be in non-critical datafiles.
Agree about B and C
Not Sure about D or E but would say D as losing archive log may not be a failure.
Also, DRA using the archive logs for recovery as mentioned in section “Manual Actions and Automatic Repair Options” of Oracle Database Backup and Recovery User’s Guide 11.2
Data Recovery Advisor performs feasibility checks before recommending an automated repair. For example, Data Recovery Advisor checks that all backups and archived redo logs needed for media recovery are present and consistent. Data Recovery Advisor may need specific backups and archived redo logs. If the files needed for recovery are not available, then recovery is not possible.
Thus i would say B,C and D
ABC
RMAN> LIST FAILURE;
List of Database Failures
=========================
Failure ID Priority Status Time Detected Summary
———- ——– ——— ————- ——-
142 HIGH OPEN 23-APR-13 One or more non-system datafiles are missing
101 HIGH OPEN 23-APR-13 Datafile 1: ‘/disk1/oradata/prod/system01.dbf’
contains one or more corrupt blocks
A sure.
B is here:
Because failure information is not stored in the database itself, the database does not need to be open or mounted for you to access it. You can view failures when the database is started in NOMOUNT mode. Thus, the availability of the control file and recovery catalog does not affect the ability to view detected failures, although it may affect the feasibility of some repairs.
C for sure.
Physical corruptions such as block checksum failures and invalid block header field values
D (also true) . The Data Recovery Advisor may detect or handle some logical corruptions. In general, corruptions of this type require help from Oracle Support Services.
http://docs.oracle.com/cd/E29597_01/backup.1111/e10642/rcmrepai.htm#CHDDBECC
ABC
Data Recovery Advisor can diagnose failures such as the following:
Components such as datafiles and control files that are not accessible because they do not exist, do not have the correct access permissions, have been taken offline, and so on
Physical corruptions such as block checksum failures and invalid block header field values
Inconsistencies such as a data file that is older than other database files
I/O failures such as hardware errors, operating system driver failures, and exceeding operating system resource limits (for example, the number of open files)
The Data Recovery Advisor may detect or handle some logical corruptions. In general, corruptions of this type require help from Oracle Support Services.
Data Recovery Advisor can diagnose failures such as the following:
Components such as datafiles and control files that are not accessible because they do not exist, do not have the correct access permissions, have been taken offline, and so on
Physical corruptions such as block checksum failures and invalid block header field values
Inconsistencies such as a datafile that is older than other database files
I/O failures such as hardware errors, operating system driver failures, and exceeding operating system resource limits (for example, the number of open files)
Note that Data Recovery Advisor may detect or handle some logical corruptions. But in general, corruptions of this type require help from Oracle Support Services.
I would say: ABC
From the link:
Data Recovery Advisor can diagnose failures such as the following:
A, B
=====
* Components such as datafiles and control files that are not accessible because they do not exist, do not have the correct access permissions, have been taken offline, and so on.
C
==
* Physical corruptions such as block checksum failures and invalid block header field values
* Inconsistencies such as a datafile that is older than other database files
* I/O failures such as hardware errors, operating system driver failures, and exceeding operating system resource limits (for example, the number of open files)
So, ABC for me.