eG Help

Full Text Index is created to enable text search features on specific column in a table. Full Text index is bound to a defined column of a table. Conceptually, for efficient operational processing, full-text indexes perform search on columns in the same way that indexes support searching through books. DML (Insert, Update and Delete) and DDL (Create, Drop and Alter) commands on the table can impact/update the full text index. Full Text Index is automatically dropped when you drop a table or column on which index is created. SAP HANA automatically creates full-text indexes for columns of type TEXT and SHORTTEXT(n). For other column types, you must manually create any required full-text indexes.

Full-text indexes in a SAP HANA database must be created and updated in synchronization with the corresponding columns. This synchronization can be either synchronous or asynchronous. To handle asynchronous processing of text, SAP HANA uses queues. The queue is a mechanism used to enable a full-text index to operate asynchronously. This means that when you insert new entries into the column, the text is not made available in the column until it is preprocessed. When you insert new entries, the queue sends the text to the preprocessor for analysis. It returns a serialized instance of a DAF (document analysis format) object, which is then processed further by the HANA column store. The result is stored in the full-text index. The SAP HANA queue manager automatically creates a queue when you create an asynchronous full-text index or when the index server is started and the queue manager finds the information that a specific queue is needed. The queues are always created on the server on which the table is stored.

By monitoring the full-text queue status, administrators can determine the statistics pertaining to the tables and documents in the queue and be proactively alerted to any increase in the failed or suspended processes. This test reports the number of active and suspended tables in the queue and also reports the number of queued documents and error documents. This helps administrators to promptly resolve the bottleneck conditions before it leads to any server setbacks.

Outputs of the test: One set of results for the target database server instance being monitored.

Measurement	Description	Measurement Unit	Interpretation
totalTableCount	Indicates the total number of tables in the full-text index queue.	Number
activeTableCount	Indicates the number of active tables in the queue.	Number
SuspendedTableCount	Indicates the number of suspended tables in queue.	Number	A low value is desired for this measure. The detailed diagnosis of this measure lists the Schema name, Table name, Column name, Status, Indexed doxument count, Queued document count, and Error document count.
MaxQueuedDocCount	Indicates the number of documents in the queue during the last measurement period.	Number
MaxErrorDocCount	Indicates the number of failed documents during the last measurement period.	Number