How to Prevent The File Cache From Growing Excessively During a Full Collection Rebuild

(Doc ID 1538810.1)

Last updated on MARCH 24, 2017

Applies to:

Oracle WebCenter Content - Version and later
Information in this document applies to any platform.


During indexing, files will be cached out to disk for documents that are stored inside the database using a JDBC FileStoreProdivder. Typically files will be removed from the cache after 7 days, which is the default value for the DatedCacheIntervalDays. 

However, during a full collection rebuild you may find that the file cache grows excessively as all content items will be cached out to disk and are not cleaned up. The FsCleanUpCacheDuringIndexing parameter (covered in Note 1064293.1) will not help as - per default - the cleanup cycle will only take place at the end of the rebuild.

The following instructions tell you how to keep the file cache under control during a full collection rebuild by kicking off a separate cleanup cycle during the rebuild.



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