My Oracle Support Banner

OracleTextSearch Fails To Full-Text Index Special Characters (Doc ID 1391814.1)

Last updated on MAY 15, 2018

Applies to:

Oracle WebCenter Content - Version 11.1.1.3.0 and later
Information in this document applies to any platform.
@Currency check 11-Nov-14

Symptoms

On : 11.1.1.3.0 version, Webcenter Content Server:

When attempting to check-in Office document file with any special characters, that gets refined by IBR,
the indexer will fail to full text index and the following error occurs:
Note: Issue does not affect documents with normal characters. After changing the special characters to normal characters, the document will full-text indexes properly on resubmit.

 

ERROR
-----------------------
Full text index failed. Unexpected failure by Indexer.
Content has been indexed with Info only. Resubmit should only be performed if the problem has been resolved.

 

System audit log from the indexer:

>indexer/6 07.26 15:35:11.578 index update work Task 'Opt_FT_IdcText1' already exists. dSjState is 'A'. Last processed status is ''
>indexer/6 07.26 15:35:29.632 index update work preparing 1 items
>indexer/6 07.26 15:35:29.636 index update work doing conversion with intradoc.indexer.TextConversionHandler@1e1d25ed on intradoc.indexer.IndexerInfo@1e15be8e dID:239267 key:null mdo:false iwf:true sta:-1 alone:true
>indexer/6 07.26 15:35:29.676 index update work prepareDoc complete
>indexer/6 07.26 15:35:29.759 index update work Error occurred in content 'PDOC212029', DRG-11301: error while indexing document
indexer/6 07.26 15:35:29.759 index update work DRG-11302: document may be partially indexed
indexer/6 07.26 15:35:29.759 index update work DRG-11428: document contains invalid characters
>indexer/6 07.26 15:35:29.830 index update work preparing 1 items
>indexer/6 07.26 15:35:29.830 index update work prepareDoc complete
>indexer/6 07.26 15:35:29.907 index update work Task 'Opt_FT_IdcText1' already exists. dSjState is 'A'. Last processed status is ''

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Configure IBR to use WinNative conversion via Ghostscript
2. Check-in document with special characters like: the extended dash or superscript th, nd, st after a numbered street (2nd st.)
example: Hotel_Corporate_Rates_-2011[special_char_index_fails]

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot check-in these documents successfully.


NOTE: In addition to indexing issues, there have also been issues with hyperlinks not being converted from the Microsoft Office native to PDF, formatting errors with Microsoft Word tables being re-arranged and mis-interpreted, invalid characters when copying text from the resulting PDF version of the Microsoft Office document and other issues.



Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.