Which three are true about Smart Flash log?

Question

Options

• AI/O Resource Manager database plans can be used to enable or disable Smart Flash Log for different
• BLGWR will not wait for writes to Smart Flash log if the write to a disk based log file completes first.
• CSmart Flash Log is enabled by default, using 1024 MB of Rash storage on each storage server.
• DYou can remove Smart Flash Log from a single storage server with the drop flashing command.
• EI/O Manager category plans can be used to enable or disable Smart Flash Log For different I/O categories.

• A
  86% (12)
• C
  7% (1)
• E
  7% (1)

Explanation

A: the Exadata I/O Resource Manager (IORM) has been enhanced to enable or disable Smart Flash Logging for the different databases running on the Database Machine. B: Smart Flash Logging works as follows. When receiving a redo log write request, Exadata will do parallel writes to the on-disk redo logs as well as a small amount of space reserved in the flash hardware. When either of these writes has successfully completed the database will be immediately notified of completion. If the disk drives hosting the logs experience slow response times, then the Exadata Smart Flash Cache will provide a faster log write response time. Conversely, if the Exadata Smart Flash Cache is temporarily experiencing slow response times (e.g., due to wear leveling algorithms), then the disk drive will provide a faster response time. This algorithm will significantly smooth out redo write response times and provide overall better database performance. D: Category plans are configured and enabled using the CellCLI utility on the cell. Only one category plan can be enabled at a time Not C: By default, 512 MB of the Exadata flash is allocated to Smart Flash Logging

No community discussion yet for this question.