Known problems and solutions
These troubleshooting topics provide descriptions of and
solutions or workarounds for problem situations that you might encounter.
Refer to this troubleshooting information to understand what condition
or event generated your problem situation and to find out what you
need to do to recover from or work around a problem, or to prevent
a recurrence of the problem.
Text extraction can fail for PDF documents that use embedded fonts
Text extraction from a Portable Document Format (PDF) document that uses embedded fonts can fail. IBM Content Search Services is unable to index or search on these documents.
Text extracted from a document during indexing is truncated
The amount of extracted text from a document is exceeding a configuration setting, which prevents some of the text from being indexed.
Indexing a document fails with an error.
When indexing a document, warnings and a Failed to convert error are generated, which indicates that a content element file for the document could not be converted.
A query returns unexpected results
A query for objects returns unexpected results.
Indexing a document fails with an error
The Content Platform Engine generates an error stating No token or line breaks when a content element file incorrectly has a MIME type of text/plain.
Indexing a document results in timeout messages
The Content Engine server reports timeouts while indexing data.
The server experiences an out-of-memory condition
An IBM Content Search Services server is logging an out-of-memory error.
Content Platform Engine server runs out of disk space
The temporary files that are created for content-based retrieval activities are not being removed. The accumulation of these temporary files can cause out-of-disk problems.
Indexing into many full-text indexes causes an error
An error occurs when an IBM Content Search Services server performs concurrent index operations on many full-text indexes.
Indexing fails because disk is full
The temporary folder used for indexing has specific usage and size requirements.
Indexing fails because no index areas are available
No index areas are available to receive new index information.
Indexing is delayed because of low disk space
Text extraction consumes too much disk space during the Content Search Services (CSS) indexing process.
The Content Platform Engine server is unable to retrieve content data from the content directory during full-text indexing
During full-text indexing, the Content Platform Engine server is unable to obtain content data from the content directory for processing.
AIX server runs out of memory when documents are indexed
While the IBM Content Search Services server is indexing documents, the AIX® server runs out of memory.
Upgrading an object store when its text language is set to auto causes an error
When you upgrade an object store from Content Cortex version 5.0.x or 5.1.x and the text language is set to auto, an error occurs.
Index processing is delayed
When you create an index request, the index request is scheduled to be created later by the Content Platform Engine server.
Database first search runs slowly
When you run a database first search, either by using the SQL option CBR_DB_FIRST or as the result of a dynamic switching choice of database first, the IBM Content Search Services server takes a long time to return the search results.
Dynamic switch search does not choose database first when the expected hits are more than the threshold
In a dynamic switch search, the database first algorithm is not chosen by the IBM Content Search Services server when the expected number of hits are more than the threshold value.
Creating an index area fails with an error
An index area cannot be created because the version of the IBM Content Search Services server is incompatible with the version of Content Platform Engine .
Text extraction processes fail to start on a UNIX system
When IBM Content Search Services performs text extraction as it indexes documents on a UNIX system, the text extraction processes fail to start because the UNIX open file limit is exceeded.
Document search fails when morphological index is created with Chinese, Japanese, Korean characters
Content Search Services search fails when morphological index is created with Chinese, Japanese, Korean characters.
Finding additional problem/solution information
If you cannot find a solution to a problem that you encounter when you use IBM Content Search Services , use the resources listed in this topic to discover additional solution information.