DIP 11g Provisioning to EBS Not Working After Bootstrapping User Accounts from AD. DIP Log Error: [LDAP: error code 4 - Sizelimit Exceeded]
(Doc ID 1355224.1)
Last updated on AUGUST 30, 2023
Applies to:
Oracle Internet Directory - Version 11.1.1 and laterInformation in this document applies to any platform.
Symptoms
11.1.1.x version, Directory Integration Platform (DIP)
After configuring synchronization with Active Directory (AD) and bootstrapping AD users in to OID, DIP provisioning to EBusiness Suite (EBS) stopped working.
The following error occurs in the MW_HOME/user_projects/domains/IDMDomain/servers/wls_ods1/logs/wls_ods1.out log.
ERROR
-----------------------
<29-Aug-2011 22:58:05 o'clock EST> <Error> <oracle.ldap.admin.ServerAccessWrappersJNDI> <BEA-000000> <Size Limit Exceeded. Failed.
Host='<OID_HOSTNAME>'
Details:
[LDAP: error code 4 - Sizelimit Exceeded]
javax.naming.SizeLimitExceededException: [LDAP: error code 4 - Sizelimit Exceeded]; remaining name 'cn=changelog'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3093)
-----------------------
<29-Aug-2011 22:58:05 o'clock EST> <Error> <oracle.ldap.admin.ServerAccessWrappersJNDI> <BEA-000000> <Size Limit Exceeded. Failed.
Host='<OID_HOSTNAME>'
Details:
[LDAP: error code 4 - Sizelimit Exceeded]
javax.naming.SizeLimitExceededException: [LDAP: error code 4 - Sizelimit Exceeded]; remaining name 'cn=changelog'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3093)
The issue has the following business impact:
Due to this issue, new users cannot access EBusiness Suite. Before integrating with AD, provisioning was working as expected.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |