Repairing Inconsistencies of Entries in the
UME Database
Use
Use this procedure to remove inconsistencies in the database used by the user management engine (UME).
Prerequisites
· You have found inconsistencies in the database entries for the UME using the consistency check tool.
More information: Checking the Consistency of Entries in the UME Database.
· You have access to a user, which has been assigned a UME role with one of the following UME actions:
¡ UME.Manage_All
¡ UME.System_Admin
Procedure
...
1. Back up the database of the SAP NetWeaver Application Server (AS) Java.
The consistency check makes changes directly in the database. To undo the changes, you must prepare a backup.
2. Choose Start Interactive Repair.
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:
¡ Delete a principal
This option deletes all database entries with this principal.
¡ Delete an attribute of a principal in a specific name space
This option deletes all database entries with this attribute in the given namespace for a specific principal.
¡ Delete a value of an attribute of a 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.
3. Select the required repair options.
4. Determine if you want to send delete notification.
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.
5. Set the indictor Ensure that the database has been backed up. It will not be possible to undo afterwards.
This step is a reminder for you to backup the database of the AS Java.
6. Choose Start the Repair Process.
Choose Interrupt Repair to stop the repair process.
7. Choose Refresh until the message Repair process finished: <result> appears.
Result
The consistency check finishes with one of the following results:
· Repair process finished: no inconsistencies remain.
The consistency check has removed all inconsistencies from the database.
· Repair process finished: inconsistencies remain.
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.
Example
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:
· Principal ID
· Attribute namespace
· Attribute
· Value
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.
· If you choose to delete principal1, the consistency check deletes all the rows in the table.
· If you choose to delete attribute1 in namespace com.sap, the consistency check deletes the first two rows.
· If you choose to delete value x, the Consistency Check deletes only the first row.