Oracle Database Consistency Alerts in SAP

Share this article :

Consistency check

Cause: Threshold for number of days since the last successful run of the consistency check is exceeded.
Action: Run the consistency check.

Objects missing in database

Primary indexes, Secondary indexes, Tables, Views
Cause: Some ABAP Dictionary objects were not found in the database. 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.
Action: Unless there has been either an incomplete transport or a canceled conversion, simply create the object in the database.

Unknown objects in ABAP Dictionary

Database tables, Database indexes, Database views, Database tables without unique index
Cause: Objects were found in the database that are not defined in the ABAP Dictionary. Since these objects do not belong to the SAP System or cause problems, this list is primarily for information. These objects are usually created directly via the database. If the author is unknown, the purpose of the object can sometimes be determined using the display function. Because the data display in the SAP System is based on ABAP Dictionary definitions, data can be displayed only via the database.
Action: Customer tables, views and indexes should always be created with the ABAP Dictionary. This is the only way to ensure that the objects are recognized by the SAP System and that problems such as collisions can be avoided during upgrading.

Inconsistent objects

Primary indexes, Secondary indexes, Tables, Views
Cause: Objects exhibit inconsistencies between their ABAP Dictionary definitions and their database data dictionary definitions.
Action: Compare the object’s definition in the ABAP Dictionary with that in the database data dictionary and update the incorrect one.

Other checks

Primary indexes, Secondary indexes, Tables, Views, Primary index not unique
Cause: Several checks are performed, including whether the primary indexes of tables defined in the ABAP Dictionary were created uniquely in the database and whether there are objects in the SAP tables that either cannot be described at all or cannot be completely described in the ABAP Dictionary.

Optional indexes

Too many indexes created, Indexes not created
Cause: Indexes defined in the ABAP Dictionary as optional database indexes have been found.
All the indexes which are defined in the ABAP Dictionary but for which a flag is set that they should not be created on the database to their system configuration or database system are displayed here as well.
Action: Determine if these indexes have either been created or not been created as intended.

Related posts

Disable Transport All in STMS
Configure PRIV Mode Termination Automatically
Find STMS Transport Domain Controller
Drop Tablespace via BRTOOLS
© 2018 ITsiti. All Rights Reserved
Powered by KEEM