OIDADPSWD Package Invalid After Running PSA for ODS Schema After Applying OID 184.108.40.206 PatchSet (PS6)
(Doc ID 1905697.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Internet Directory - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Upgrading from an Oracle Internet Directory (OID) 10gAS instance which was using the pl/sql external authentication plugins.
The upgrade also involved creating/using the new java based plugins, which are now in use and working, and no longer using the plsql plugins that were in place in 10g.
However, when patching to OID 18.104.22.168 following:
Oracle® Fusion Middleware Patching Guide 11g Release 1 (22.214.171.124.0) Part Number E16793-25
Chapter 4 "Updating your Schemas with Patch Set Assistant
Section 4.4.4 "Checking for invalid database Objects"
At this point, the package ODS.OIDADPSWD is invalid and will not compile.
Reviewing the dba_errors log, it fails in two sections of the code - both of which are calling the package ODS.LDAP_PLUGIN and use the function get_adupname contained within.
The problem seems to be that a new ODS.LDAP_PLUGIN package was installed with the 126.96.36.199 upgrade. The previous version of the ODS.LDAP_PLUGIN package, i.e. 188.8.131.52, contains the functions needed.
So seems the code in the LDAP_PLUGIN package changed. Several functions were removed with the running of Patch Set Assistant (PSA) under the 184.108.40.206 OID update. Able to reference another test build that still has 220.127.116.11 OID, and that version has the functions called by OIDADPSWD. In fact the code in 18.104.22.168 OID matches line for line to a production 10.1.2.3 OID install. Seems that, until 22.214.171.124 came along, then that the package was modified.
For now as a workaround, just ignoring the package validation since it is not longer needed or used (as the java based plugins are used instead).
Upgraded to 126.96.36.199.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|