OID / DIP Provisioning Synchronization Not Working In Portal Unable to Recreate Users in Portal (Doc ID 1281967.1)

Last updated on DECEMBER 23, 2016

Applies to:

Portal - Version 10.1.2.0.2 to 10.1.4.2 [Release 10gR2]
Information in this document applies to any platform.
Checked for relevance on 17-Feb-2015

Symptoms

DIP Provisioning to Oracle Portal is not working.

When a user is deleted and recreated with the same name in OID , the portal.wwsec_person$ table is not being correctly updated.

The following error is shown when the user attempts to log into Portal.

Error: Internal error (WWC-00006)
Unexpected error encountered in wwsec_app_priv.process_signon (User-Defined Exception) (WWC-41417)
There is a conflict with your assigned user name. There is a user entry with this name, but with a different globally unique identifier, which must be resolved before you can log on with this name. Please inform your administrator. (WWC-41742)



DIP Trace log shows:

Error in Mapping EngineODIException: Exception Connecting to DB :java.sql.SQLException: Io exception: JNDI Package failurejavax.naming.NameNotFoundException: [LDAP: error code 32 - No Such Object]; remaining name 'cn=<SID>,cn=oraclecontext'
ODIException: Exception Connecting to DB :java.sql.SQLException: Io exception: JNDI Package failurejavax.naming.NameNotFoundException: [LDAP: error code 32 - No Such Object]; re
maining name 'cn=<SID>,cn=oraclecontext'

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