Last updated on MARCH 08, 2017
Applies to:Oracle Internet Directory - Version 10.1.2 and later
Information in this document applies to any platform.
Ldapsearch filters not showing, or consistently showing, values for requested operational attributes, such as attributes that store time stamps, even though the attributes are verified to be indexed and contain values. This can also affect custom code, i.e., dbms_ldap or java code searches.
The following or similar symptoms can occur:
When searching for locked accounts, the ldapsearch results does not display / return the pwdaccountlockedtime attribute/value pair requested.
Other attributes requested are returned ok in the search results, including perhaps other operational attribute types such as orclguid.
Returns only the first three of the four attributes requested:
An ldapsearch requesting a single operational attribute does not return its name/value pair in the
search results. When requesting an additional attribute, i.e., two or more, then the search returns the expected results ok.
For example, the following ldapsearch does not does not return pwdaccountlockedtime even when the account is locked and the attribute is populated:
But when adding another attribute to be retrieved, then it lists all the expected values ok:
The same behaviour can happen for other attributes, such as pwdfailuretime for example.
OID schema defnition default values for the attribute(s) in question were changed.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms