Your two-instance RAC database is running in ARCHVELOG. The instance running on node1., fails and this failure Is ejected by the instance running on node2,which indicates the recovery process for…

Question

Options

• APMON
• BMMON
• CSMON
• DGES
• EGCS

• B
  6% (1)
• C
  82% (14)
• E
  12% (2)

Explanation

Instance Recovery and Database Availability The graphic illustrates the degree of database availability during each step of Oracle instance 1. Real Application Clusters is running on multiple nodes. 2. Node failure is detected. 3. The enqueue part of the GRD is reconfigured; resource management is redistributed to the surviving nodes. This operation occurs relatively quickly. 4. The cache part of the GRD is reconfigured and SMON reads the redo log of the failed instance to identify the database blocks that it needs to recover. 5. SMON issues the GRD requests to obtain all the database blocks it needs for recovery. After the requests are complete, all other blocks are accessible. 6. The Oracle server performs roll forward recovery. Redo logs of the failed threads are applied to the database, and blocks are available right after their recovery is completed. 7. The Oracle server performs rollback recovery. Undo blocks are applied to the database for all uncommitted transactions. 8. Instance recovery is complete and all data is accessible. Note: The dashed line represents the blocks identified in step 2 in the previous slide. Also, the dotted steps represent the ones identified in the previous slide.

No community discussion yet for this question.