Invalid Source Domain Error When Validating OID 11g DIP Sync Import Profile Domain Mapping Rule (Doc ID 1291923.1)

Last updated on JUNE 30, 2017

Applies to:

Oracle Internet Directory - Version: 11.1.1 and later   [Release: 11g and later ]
Information in this document applies to any platform.

Symptoms

Using Oracle Internet Directory (OID) 11g and Directory Integration Platform (DIP).

Within EM FMW Control console, created an import synchronization profile with OID as destination.

Chose SunOne Directory as the source; the connection test to the Sun server works fine.

Created a domain mapping rule and provided the source and destination containers as required, but when validating the mapping rule, it returns error:
Invalid source domain

In trying to validate the profile, it returns error:
Domain rule "0" has error: Invalid source domain: 'ou=myou,ou=users,dc=mycompany,dc=com' not found

Going back into the Mapping tab and around the Source Container option, then using the lookup feature (that will allow to navigate and expand to the containers desired in the SunOne ldap server tree), it returns error:

[LDAP: error code 12 - The server is not configured to pass through control 2.16.840.1.113894.1.8.31]
javax.naming.OperationNotSupportedException: [LDAP: error code 12 - The server is not configured to pass through control 2.16.840.1.113894.1.8.31]; remaining name ''

javax.faces.el.EvaluationException: javax.naming.OperationNotSupportedException: [LDAP: error code 12 - The server is not configured to pass through control 2.16.840.1.113894.1.8.31]; remaining name ''
at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:58) at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1259) at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:90) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:309) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:94) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:97) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:90) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:309) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:94) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:91) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.broadcastEvents(LifecycleImpl.java:812) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:292) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:177) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:97) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420) at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247) at
....<etc, etc>....

Able to successfully traverse through the SunOne DIT tree using command line ldapsearch as well as a 3rd party ldap tool (JXplorer) while authenticated as the same SunOne user account used in the profile.

Also, the same SunOne user account configured in the profile was previously used with diptester tool in OID 10g for bootstrapping the initial load of user records, and then to sync only the change records from the same SunOne ldap server, both successfully.

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