After migrating from legacy disk-based configuration, which three approaches would you use to
evaluate the efficiency of Exadata Flash Cache?
A.
Review the Flash Hit rate via cellcli metrics.
B.
Compare Optimized Physical Reads and Total Read Requests in Automatic Workload
Repository (AWR).
C.
Review the IOSTAT data that is gathered from each compute node by OS Watcher.
D.
Evaluate the Smart Flash Logging efficiency metrics via CellCLI.
E.
Check I/O latency on large I/O to Temp in AWR.
Explanation:
A: You wish to determine which database objects are currently cached in Smart
Flash Cache.
Use the list flashcachecontent CellCLI command to report the objectscurrently stored in Smart
Flash Cache and map these to database object names.Using dcli or cellcli from a storage cell, run
the following command:
[oracle@cm01dbm01 ~]$ dcli -g ./cell_group cellcli -e list flashcachecontent \
> attributes dbUniqueName,hitCount,missCount,cachedSize,objectNumber
cm01cel01: EDW 0 2 98304 3
cm01cel01: DWPRD 0 0 57344 8
cm01cel01: VISY 0 0 8192 8
cm01cel01: EDW 9 15 729088 18
cm01cel01: DWPRD 0 0 16384 18
Output omitted for brevity
C: IOSTAT can be used to get both DISK and FLASH performance data.
D: Using Storage Cell Metrics to Measure IORM (Exadata IO Resource Manager) PerformanceImpact
Exadata provides a number of performance metrics for each of the Category, Interdatabase, and
Intradatabase IORM types. You can find these metric and their descriptions using
CellCLI commands.
With a representative database workload running and after your IORM plan has been created, use
the list metriccurrent or list metrichistory CellCLI command to report your current or historical
IORM metrics.
A B D
The answer looks good to me is – A,B,D
C – It was correct only in case when we take out the I/O stat for the storage cell and not the compute nodes (DB nodes).
I have checked many dump questions and Ans is A,C & D only
It’s A,B & D Only
So is it’s A,B & D – confirmed ?
yes.. A, B, D are confirmed. C option is not right.
A,B,D are correct.
Reference: Exadata Recipes page 541ff
ABD
C wrong because it’s compute node not cell.
C wrong because compute node’s OS-Watcher do not run Iostat; Iostat runs only on cell.