Troubleshooting FTS indexing issues
When you use the Full Text Search (FTS) functionality, you might encounter issues such as FTS not fetching expected results or FTS taking a long time to fetch results. See the guidelines described here to resolve the problem or to create a BMC Support case.
- You do not get any results because the index is not set correctly.
- The size of the
ft_pendingtable is increasing.
- You cannot add new records and the existing records are not processed.
- You get error messages while performing an FTS reindex.
- You observe a performance issue during the indexing process.
- Reindexing does not work.
- Scheduled/Scan time indexing does not work.
In a server group environment, this might impact one or more servers.
Perform the following steps to troubleshoot the FTS indexing issues:
Determine the type of indexing activity:
Determine the cause of indexing activity. It can be a user activity or there can be an automated process that causes indexing. Depending on the cause of indexing, different FTS operations can occur. You can view some of these operations in the
Use the FTS Management console to check if the server is currently performing a reindex activity
Perform the following steps to check if any server is performing reindex:
If the Re-Indexing In Progress value is set to Yes for any server, check if the form reindex is in-progress. Identify if the majority of indexing jobs are individual records or the entire form. Form reindexing takes a longer time to complete.
Enable logs and reproduce the problem.
Perform the following steps:
Use steps described in the Enabling server-side AR System logs topic to disable the logging. Disable the logs from each affected indexing server without fail.
Collect the logs
Copy logs to another location where you can view them. Ensure that the logs are not overwritten. The log file size can be large and it might vary depending on volume.
Review the symptoms and error messages. Use the table to troubleshoot the issue.
|6||Analyze the logs||You can review the logs yourself to try to identify error messages or behaviors. Use the table to help identify possible symptoms and solutions.|
|7||Creating a BMC Support Case|
Collect and send logs and detailed information when creating a case with BMC Support:
After you determine a specific symptom or error message, use the following table to identify the solution:
|ARERR 8760||On screen|
The arftindx.log file on the FTS Management console
|Data is not indexed|
The arftindx.log file and the
|AR System Server memory grows very high during the indexing process||Operating system tools|
FTS searcher plug-in potential memory leak.
Addressed in 1802 (9.1.04.02) hot fix package: SR_9104P2_20181128_CU_ALL.zip
|You get an error that FTS is either not licensed or the FTS service is not yet ready||The arftindx.log file|