My Oracle Support Banner

Obsolescence of KOREAN_LEXER Lexer Type (Doc ID 300172.1)

Last updated on MARCH 05, 2019

Applies to:

Oracle Text - Version 10.2.0.1 to 11.1.0.7 [Release 10.2 to 11.1]
Information in this document applies to any platform.

Symptoms

Obsolescence of the KOREAN_LEXER lexer type was first announced in Oracle Text Release 9.0.1.  Beginning with Oracle Text Release 10gR2, it is discontinued. This means that users can no longer use the KOREAN_LEXER in Release 10gR2.  They must migrate to the KOREAN_MORPH_LEXER lexer type.  This discontinuance will manifest most commonly as the following two problems:

After upgrading to 10gR2, if the pre-10gR2 Text index was using KOREAN_LEXER then after the upgrade, most all operations including queries on such index will fail. The following error will be included on the error stack in such cases:

DRG-13201: KOREAN_LEXER is desupported


When importing a pre-10gR2 dump file to 10gR2 in a manner which creates the Text index (e.g. INDEXES=Y with imp), if the Text index uses KOREAN_LEXER then creation of that index will fail with the following errors on the error stack:

DRG-10502: index <index_name> does not exist
DRG-13201: KOREAN_LEXER is desupported

Cause

To view full details, 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 a vibrant support community of peers and Oracle experts.