Text indexes not working properly
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-23-2025 05:56 AM
I recreated the text index using the following procedure:
Target table: Knowledge [kb_knowledge]
*This is an OOTB table.
However, the index value is always 1.
There are more than 100 records in the knowledge table.
It has been two days since the recreation, but it is still 1.
Is this a malfunction?
I would like to know the recovery procedure.
Will cloning from a healthy instance solve the problem?
Screenshots are included in the article below.
All configuration values ​​remain OOTB.
Even if a record is updated, the "text_index" event is not issued to the event table [sysevent].
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-07-2025 11:21 AM
We are having a similar issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-07-2025 03:49 PM
Do you have "no_text_index=true" set on your dictionary record attribute for your collection type?
This was the cause in my case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-17-2025 05:34 AM - edited ‎03-17-2025 06:02 AM
Check to see if this article provides some insight into the issue. If I have ever had any issue with text indexing the first place to confirm possible issues is the sysevent table. There is an event registered into the table for the full indexing job (text_index.all). Is the job present in the table, how long was it running? I would probably go into the node logs to see if I would locate any clues to what is causing the issue.
How to track the progress of text indexing (or reindexing) and tell if it has completed
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0694751
- Jan