Content Server's Content Categorizer Process Can Leave Behind Large Files In Temp Directory
(Doc ID 1519478.1)
Last updated on APRIL 09, 2024
Applies to:
Oracle WebCenter Content - Version 10.0 and laterInformation in this document applies to any platform.
Symptoms
When checking in large files (+10 MB) into the content server, click on the 'Categorize' button from the Content Categorizer component.
Large temp files can remain in the /tmp directory after the content is categorized.
The categorization process fills in metadata based on rules set in Content Categorizer.
The Configuration entry MaxIndexableFileSize=<size in bytes> works to prevent large files from being indexed. It does not work for Content Categorizer. Categorizer will push through the large files in OIT no matter the config.
Changes
Large files (10+ MB) are being checked in.
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 |
Changes |
Cause |
Solution |
References |