Text Index with MULTI_LEXER Fails with DRG-50610 and DRG-11432 errors When Sub_Lexer has NEW_GERMAN_SPELLING enabled
Last updated on DECEMBER 03, 2012
Applies to:Oracle Text - Version 10.2.0.1 and later
Information in this document applies to any platform.
When creating a text index with multi_lexer preference that includes a sub_lexer with NEW_GERMAN_SPELLING set, then following errors
are logged in ctx_user_index errors view and therefore no token gets generated (the coresponding document is not indexed).
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