High number of text_index events, as seen in the event log (System Policy> Events > Event Log) using the following lookup criteria

Created  ON Today

Queue = text_index

This output may show a high number of text_index events for the same table, with repeated columns (parm1)

such as can be seen here:

 column "Parm1" indicates the columns for which text indexes are being generated.   These text indexes are used for performing global searches in your instance.    This may be one or more columns represented, and separated by a comma(,).    Trends can be found by grouping by table, to identify specific table(s) for which there are a high number of text indexes generated.

 NOTE:  In some cases the large number of events can be for the same record.   If not already in your list view you can add the INSTANCE column, which reflects the sys_id value for the record updated/inserted for which the event was created.  If you see a high number of repeating values, check the record with the matching sys_id to understand what is causing the excessive indexes.


Release or Environment

Any release


Text_index events are generated when records are created or updated in a table for which text_indexing is active.   It is common for integration processes to touch numerous records in a given table, and can explain a flood of text_index events during given period of time.


If there are columns configured to generate text_index events on, which will NOT be used for text searches, it would be a good idea to disable text indexing on those column(s). 

This can be done by going to the dictionary for the table (see the table column in the output listed), and selecting the individual column(s).  Then add the attribute for no_text_index=true.  This will prevent further text_index events from being generated on those specific columns.

 You can also reference this documentation specific to removing text indexing for specific columns:

Article Information

Last Updated:2020-06-03 12:59:24