High read rate (physical):<number of>pages per command <number of> physical reads, <number of> commands

The application contains statements that require a large number of physical database reads, as the requested data was not found in the data cache. A high read rate 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 rate is not caused by the first read of the table, check the size of the data cache and the data cache hit rate. Also, determine whether the SQL statements in the application read much more data than is actually required for processing (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.