Exachk reports FAIL FlashCache With PRE 11.2.2.4.0
(Doc ID 1399185.1)
Last updated on OCTOBER 27, 2021
Applies to:
Oracle Exadata Storage Server Software - Version 11.1.3.1.0 to 11.2.2.3.5 [Release 11.1 to 11.2]Information in this document applies to any platform.
Symptoms
Exadata reports below failure with pre 11.2.2.4. releases.
FAIL Storage Server Check Storage Server Flash Memory is not configured as Exadata Smart Flash Cache All Storage Servers
Storage Server Flash Memory is not configured as Exadata Smart Flash Cache
Success Factor DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation
Benefit / Impact:
For the vast majority of situations, maximum performance is achieved by configuring the storage server flash memory as cache, allowing the Exadata software to determine the content of the cache.
The impact of configuring storage server flash memory as cache at initial deployment is minimal. If there are already grid disks configured in the flash memory, consideration must be given as to the relocation of the data when converting the flash memory back to cache.
Risk:
Not configuring the storage server flash memory as cache may result in a degradation of overall performance.
Action / Repair:
To confirm all storage server flash memory is configured as smart flash cache, execute the command shown below:
cellcli -e "list flashcache detail" | grep size
The output will be similar to:
size: 364.75G
Starting with Exadata software version 11.2.2.4, for an environment deployed according to Oracle standards, with the storage server "flashlog" feature in use at the default size of 512M, the size of the storage server "flashcache" is expected to be 364.75G. If the size is less than that, some of the storage server flash memory may be configured as grid disks, or there may be a hardware issue, or there may be a configuration issue. Investigate and correct the condition.
To create Exadata Smart Flash Cache, execute the following cellcli command as the "celladmin" user:
create flashcache all
NOTE: For Exadata Software version 11.2.2.3 or lower, or Exadata Software version 11.2.2.4.0 or higher where a decision was made not to create Exadata Smart Flash Log, the size of the storage server "flashcache" is expected to be 365.25G.
NOTE: See also "Verify Exadata Smart Flash Log is Created".
Success Factor DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation
Benefit / Impact:
For the vast majority of situations, maximum performance is achieved by configuring the storage server flash memory as cache, allowing the Exadata software to determine the content of the cache.
The impact of configuring storage server flash memory as cache at initial deployment is minimal. If there are already grid disks configured in the flash memory, consideration must be given as to the relocation of the data when converting the flash memory back to cache.
Risk:
Not configuring the storage server flash memory as cache may result in a degradation of overall performance.
Action / Repair:
To confirm all storage server flash memory is configured as smart flash cache, execute the command shown below:
cellcli -e "list flashcache detail" | grep size
The output will be similar to:
size: 364.75G
Starting with Exadata software version 11.2.2.4, for an environment deployed according to Oracle standards, with the storage server "flashlog" feature in use at the default size of 512M, the size of the storage server "flashcache" is expected to be 364.75G. If the size is less than that, some of the storage server flash memory may be configured as grid disks, or there may be a hardware issue, or there may be a configuration issue. Investigate and correct the condition.
To create Exadata Smart Flash Cache, execute the following cellcli command as the "celladmin" user:
create flashcache all
NOTE: For Exadata Software version 11.2.2.3 or lower, or Exadata Software version 11.2.2.4.0 or higher where a decision was made not to create Exadata Smart Flash Log, the size of the storage server "flashcache" is expected to be 365.25G.
NOTE: See also "Verify Exadata Smart Flash Log is Created".
Changes
The exachk output reports this with recent version of exachk.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |