My Oracle Support Banner

OUD - Search Using Deeply Nested Filter Succeeds in ODSEE But Fails or is Slow in OUD (Doc ID 2385736.1)

Last updated on MARCH 07, 2019

Applies to:

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


Searching against OUD using a deeply nested search filter may fail or appear to hang.
The same search issued against ODSEE will succeed and return in a timely fashion.

Some additional observations when deeply nested search filters are employed against OUD...

- The search operation may never complete, even after an OUD server defined time limit of 1 minute.
- The load on the server may climb and the CPU being utilized by the OUD java process may increase.
- After ending the client application that issued the search with the deeply nested filter, CPU utilization for the OUD process may remain high.

Below is an example of a deeply nested search filter that causes problems on OUD. While the filter is not well formulated, it is still technically valid...

$Oracle_Home/OUD/bin/ldapsearch -h localhost -p 390 -D "uid=admin,ou=Directory Administrators,dc=example,dc=com" -w <PASSWORD> -b "dc=example,dc=com" "(|(uid=9742)(|(uid=9857)(|(uid=10065)(|(uid=10415)(|(uid=10569)(|(uid=10648)(|(uid=10714)(|(uid=11044)(|(uid=11049)(|(uid=11070)(|(uid=11094)(|(uid=11246)(|(uid=11595)(|(uid=11735)(|(uid=11883)(|(uid=11927)(|(uid=11984)(|(uid=12034)(|(uid=12067)(|(uid=12190)(|(uid=12231)(|(uid=12250)(|(uid=12264)(|(uid=12348)(|(uid=12360)(|(uid=12439)(|(uid=12527)(|(uid=13167)(|(uid=13431)(|(uid=13673)(|(uid=13723)(|(uid=13813)))))))))))))))))))))))))))))))))"



Migration from ODSEE to OUD.


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

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