My Oracle Support Banner

OID 11g - EBS DIP Provisioning Profiles Not Getting Removed Completely on De-Registering (Doc ID 1915886.1)

Last updated on SEPTEMBER 26, 2024

Applies to:

Oracle Internet Directory - Version 11.1.1 and later
Information in this document applies to any platform.

Symptoms

Oracle Internet Directory (OID) 11g Directory Integration Platform (DIP) logs showing messages referencing old EBusiness Suite (EBS) provisioning profiles that were previously de-registered. 
Though this note was written for EBS provisioning issue, similar issue can occur with different Provisioning/Sync profiles.

This issue has been noticed in Oracle Label Security (OLS) as well.

On registering a DB including OLS with OID using DBCA.. IT creates provisioning profiles and the jobs are owned by the ODSSM schema. When deregister and reregister is done due to some issue... the same ODSSM tables do not get cleaned up after re-registering.. The profiles get recreated but the jobs show the old profile name.

Solution remains the same. DB tables listed below must be cleaned up.


Typical DIP diagnostic log (e.g., wls_ods1-diagnostic.log) error can be as follows:

Where this orclodipprofilename value indeed does not exist in OID, so OID is returning the correct/expected LDAP error (LDAP: error code 32 - No Such Object).

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


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