How to remove high IO overhead on clustersync directory? (Doc ID 1507674.1)

Last updated on AUGUST 21, 2023

Applies to:

Goal

Why does ContentServer access clustersync files such as {clustersync}/myclustercsdatasourcecategory, {clustersync}/myclusterelementcatalog, etc?
It's causing a performance overhead, as it's accessing the file system each time a query is performed.

The following kind of messages can be found in the logs if accessing the files takes more than 500ms.

[2014-03-31 07:07:00.681][CS.SYNC][WARN] Setting state for {ft.sync}{data source}{tablename} took 3459 ms !!!

Is there any way to disable this behaviour?
 

Solution

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