High read activity (physical)<number of> pages/second

There are a high number of physical database reads, as the data requested by the applications was not found in the data cache. High read activity is normal if a table is accessed for the first time, or has not been used for a long time and therefore has been removed from the data cache.

If the high read activity is not caused by the first read of the table, check the data cache hit rate and increase the size of the data cache, if necessary. Also determine whether the SQL statements in the application read much more data than is actually required for processing (use the diagnostic monitor to look for unnecessary tablescans or disadvantageous search strategies).

For tablescans, make sure for _LRU_FOR_SCAN=YES (XPARAM) only 10% of the cache is used for buffering, so that there is enough room in the cache for the entire table. Otherwise, the table will have to be physically read again for the next scan.