The RebuildOptimizationInterval Parameter is not Interpreted
Last updated on MAY 10, 2017
Applies to:Oracle WebCenter Content - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
The RebuildOptimizerInterval parameter is not a time period interval, it is a delta based on the number of content items added + number of content items deleted + number of content items updated.
By default that delta number is 50000. When the change delta exceeds 50000, the optimizer gets executed.
Even if the parameter number is set and increased in the config.cfg file, the WebCenter Content server ignores the setting and will invoke the optmizer when 50000 changes are reached.
If a large number of content items are constantly added, deleted, or updated, this may cause the index to have the optimize process running almost all of the time. That may cause slow interactions between the WebCenter Content server and the database which usually manifests as a performance issue.
If the optimizer runs during an index collection rebuild, that also may cause the indexing to hang.
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