The Database Smart Flash Cache allows an instance to access multiple flash devices without requiring a volume manager. This feature only works on Solaris and Linux OS.
Enabling Smart Flash Cache is a benefit if:
- Buffer Pool Advisor of AWR or STATSPACK says to double size of buffer cache.
- DB FILE SEQUENTIAL READ is top wait event.
- System has spare CPU cycles.
Two initialization parameters used to configure Database Smart Flash Cache.
DB_FLASH_CACHE_FILE – list of Paths and files for Database Smart Flash Cache which can be ASM or OS files but must be on a flash device. If not specified, oracle will create on startup. Support max of 16 files.
DB_FLASH_CACHE_SIZE – Specifies size of each file, if number of sizes does not match number of files, an error will occur. Size is specified by nG (ie 10G). You disable FLASH device by specifying zero for size. But this is not a dynamic change and restart is required.
V$FLASHFILESTAT view can determine latency and read counts for each file.
Larry Catt
OCP