11 Troubleshooting the Oracle Identity Manager Installation

The following sections describe problems that can occur during Oracle Identity Manager installation:

• Oracle Identity Manager Installation Fails During Installation in an Oracle WebLogic Server Cluster

• Task Scheduler Fails in a Clustered Installation

• Troubleshooting the JNDI Namespace Configuration

Note:

You can use the Diagnostic Dashboard tool for assistance when you troubleshoot Oracle Identity Manager. See Oracle Identity Manager Administrative and User Console Guide for detailed information.

Oracle Identity Manager Installation Fails During Installation in an Oracle WebLogic Server Cluster

The Oracle Identity Manager installation will fail during installation in an Oracle WebLogic Server cluster if incorrect values are defined for the target server and server port number. Do not define the Administrative Server as a target during the installation process. The setup script must create the JMS Server on a cluster member.

Workaround Example

The following is a sample procedure to clean up the Oracle WebLogic Server services so that you can continue with the installation:

1. Open the WebLogic Server Administration Console to clean up the services that have been created for the cluster.

2. Navigate to Services, JDBC, Data Sources, and then delete both data sources.

3. Navigate to Services, Messaging, JMS Servers, and delete the JMS servers.

4. Navigate to Services, Messaging, JMS Modules, and delete the JMS modules.

5. Navigate to Services, Persistence Stores, and delete the JDBC stores.

6. Open the OIM_HOME\Profile\weblogic.profile file, and then change the following:

   1. The Oracle WebLogic Server target name from myserver to <cluster_member1>.

   2. The Oracle WebLogic Server target port from 7001 to 7051.

7. Run the setup_weblogic.cmd script.

8. Review the log file to verify that the script has run successfully.

9. After the setup script runs successfully, restart Oracle WebLogic Server.

You can either continue with your installation (restart the Oracle Identity Manager Installer at this point), or start Oracle Identity Manager installation by removing all installed Oracle Identity Manager products as well as the WebLogic domain.

Task Scheduler Fails in a Clustered Installation

The Task Scheduler fails to work properly when the cluster members, which are computers that are part of the cluster, have different settings on their system clocks. Oracle strongly recommends that the system clocks for all cluster members be synchronized within a second of each other.

Troubleshooting the JNDI Namespace Configuration

If you create a user and that is the only user who can perform lookups, you might see the following exception when attempting to start Oracle Identity Manager where user_name represents the user you created to perform lookups:

[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: Authenticate/connect User with ID: user_name was not found in Xellerate.
[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: Authenticate/connect User with ID: user_name was not found in Xellerate.
[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: XellerateLoginModuleImpl/login encounter some problems:
com.thortech.xl.security.tcLoginException:
  at com.thortech.xl.security.tcLoginExceptionUtil.createException(Unknown Source)
  at com.thortech.xl.security.tcLoginExceptionUtil.createException(Unknown Source)
  at com.thortech.xl.security.Authenticate.connect(Unknown Source)
  at com.thortech.xl.security.wl.XellerateLoginModuleImpl.login(Unknown Source)
  at weblogic.security.service.DelegateLoginModuleImpl.login(DelegateLoginModuleImpl.java:71)

To resolve this issue, refresh the embedded LDAP directory in the Managed Server with the LDAP directory in the Administrative Server after starting Oracle Identity Manager as follows:

1. Log on to the WebLogic Server Administration Console.

2. Click the domain name under Domain Structure on the left pane.

3. Click the Security and Embedded LDAP tab.

4. Select the Refresh replica at startup option, and then click Save.

Note:

You must only perform these steps once to resolve this issue. You can disable the Refresh replica at startup option after restarting the Admin and Managed Servers.