20081210 apps user does not have permission to access dbms_ldap package - plembo/onemoretech GitHub Wiki

title: APPS user does not have permission to access dbms_ldap package link: https://onemoretech.wordpress.com/2008/12/10/apps-user-does-not-have-permission-to-access-dbms_ldap-package/ author: lembobro description: post_id: 420 created: 2008/12/10 17:35:26 created_gmt: 2008/12/10 17:35:26 comment_status: open post_name: apps-user-does-not-have-permission-to-access-dbms_ldap-package status: publish post_type: post

APPS user does not have permission to access dbms_ldap package

This is an Oracle EBS (Enterprise Business Suite) thing.

The error would be something like:

Unabled to call fnd_ldap_wrapper.update_user due to the following reason:
OID is not registered correctly. Please contact system administrator.

This happens when trying to create a new user or reset a password from the EBS side.

The mis-spelling is literal. Another mark of the high quality one comes to expect from Oracle software.

Up to now I’ve only seen this very generic error in an EBS/OID integration when there is no corresponding user entry in OID for the subject EBS user account. But in MetaLink Note 365378.1 the blame gets pinned on the APPS user not having permission to access the dbms_ldap package.

The fix is to apply the correct permissions (see diagnostic query below before trying this).

Grant ALTER ANY PROCEDURE to apps; Grant CREATE ANY PROCEDURE to apps; Grant CREATE SNAPSHOT to apps; Grant DROP ANY PROCEDURE to apps; Grant QUERY REWRITE to apps; Grant RESUMABLE to apps; Grant UPDATE ANY TABLE to apps;

To check whether you really are experiencing an APPS account permissions problem, Oracle suggests running these two queries.

SQL> select OBJECT_NAME from ALL_OBJECTS where OBJECT_NAME = 'DBMS_LDAP' and OBJECT_TYPE = 'PACKAGE BODY' and STATUS = 'VALID' and OWNER = 'SYS';

SQL> select OBJECT_NAME from DBA_OBJECTS whereOBJECT_NAME = 'DBMS_LDAP' and OBJECT_TYPE = 'PACKAGE BODY' and STATUS = 'VALID' and owner = 'SYS';

If the first query does not return any rows, but the second does, you apparently have a permissions issue.

Of course the particular error that led us to this code turned out not to be due to this problem, but hey, that’s why working with Oracle is so much fun.

And Larry, I’m not laughing any more.