1Z0-052 · Question #143
You executed the following commands in an RMAN session for your database instance that has failures: RMAN> LIST FAILURE; After some time, you executed the following command in the same session…
The correct answer is A. It produces a warning for new failures before advising for CRITICAL and HIGH failures. When ADVISE FAILURE detects failures in the ADR that were recorded after the most recent LIST FAILURE command, it automatically issues a warning about those new failures before proceeding with advice. RMAN does not silently ignore new failures or require the user to rerun LIST…
Question
You executed the following commands in an RMAN session for your database instance that has failures:
RMAN> LIST FAILURE; After some time, you executed the following command in the same session:
RMAN> ADVISE FAILURE; But there are new failures recorded in the Automatic Diagnostic Repository (ADR) after the execution of the last LIST FAILURE command. Which statement is true for the above ADVISE FAILURE command in this scenario?
Options
- AIt produces a warning for new failures before advising for CRITICAL and HIGH failures.
- BIt ignores new failures and considers the failures listed in the last LIST FAILURE command only.
- CIt produces advice only for new failures and the failures listed in the last LIST FAILURE command
- DIt produces an error with recommendation to run the LIST FAILURE command before the ADVISE
How the community answered
(58 responses)- A64% (37)
- B7% (4)
- C10% (6)
- D19% (11)
Why each option
When ADVISE FAILURE detects failures in the ADR that were recorded after the most recent LIST FAILURE command, it automatically issues a warning about those new failures before proceeding with advice. RMAN does not silently ignore new failures or require the user to rerun LIST FAILURE manually.
RMAN's ADVISE FAILURE command internally re-queries the ADR at execution time and, if it finds failures recorded after the previous LIST FAILURE, it emits a warning message identifying those new failures so the DBA is aware of them. It then proceeds to generate repair advice covering all CRITICAL and HIGH priority failures, including both the previously listed ones and the newly discovered ones. This design prevents any failures from being silently overlooked during a repair session.
RMAN does not restrict itself to the failure set from the last LIST FAILURE execution; it actively re-checks the ADR and incorporates newly recorded failures into its advisory output.
ADVISE FAILURE does not produce advice exclusively for new failures; it advises on all unresolved CRITICAL and HIGH failures and simply issues a warning about the new ones discovered since the last LIST FAILURE.
RMAN does not generate an error or halt when new failures are found; it handles the situation automatically by warning the user and continuing to produce advice without requiring a manual re-run of LIST FAILURE.
Concept tested: RMAN Data Recovery Advisor ADVISE FAILURE new failure handling
Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/rman-data-repair-concepts.html
Topics
Community Discussion
No community discussion yet for this question.