SAP Knowledge Base Article - Preview

3371565 - TRexAPI_StopwordAndTermMappingUtil_tokenizerCacheLock lock contention in SAP HANA


You notice thread samples in state Mutex Wait waiting on lock TRexAPI_StopwordAndTermMappingUtil_tokenizerCacheLock. You may ascertain this using HANA_Threads_ThreadSamples_LockHierarchy_<version> included with 1969700.

Statement hash be788bf5f4482e70db907fbf7c73d857 is one known example associated with this scenario:

/* procedure: "SAPSR3"."/SAPSLL/CL_SPL_HANA_SEARCH=>CHECK_NAME_COUNTRY" variable: HITS line: 28 col: 7 (at pos 990) */ SELECT guid_tspl  AS guid_tspl,
                    guid_tspln AS guid_tspln,
                    CAST(HIGHLIGHTED(single_string_name) AS NVARCHAR(250)) AS mch_kws,
                    TO_INT(SCORE() * 100) AS score
                    FROM "/SAPSLL/CL_SPL_HANA_SEARCH=>/SAPSLL/TSPLN#covw"
                    WHERE mandt = SESSION_CONTEXT('CLIENT')
                     AND CONTAINS( single_string_name, __typed_NString__($1, 250),
                                   FUZZY($2, $3) )

However, lock contention on TRexAPI_StopwordAndTermMappingUtil_tokenizerCacheLock may occur in any scenario involving a high number of parallel search operations.



SAP HANA, platform edition


SAP HANA, platform edition all versions


TRex, Mutex, Tokenizer, TRexAPI_StopwordAndTermMappingUtil_tokenizerCacheLock, Mutex Wait , KBA , HAN-DB-ENG , SAP HANA DB Engines , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.