Use this procedure to remove inconsistencies in the database used by the user management engine (UME).
More information: Checking the Consistency of Entries in the UME Database .
The consistency check makes changes directly in the database. To undo the changes, you must prepare a backup.
The consistency check displays the Interactive Repair Process view. In this view, the consistency check offers one or more the following repair options for each error found:
This option deletes all database entries with this principal.
This option deletes all database entries with this attribute in the given namespace for a specific principal.
This option deletes the database entry with this value for the specific attribute and principal.
The consistency check also provides a description for each error.
The delete notification alerts applications which implement registered listeners to changes in the database.
This enables SAP NetWeaver Portal Knowledge Management to its update access control lists (ACL).
To send delete notification, set the indicator Send Delete Notifications to Components Outside UME.
This step is a reminder for you to backup the database of the AS Java.
Choose Interrupt Repair to stop the repair process.
The consistency check finishes with one of the following results:
The consistency check has removed all inconsistencies from the database.
You did not choose all the repair options suggested by the consistency check.
The consistency check sometimes suggests more than one repair option for a single error. If you choose only one repair option, the consistency check reports that inconsistencies remain. To be sure that no more inconsistencies remain, run the consistency check again.
To view the results of the repair process, choose View Repair-Log. In the Log of Repair Process view, you can see which repairs the consistency check made. The consistency check writes this log to the working directory under the filename repair.log . Whenever you start a repair process, the consistency check overwrites this log.
To understand how the consistency check repairs inconsistencies, it is helpful to understand how the UME stores data in the database of the AS Java. Among other data, the UME stores the following in the database:
A database table might look like the following:
UME Data in the Database
Principal ID | Namespace | Attribute | Value |
---|---|---|---|
principal1 |
com.sap |
attribute1 |
x |
principal1 |
com.sap |
attribute1 |
y |
principal1 |
com.sap |
attribute2 |
z |
Depending on the repair option you choose, the consistency check deletes different rows from the table.