Resource Access Information Is Not Visible in OIDDAS with Single Level Domain (Doc ID 352818.1)

Last updated on AUGUST 18, 2021

Applies to:

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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.