Last updated on JANUARY 11, 2015
Applies to:Identity Manager - Version 188.8.131.52.14 to 184.108.40.206.4 [Release 11g]
Information in this document applies to any platform.
Missing Lexers post upgrade.
In attempt to run complete technote: How to Fix Corrupted Index to Resolve IAM-7130123 error in OIM Catalog Search (Doc ID 1607412.1)
select * from catalog where catsearch(tags,'TestApp') > 0;
ORA-29900: operator binding does not exist
ORA-06553: PLS-306: wrong number or types of arguments in call to 'CATSEARCH'
29900. 00000 - "operator binding does not exist"
*Cause: There is no binding for the current usage of the operator.
*Action: Change the operator arguments to match any of the existing
bindings or add a new binding to the operator.
Then, when running the blocks from the technote to rebuild the index, we received errors:
How to Fix Corrupted Index to Resolve IAM-7130123 error in OIM Catalog Search (Doc ID 1607412.1)
1. Lexer CATALOG_PREFERENCE does not exist
OIM_PKG_CATALOG_INDEX to remove references to CATALOG_PREFERENCE and replaced them with BASIC_LEXER, like:
' on CATALOG(TAGS) indextype is CTXSYS.context ONLINE FILTER BY CATEGORY parameters('' sync (on commit) lexer BASIC_LEXER'')';
Then we get error:
2. Lexer BASIC_LEXER does not exist
So we removed that reference from OIM_PKG_CATALOG_INDEX as follows:
' on CATALOG(TAGS) indextype is CTXSYS.context ONLINE FILTER BY CATEGORY parameters('' sync (on commit)'')';
Then able to run the PL/SQL block from the tech note and to see all existing application instances in the catalog UI by searching for their names.
Need to resolve the issue of the fact that those 2 lexers which come packaged with OIM are currently not present.
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