Low hit rate for optimizer strategy 
Low hit rate for optimizer strategy
Low hit rate for optimizer strategy:<percentage>%, <number of>accesses, <number of>rows read, <number of> rows qualified
Explanation
There is a poor ratio of read lines to found (qualified) lines for the access strategy used by the database optimizer. See also
Low hit rate for table scans.User action
First rebuild the internal database statistics to see if the database optimizer can find a better search strategy. You can use CONTROL to update statistics, or use the UPDCOL tool from an operating system command line. As large amounts of data may need to be checked, these statements may run for a long time and should therefore not be started during active applications, if possible. This will also help to avoid any lock conflicts. (stopsap r3 - Update Statistics - startsap r3).
If this is not successful, check the statement that triggered the poor search strategy. You can do this by starting the diagnostic monitor or an R/3 SQL trace, and then checking for any long-running statements where the EXPLAIN statement is used to check the search strategy used by the optimizer.