Indexer Encounters Error On Every Document, Then Retries Everything
Last updated on FEBRUARY 07, 2018
Applies to:Oracle Universal Content Management - Version: 6.1 to 7.5.2 - Release: Stellent to Stellent
Information in this document applies to any platform.
A Content Server using Verity as the indexing engine is unable to index any documents. Even a batch size of one containing any document will fail the first time. After the first failed attempt to index the batch, the index will go into a retry state, during which the documents may get indexed. However, the indexer is slow to enter the retry state, significantly slowing down the speed at which documents get indexed.
WHAT DOESN'T WORK:
Documents fail on pass through the indexer.
WHAT DOES WORK:
Searching on previously indexed documents is not affected.
From the indexer tracing in the server output, error messages similar to the following are reported:
indexer 08.23 13:22:30.491 stderr read 93 bytes
indexer 08.23 13:22:30.491 stderr Warn E2-0527 (Document Index): Document 1 (z303233323434):
Stream error (-144) - SKIPPING
indexer 08.23 13:22:31.154 stderr read 98 bytes
indexer 08.23 13:22:31.154 stderr Error opening
indexer 08.23 13:22:31.165 stderr read 31 bytes
indexer 08.23 13:22:31.165 stderr Acrobat exception: 1074593822
Documents should get indexed during the pass through the indexer.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms