Missing Indexes (SAP DB) (SAP Library

Missing Indexes (SAP DB)

Use

Indexes are essential for fast efficient access to the serverdb. You should make regular checks to determine whether indexes are missing from the database system. This is particularly important after major changes, such as an upgrade.

There are two types of inconsistencies:

Indexes are found in the serverdb, but not in the R/3 Repository
Indexes are defined in the R/3 Repository but are not found in the server database

Procedure

Use the Tables/Indexes section in the Detail Analysis Menu to determine whether any indexes are missing.

The available functions are:

Checks	Updates the comparison between the R/3 Repository and the database system
Detailed analysis	Detailed index analysis for a table
Roots	Detailed index analysis for a table. The system reports the root page number for the B*tree created for the index.
Missing indexes	Detailed list of the missing indexes

Always recreate missing indexes immediately as they are very important for database system function.

Primary indexes (ending with 0) ensure that the line keys (row keys) are unique. Missing primary indexes is therefore a critical problem.
Secondary indexes (do not end with 0) are used for special scans and are only relevant to performance.

To create missing secondary indexes, use the database utility. For indexes that are defined in the ABAP Dictionary but are not in the server database, you can start the database utility directly from the list by choosing Create in DB ( Creating Objects in the Database)

To create missing primary indexes, you can also use the database utility. However, you should make a detailed analysis of the situation before you use the database utility. If duplicate keys have already been inserted in the table, for example, it is no longer possible to create the index. You must identify the incorrect keys and delete them. In difficult cases, contact SAP regarding the restoration of the index.

See also:

Database Alert Monitor