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 126.96.36.199.0 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...
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