Oracle Text and UCM - Lexer Configurations
(Doc ID 871212.1)
Last updated on MAY 22, 2020
Applies to:Oracle WebCenter Content - Version 10.0 to 220.127.116.11.0 [Release 10gR3 to 11g]
Information in this document applies to any platform.
***Checked for relevance on 03-April-2011***
UCM uses Oracle Text to index the extracted text of content items. As the extracted text of content items is inserted into the indexes, a process of lexical analysis is performed, which tokenizes the indexable words of the text. The lexer settings in the database can affect and alter the manner in which text is stored and accessed in the database indexes, as well as how content items are searched upon through the UCM interface.
Appendix D of the Oracle Text Reference guide discusses lexer types in greater detail. This note will demonstrate use of several lexers that can be used with UCM. The examples contained here assume the database version is at least Oracle 18.104.22.168. Another assumption made is that in the file <UCM>/config/config.cfg the config setting SearchIndexerEngineName should be set like
The examples below have not been fully tested with a config setting of SearchIndexerEngineName=DATABASE.FULLTEXT.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|UCM Default Lexer|
|Which lexer to use?|
|Using the BASIC_LEXER or AUTO_LEXER|
|Using a Multi-Lexer|