OID 11g Creating/Saving DIP Profile Fails: Unable to save profile <profile_name> into the OID. An exception occurred while performing the save operation. | Error in deleting profile <profile_name>.
(Doc ID 1990957.1)
Last updated on AUGUST 27, 2019
Applies to:
Oracle Internet Directory - Version 11.1.1 and laterInformation in this document applies to any platform.
Symptoms
Oracle Internet Directory (OID) 11g with Directory Integration Platform (DIP).
Trying to create a DIP profile to synchronize users/groups with AD.
After entering all of the information and pressing OK, getting error:
Unable to save profile MyProfile into the OID.
An exception occurred while performing the save operation. Please view logs for more details.
Error in deleting profile MyProfile.
An exception occurred while performing the save operation. Please view logs for more details.
Error in deleting profile MyProfile.
The 'Additional Information' on the error shows:
javax.management.MBeanException: Error in deleting profile MyProfile.
at oracle.idm.integration.sync.profile.SyncProfileOIDDAO.delete(SyncProfileOIDDAO.java:2253)
at oracle.idm.integration.bean.SyncProfileBean.storeFromMemory(SyncProfileBean.java:1512)
at oracle.idm.integration.bean.SyncProfileBean.storeFromMemory(SyncProfileBean.java:1418)
...<etc>...
Caused by: javax.naming.OperationNotSupportedException: [LDAP: error code 53 - Server currently in read only mode. Update operations not allowed]; Remaining name: 'orclodipagentname=MyProfile,cn=subscriber profile,cn=changelog subscriber,cn=oracle internet directory'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3126)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2999)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2806)
at com.sun.jndi.ldap.LdapCtx.c_destroySubcontext(LdapCtx.java:856)
at com.sun.jndi.toolkit.ctx.ComponentContext.p_destroySubcontext(ComponentContext.java:665)
at com.sun.jndi.toolkit.ctx.PartialCompositeContext.destroySubcontext(PartialCompositeContext.java:348)
at javax.naming.InitialContext.destroySubcontext(InitialContext.java:492)
at oracle.idm.integration.sync.profile.SyncProfileOIDDAO.delete(SyncProfileOIDDAO.java:2236)
... 53 more
at oracle.idm.integration.sync.profile.SyncProfileOIDDAO.delete(SyncProfileOIDDAO.java:2253)
at oracle.idm.integration.bean.SyncProfileBean.storeFromMemory(SyncProfileBean.java:1512)
at oracle.idm.integration.bean.SyncProfileBean.storeFromMemory(SyncProfileBean.java:1418)
...<etc>...
Caused by: javax.naming.OperationNotSupportedException: [LDAP: error code 53 - Server currently in read only mode. Update operations not allowed]; Remaining name: 'orclodipagentname=MyProfile,cn=subscriber profile,cn=changelog subscriber,cn=oracle internet directory'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3126)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2999)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2806)
at com.sun.jndi.ldap.LdapCtx.c_destroySubcontext(LdapCtx.java:856)
at com.sun.jndi.toolkit.ctx.ComponentContext.p_destroySubcontext(ComponentContext.java:665)
at com.sun.jndi.toolkit.ctx.PartialCompositeContext.destroySubcontext(PartialCompositeContext.java:348)
at javax.naming.InitialContext.destroySubcontext(InitialContext.java:492)
at oracle.idm.integration.sync.profile.SyncProfileOIDDAO.delete(SyncProfileOIDDAO.java:2236)
... 53 more
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 |