Troubleshooting the indexer for text search

These topics can help you solve common problems when using the text search support in IBM® Content Manager.

Incorrect Net Search Extender configuration
IBM Content Collector text search support requires that all text indexes managed by Net Search Extender be created with specific index configuration settings. If these settings are not configured correctly, the text search result set might not be not complete, or might even be empty.
The item type cannot be processed by an indexer tool
The indexer tools (afuIndexer, afuCreateIndex, afuConfig, or afuCheck) cannot process the item type that was passed.
The existing full-text index is not compatible with the new index configuration
If you run any of the indexer tools on an existing item type with an index configuration that was created using an IBM Content Collector Text Search Support version before V4.0, configuration errors are reported. The item type cannot be indexed.
IBM CommonStore email item types cannot be enabled using afuEnableItemType
Item types with a document data model cannot be enabled for indexing using the IBM Content Collector afuEnableItemType indexer tool.
A native DB2 library cannot be loaded
The native DB2 library db2jcct2 cannot be loaded.
Running the indexing tools on Linux using a DB2 version on 64-bit
Running any of the indexer for text search tools on Linux using a DB2 version on 64-bit results in errors if the DB2 instance uses the 32-bit JDBC driver. You must modify your environment settings and ensure that these changes take effect in the current Linux shell itself.
DB2 installation directory cannot be located
You must define the environment variable DB2HOME before you run the indexer tool afuRecreateIndex.
DB2 is performing lock escalation
DB2 performs lock escalation internally to reduce the number of locks held.
JDBC throws java.io.CharConversionException
Sometimes the afuIndexer process unexpectedly throws a Java exception during document processing and indexing.
No index is found after the index is re-created
Re-creating an index using the same name and location as the dropped index results in an error stating that the index cannot be found.
Net Search Extender stops unexpectedly without issuing a COMMIT
The indexer process stops unexpectedly because Net Search Extender detected a fatal error.
Net Search Extender fails while indexer process is running
The Net Search Extender might fail if a required DB2 fix pack is missing.
Finding a document that could not be searched
If you cannot find a document when searching for it, you should check if it was indexed correctly.
The indexer process stops because the AFUFetchFile UDF cannot be accessed
The AFUFetchFile UDF used by Net Search Extender must be registered in DB2.
Obtaining the DB2 port number
You must know the DB2 database name and the connection port number to configure a connection between the system administration client and the remote DB2 database.
Using SQL statements that are very long or complex
SQL statements that are either too long or very complex result in an SQL0101N error message.
Using an incorrect JDBC setup for the indexer processes
The SQL error SQL1224N is caused by an incorrect JDBC setup.
The JDBC type 2 driver cannot be loaded correctly
The afuIndexer process cannot be started, displaying an SQL error message stating that a native library could not be loaded.
Items with textual content greater than 1 MB are not indexed when using DB2 V9.5
If you are using DB2 Universal Database V9.5 and the indexer for text search, items which have a textual content that is greater than 1 MB might not be indexed.
The indexer process stops because the index cannot be found
The indexer afuIndexer process stops and an error message is displayed stating that the index does not exist.
Changes to the default directory and file name settings of the AFUFetchFile UDF configuration
The indexer process automatically creates and maintains a binary configuration file called AfuFetchFile.config which is used by the AFUFetchFile UDF.
Error accessing XML files in the AFUFetchFile UDF
The indexer process is unable to access the XML files which contain the document content that is to be indexed.
Error accessing XML files in the AFUFetchFile UDF if the item ID consists of question marks
The indexer process is unable to access the XML files which contain the document content that is to be indexed if the item ID consists of question marks (?).
The indexer worker process stops indicating an out of memory situation
Sometimes the indexer worker process stops and assumes that there is not enough memory to continue processing.

Parent topic: Troubleshooting Content Collector