17.2 Troubleshooting Identity Manager Engine

The following table lists the issues you might encounter and the suggested actions for working on these issues. If the problem persists, contact your NetIQ representative.


Suggested Actions

While installing Identity Manager engine on OES, the following message is reported on the console and in the idminstall.log file located at /var/opt/netiq/idm/log/ directory.

Ensure that the /etc/OES-brand file exists on the OES server. If the file is not present, create a new file and try installing Identity Manager Engine again.

When you run Identity Manager Engine on Linux systems, the /tmp directory runs out of disk space in spite of the available space. You can check this status using df (disk free) and du (disk used) commands. The df command shows no available space while the du command shows that not all the space allocated for /tmp is used. This issue occurs because every Identity Manager driver that is instantiated loads several libraries in the memory. The JVM temporarily copies these drivers to /tmp directory and then deletes them. The deleted files continue to use the memory until the JVM process that created those files is terminated. You can use the lsof command to determine this behavior. Files in this state are marked as deleted. The total disk space consumed depends on the number of drivers running on the server.

The space consumed is relatively static.Therefore, ensure that you provide sufficient extra space in /tmp directory. If the issue persists, restart eDirectory.

In a multi-server environment, an unrecognized extended exception is displayed.

Ensure that the primary server has a read-write partition for the secondary server:

  1. Log in to iManager.

  2. Click Roles and Tasks > Partitions and Replicas > Replica View.

  3. Select the secondary server.

  4. Assign read-write permissions to the server.

NOTE:Ensure that you have added the secondary server in the driver set.