350 IBM Content Manager OnDemand Guide
Example 15-4   Content Manager OnDemand system log messages that relate to full text search
Message 397: Document Full Text Index Add: ApplGroupName(Adobe PDFs) Agid(5021) 
Full Text Index Notified(1) Count(16) Time(0.069)
Message 398: Document Full Text Index Add Failed: ApplGroupName(Adobe PDFs) 
Agid(5021) Full Text Index Notified(0) Count(16) Time(0.001)
Message 399: Document Full Text Index Delete: ApplGroupName(Adobe PDFs) Agid(5021) 
Full Text Index Notified(1) Count(16) Time(0.025)
Message 226: Application Group Query: Name(BaxterBayBank) Agid(5025) Time(0.120) 
Hits(2) Count() Sql(WHERE ODDAT_Sdate BETWEEN '1996-06-22' AND '2013-06-22' ) 
SqlR() FullTextSearch(lunch* newark) FullTextScore() ServerTextSearch() AnnColor() 
AnnText() OrderBy()
Message 439: FTS Error: IQQS0032E The query lunch~x cannot be processed because it 
has incorrect syntax. Causes of the problem:   IQQP9014E The query [lunch~x] 
cannot be parsed because there is a syntax error at position 7. The fuzzy argument 
value [x] is not valid because its data type is not float or double. -- 
File=arsfti.cpp, Line=394
Messages 397, 398, and 399 are viewable and contain the list of documents (their metadata) 
that are affected by this operation. In the case of message 398 (fail), the failure reason is 
documented, as well.
Each time the FTS Server reports an error, message 439 is issued, and it contains the error 
message that was returned by the FTS Server. In this case, the query that is entered by the 
user contained a wrong syntax for a proximity or fuzzy search.
15.7.2  Full Text Search Server log
Y ou can troubleshoot the FTS Server by configuring and viewing the FTS Server logs. The 
FTS Server generates logging information during server startup, indexing, and searching. 
The log files contain configuration information, warnings, errors, and debugging information 
that can be useful for monitoring the server and for troubleshooting specific issues. The 
command-line tools also generate log files. By default, log files are stored in the FTS_Home/log 
directory. Y ou can run the configTool with the list -logFolder command to see your log 
directory.
Every message in the log file has an associated level that indicates the message type. The 
logging levels, in descending order of severity, are defined:
/SM590000SEVERE: Errors and exceptions that occur while the server is running. Typically, SEVERE 
messages include detailed information with the stack trace.
/SM590000WARNING: Mild problems that might require the attention of an administrator, such as a 
missing value for a setting with a default value, or the truncation of a document during 
indexing.
/SM590000INFO: Informational messages that are generated during system operation.
/SM590000FINE: Detailed messages for debugging purposes. This level includes parsed queries.
/SM590000FINER: More details, for example, the results of document parsing.
/SM590000FINEST: The most detailed level.