Show TOC Start of Content Area

Procedure documentation Checking the Consistency of Entries in the UME Database  Locate the document in its SAP Library structure

Use

To eliminate inconsistency that can arise in the database of the user management engine (UME), use the UME consistency check.

Example

Some causes of inconsistencies include:

         Changing an external data source, such as a directory server, with external tools. This includes deleting a user, creating a user with the same unique ID as a user in the SAP NetWeaver Application Server (AS) Java database, or changing the unique ID of a user.

         Failure of an AS Java node.

If you regularly manage an external data source with external tools, consider running a consistency check on a regular basis.

Prerequisites

      The consistency check can generate a heavy load for your AS Java and any connected data source. Plan to run the consistency check when there is little user traffic. If necessary, remove a server node from load-balancing and run the consistency check on that server.

      You must have a user assigned to a role with one of the following UME actions:

       UME.Read_All enables you to run a consistency check, but you cannot repair any inconsistencies.

       UME.Manage_All grants you full access to the consistency check.

       UME.System_Admin grants you full access to the consistency check.

Procedure

...

       1.      Start the consistency check tool.

                            a.      Start identity management as a standalone or use the identity management quicklink for the SAP NetWeaver Administrator.

For more information, see Identity Management.

                            b.      Choose Consistency Check.

       2.      Choose Choose Working Directory.

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/.

Caution

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.

       3.      Save the working directory.

       4.      Choose Start Check.

Note

Choose Interrupt Check to stop the consistency check.

       5.      Choose Refresh until the message Check process finished: <result> appears.

The consistency check reports the result of the check process as well. The result is either inconsistencies found or not.

Result

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.

See also:

Standard UME Actions

 

End of Content Area