The Database Alert Monitor display contains, among other things, results of the consistency checks between the ABAP Dictionary and the database system.
The database is the basis of the current SAP Web AS system.
Open the Database Alert Monitor. In the alert monitor, choose SAP Consistency.
The system displays the following:
SAP Consistency Check:
Displays when the last consistency check was performed. If no inconsistencies were found, the system displays a green alert.
Objects Missing in the Database:
Yellow and red alerts indicate that some ABAP Dictionary objects (secondary indexes, tables, and views, and primary indexes) could not be found in the database. If you double-click the relevant alert, you can perform additional analyses.
If an object was intentionally deleted from the databases during development or if a database error occurred during creation, this missing object list can be significant for customer objects. Objects not being found in the database can lead to incomplete or incorrect transports and cancelled conversions. Create the missing objects in the database system.
Unknown Objects in ABAP Dictionary:
Yellow and Red alerts indicate that database objects (tables, indexes, and views) have not been defined in the ABAP Dictionary. If you double-click the relevant alert, you can perform additional analyses.
Since the objects do not belong to the SAP system, this list is mainly intended for information purposes. The objects are directly created by means of the database system. If the author is unknown, the purpose of the object can sometimes be determined using the display function. Since the data display in an SAP system is based on the ABAP Dictionary definitions, data can be displayed only by using the database system. Always create customer tables, views, and indices with the ABAP Dictionary. This is the only way of ensuring that the objects are recognized by the SAP system and that problems are avoided during the upgrade.
Yellow and red alerts indicate that the definitions of the objects (primary indexes, secondary indexes, tables, and views) in the ABAP Dictionary are not the same as those in the SAP MaxDB database catalog. Compare the object definition in the ABAP Dictionary with the definition in the catalog and correct the wrong definition.
Several checks are performed, including the check whether the primary indices of the tables defined in the ABAP Dictionary were created exclusively in the database instance, and whether there are objects in the SAP base tables that cannot be described or only incompletely described in the ABAP Dictionary.
Indexes defined in the ABAP Dictionary as optional database indexes have been found. Also displayed here are all the indexes that were defined in the ABAP Dictionary but that are flagged as not being allowed to be created in your database. Find out whether the indexes were intentionally created in this way.