Analyzing FTS logs to identify the FTS problem
To troubleshoot full text search (FTS) related issues, perform the following:
- Examine data in the following log files located in the <ARServerInstallDir>/ARServer/Db folder:
- arfts.log
- arfts-secondary.log
- arftsindex.log
- arerror.log
- arftsplugin.log
- arftsplugin-secondary.log
- armonitor.log
- arsql.log
- arftutil.log
To enable FTS index logging
- In a browser, open the AR System Administration Console, and click System > General > Server Information.
The AR System Administration: Server Information form appears. - Click the Log Files tab.
- To enable full text index logging:
- Select the Full Text Index check box.
- Select the option for the type of logging you want:
- File
- Form
- In the Name field, specify a log file name or form.
The default log file name is arftindx.log. The default form name is AR System Log: Full Text Index.
FTS index logging records all full text indexing operations to the full text indexer log but not full text searching operations. All logging for full text indexing is logged in the ARServerInstallDir/db/arftindx.log file. Entries in this log file represent the operations performed by the full text dispatcher and indexing threads, including the information sent to the search engine for modifying the indexes.
To enable SQL logging
- Select the SQL check box.
- In the Name field, specify a log file name or form.
The default log file name is arsql.log. The default form name is AR System Log: SQL. - Click OK.
SQL logging records all full text searching operations to the SQL log file, but not full text indexing operations. All logging for full text searching is logged in the ARServerInstallDir/db/arsql.log file, sharing the file with database logging. Entries in this log file that represent search engine activity are prefixed with FTS:.
For more information, see Setting log files options.