Explanation/Reference:
Explanation:
In earlier releases, database administrators had to mark an object as KEEP to have it cached in flash cache for large scan workloads. This feature primarily benefits table scan intensive workloads such as Data Warehouses and Data Marts. Random I/Os such as those performed for Online Transactional Processing (OLTP)continue to be cached in the flash cache the same way as in earlier releases.
Note: With the Exadata Storage Server Software 11.2.3.3.0 and above, the Exadata Smart Flash Cache software automatically caches objects read, in large table scans, in the flash cache based on how frequently the objects are read. Previously, the default behavior was to bypass the flash cache for such large sequential scans.