OID 12c - Oracle E-Business Suite DIP Provisioning Profiles are not Deleted Correctly during Deregistration (Doc ID 2696288.1)

Last updated on JULY 31, 2020

Applies to:

Symptoms

Provisioning from Oracle Internet Directory (OID) 12c to Oracle E-Business Suite using Directory Integration Platform (DIP) fails in an environment where the DIP Managed Server (wls_ods1) was down during an OID de-registration, followed by an OID re-registration.

Oracle Directory Integration Platform (DIP) 12c log files display messages referencing old Oracle E-Business Suite provisioning profiles that were previously de-registered.

Registering Oracle E-Business Suite with OID creates provisioning profiles and will write associated data to several ODSQTZ tables in the ODSSM schema. When de-register and re-register is performed, if for any reason the DIP Managed Server (wls_ods1) was down during the de-registration process, these ODSSM tables do not get cleaned up correctly after re-registering.The provisioning profiles are recreated but the jobs show the old profile name. If your provisioning profile includes provisioning from OID 12c to Oracle E-Business Suite, you will see that this provisioning does not take place.

The solution is to clean up these tables before performing a valid registration, to create a valid provisioning profile and corresponding entries for the same provisioning profile in the ODSQTZ tables in the ODSSM schema.

The solution in this document is specific to OID 12c only, if you encounter this issue with OID 11g, you should instead refer to My Oracle Support Knowledge <Document 1915886.1>, OID 11g - EBS DIP Provisioning Profiles Not Getting Removed Completely on De-Registering.

Cause

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