OIM Becomes Unresponsive After Sandbox Is Imported From Another Environment (Doc ID 2102433.1)

Last updated on MARCH 16, 2016

Applies to:

Identity Manager - Version 11.1.2.0.0 and later
Information in this document applies to any platform.

Symptoms

The OIM environment becomes unresponsive after a sandbox is imported from one environment to another environment.

Steps to reproduce:

Box 1:
====

1. Create a Sandbox named SampleApp1.

2. Create an Disconnected Application Instance of SampleApp1. Use OOB
form as default form.

3. Publish the sandbox.

4. Run the scheduled catalog synchronization job.

5. Test provisioning users to SampleApp1.

6. Create a Sandbox named SampleApp2.

7. Create an Disconnected Application Instance of SampleApp2. Use OOB
form as default form.

8. Export SampleApp2 Sandbox.

9. Publish the sandbox.

10. Run the scheduled catalog synchronization job.

11. Test provisioning users to SampleApp2.

12. Export the SampleApp2 configuration files through Deployment Manager.

Box 2:
====

 

Make sure there is no Application Instances of SampleApp1 and SampleApp2.

1. Import the SampleApp2 configuration files through Deployment Manager.

2. Import the SampleApp2 Sandbox.

3. Publish the SampleApp2 Sandbox or Activate the imported SampleApp2 Sandbox in Self Service Interface.

4. Run the scheduled catalog synchronization job.

5. Create a new user from Self Service Interface. The OIM should become unresponsive.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms