Troubleshooting indexing

Confirmation that the index service is configured successfully for a specific database is available in several places.

To detect if your search index is configured correctly, search for information in your database that you know is present, and check the results that are returned. If the results are not as you expect:

Check that the index was run since you added the record

The index only contains information about records that were available when the last index was created. The data and time that the index took place is displayed at the top of the following screens:

• i2 iBase Designer > Tools > Search > Search 360 Administration

• i2 iBase > Tools > Analysis > Search 360

If your record was added after this time, run the index to refresh the information it has stored.

Check the SQL Server indexing job for information about the indexing job

In SQL Server Management Studio, SQL Server Agent lists an i2_Search_Indexing job for the database, which reports success or failure in the SQL Server Agent job history. The messages this contains can be used to determine any problems such as issues with the installed iFilters for including different types of document.

Note: In addition, the SQL Server Agent must be running for the indexing to take place.

Check in the Windows™ Event Viewer for details about scheduled indexing

In the Windows Event Viewer, started and completed events are listed for the database. You can use the service logs for more information.

Note: Depending on the frequency with which the index service runs, you might want to change the properties of the Windows Event Viewer log file. For example, change its size or control what happens when the maximum log size is reached.

Run the indexing service from the command line

You can use the iBase Indexer tool via the command line to see the progress of an index in real time. For more information on running the index service, see Configuring the index service manually.