Yesterday, an Exadata storage server flashdisk entered the poor performance state. This flashdisk os used by flashcache and has a griddisk which is a member of a normal redundancy diskgroup…

Question

Options

• AIdentify the griddisk located on the poorly performing flashdisk and drop it from the associated ASm diskgroup.
• BVerify that the griddisk located on the poorly performing flashdisk has been successfully dropped from
• CDrop the flashcache on all cell.
• DSafely power off the cell containing the poorly-performing flashdisk.
• EReplace the poorly performing flashdisk.
• FPower up the cell containing the replaced flashdisk and activate all griddisks.
• GRecreate the flashcache on the cell using all flashdisks.
• HCreate a new griddisk on the replaced flashdisk.

• A
  83% (19)
• B
  4% (1)
• C
  9% (2)
• G
  4% (1)

Explanation

• The default way to deal with the Flash Storage is to use it completely as Flash Cache. You may think of Flash Cache as a prolongation of the Database Buffer Cache. It is populated automatically by the system with objects deemed useful to cache them. * The second possibility to deal with the Flash Storage is to take a part of it for building ASM diskgroups upon. All files on these ASM diskgroups will then reside permanently on Flash CellCLI> drop flashcache Flash cache exa5cel01_FLASHCACHE successfully dropped CellCLI> create flashcache all Flash cache exa5cel01_FLASHCACHE successfully created CellCLI> create griddisk all flashdisk prefix=flashdrive

No community discussion yet for this question.