To eliminate inconsistency that can arise in the database of the user management engine (UME), use the UMEconsistency check.
Some causes of inconsistencies include:
If you regularly manage an external data source with external tools, consider running a consistency check on a regular basis.
For more information, see Identity Management .
Enter the path the consistency check should use on the AS Java to write the consistency check and repair logs. The consistency check uses the default directory: /tmp/SAP_UME_DB_CHECK_RESULTS/ .
Make sure the directory you choose does not contain files you want to save. The consistency check deletes all files and subdirectories in the target directory.
Choose Interrupt Check to stop the consistency check.
The consistency check reports the result of the check process as well. The result is either inconsistencies found or not.
To view the results of the consistency check, choose View Check-Log. In the Log of Check Process view, you can see which principals (objects) the consistency check checked and any errors that resulted. The consistency check writes this log to the working directory under the filename check.log . Whenever you start a check process, the consistency check overwrites this log.
The log entries identify each principal that the consistency check checks with an INFO entry. The following entry indicates either INFO PASSED or ERROR with an error description. If the consistency check found an error, it follows the ERROR description entry with an ERROR FAILED entry. Each entry includes a time stamp.
With this information you can decide if you want to repair the UME data .