OID: Indexing a Custom Attribute Fails with Error: <Attribute Name> does not have any matching rule (Doc ID 2674890.1)

Last updated on AUGUST 22, 2022

Applies to:

Symptoms

1. Trying to index a custom attribute "<CUSTOM_ATTRIBUTE>" and it fails with the following error
 
Error "<CUSTOM_ATTRIBUTE>" does not have any matching rule.
Action: Modify attribute definition to include matching rule.

OR

2. Added a new custom attribute, as a single-value, numeric string with EQUALITY caseIgnoreMatch and SUBSTRING caseIgnoreSubstringsMatch.

Set OID to read-only mode and executed the catalog.sh command to index the attribute, but it fails with error:
<CUSTOM_ATTRIBUTE> does not have any matching rule or not supported.

Dumping the schema with command:

ldapsearch -h <OID_HOSTNAME> -p <OID_PORT> -D cn=orcladmin -w <PASSWORD> -b cn=subschemasubentry -s base -v "objectclass=*"

It shows the attribute as follows:

...< SNIP >...
attributetypes=( 2.16.840.1.113719.1.8.4.8 NAME '<CUSTOM_ATTRIBUTE>' DESC '<DESCRIPTION_OF_ATTRIBUTE_WITH_SINGLE_QUOTE>' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX '1.3.6.1.4.1.1466.115.121.1.36' SINGLE-VALUE )
...< SNIP >...

example:

attributetypes=( 2.16.840.1.113719.1.8.4.8 NAME 'MyAttribute>' DESC 'MyAttribute'sDescription' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX '1.3.6.1.4.1.1466.115.121.1.36' SINGLE-VALUE )

Cause

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