Resource Access Information Is Not Visible in OIDDAS with Single Level Domain
(Doc ID 352818.1)
Last updated on AUGUST 18, 2021
Applies to:
Oracle Internet Directory - Version 10.1.2.0.2 and laterInformation in this document applies to any platform.
This problem can occur on any platform.
Symptoms
- RADs are not visible in OIDDAS after they are created for both new users and seeded users (such as "Portal").
- Trying to create another RAD of the same name fails with das.log error:
javax.naming.NameAlreadyBoundException: [LDAP: error code 68 - Object already exists]; remaining name 'orclresourcename=gendv+orclresourcetypename=OracleDB, cn=Resource Access Descriptor , orclownerGUID=<orclguidvalue>, cn=Extended Properties , cn=OracleContext, dc=<COUNTRY>,dc=<DOMAIN>,dc=com' at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:2983) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2934) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2740) ...
- Users exhibiting the RAD problem are under a container which is parallel to the cn=users container.
- The RADs ARE in OID, however just not viewable in DAS
Changes
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 |
Changes |
Cause |
Solution |
References |