My Oracle Support Banner

How To Make Changes In oim-config.xml When OIM 11g Server(s) Are Unavailable (Doc ID 1378007.1)

Last updated on JANUARY 26, 2020

Applies to:

Identity Manager - Version 11.1.1.3.0 to 11.1.2.3.0 [Release 11g]
Information in this document applies to any platform.

Purpose

There may be situations where the OIM server is down and will not restart and configuration(s) have to changed in the oim-config.xml in the MDS; however, due to the OIM managed server being down, the usual approaches to doing so, such as the weblogicExportMetadata.sh/cmd scripts or the Enterprise Manager console, cannot be used. A particular scenario in which this may occur is if the OIM managed server hangs during startup and the thread dump shows it is hanging on JavaGroups - which depends on multicast address configured in oim-config.xml file:

java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x<THREAD_NUMBER1>> (a java.lang.Object)
at java.lang.Object.wait(Object.java:485)
at org.javagroups.JChannel.connect(JChannel.java:257)
- locked <0x<THREAD_NUMBER1>> (a java.lang.Object)
- locked <0x<THREAD_NUMBER2>> (a org.javagroups.JChannel)
at org.javagroups.blocks.NotificationBus.start(NotificationBus.java:116)
at com.opensymphony.oscache.plugins.clustersupport.JavaGroupsBroadcastingListener.initialize(JavaGroupsBroadcastingListener.java


How to change the configuration in oim-config.xml in such cases when all OIM managed servers are down?

Troubleshooting Steps

To view full details, 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 a vibrant support community of peers and Oracle experts.