After Crawler the Log Files Misses to Identify the Documents that have Conversion Failures
(Doc ID 2007505.1)
Last updated on MAY 07, 2020
Applies to:Oracle Secure Enterprise Search - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 11g]
Information in this document applies to any platform.
This documents addresses the need to rely on the crawler log-entries in order to resolve problems reported in the Crawler Summary Page.
In particular conversion failures are reported when documents can not be converted to HTML files, examples of such files are binary files, images, formats that are no known from specific applications we don't have filters for, etc.
The summary of metrics found in the crawler log at end of process show the following info:
(*) Conversion failures metric used to include both attached documents and embedded documents (content in a zip or jar file)
Problem was the crawler log file missed to identify which specific attached documents or which specific embedded files had the conversion failure, the log entries always referenced only the parent document.
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