My Oracle Support Banner

Different Error Code For Ldapsearch In OVD 11g & Backend Ldap (ODSEE) (Doc ID 1580646.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Virtual Directory - Version 11.1.1.6.0 and later
Information in this document applies to any platform.

Symptoms

The problem is with OVD 11g (11.1.1.6) release with WLS 10.3.5. Backend LDAP ODSEE 11.1.1.3.

In testing the configuration of OVD adapters a particular ldapsearch was found that would return no entries by OVD.  Also, no error returned.

Issuing the same identical search from a putty session, OVD did return the expected entry.

No further information available in OVD logs which tells us what is the difference in both searches (comparing application search with manual command line search)

It is found that the backend ODSEE logs report an error on the search. The search performed by the application 'failed' at backend ldap with an ldap error code 12 but OVD still returned error code as zero(OR no error at the prompt)


Desired outcome:  OVD error code must be same as backend ldap error code OR an error should be reported in the OVD logs.

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


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.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.