OID 11g - Ldapsearch Filtering On Custom Indexed Attributes Returns Nothing / No Results
Last updated on MARCH 08, 2017
Applies to:Oracle Internet Directory - Version 11.1.1 and later
Information in this document applies to any platform.
Oracle Internet Directory (OID) 11g, For example: 188.8.131.52.
The OID Database (DB) underwent an upgrade from 10g to 11g and was cloned from a staging data.
Created then indexed a custom attribute used for user authentication, but unable to query filtering on the attribute; it returns no results / nothing.
Sample query used to test searching for the attribute:
Steps used to index the attribute:
- Confirm that field to be indexed has a matching rule.
- Start oidadmin.
- Look in Schema Management System Object.
- Select the Attributes tab.
- Find field to be indexed and choose Edit button.
- Select the Advanced tab.
- Modify the Equality attribute to be “caseIgnoreMatch”
- Run catalog command from $ORACLE_HOME/ldap/bin:
Already tried stopping and restart OID server, and unindexing/reindexing the attribute using catalog tool. An OID debugged log shows no errors. Also, an oiddiag report shows the attribute definition is correct in the OID 11g schema and it shows as indexed ok.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms