Low hit rate on <deletes/updates>: <percentage>%, <number of> rows read, <number of> rows qualified

There is a poor ratio of read lines to changed lines for DELETES and UPDATES. Before UPDATES and DELETES can be used to change or delete lines, the lines must be localized in the corresponding table. For this, the system uses the same access strategies used for SELECT.

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 hit rate. You can do this by starting the diagnostic monitor or an R/3 SQL trace, and then checking for any long-running UPDATE or DELETE statements.