Performance Issue Caused by Capturing Trace Output in "IdcServer.log", "IdcServerNT.log", "debug.log", or "log" (Doc ID 946079.1)

Last updated on MAY 01, 2017

Applies to:

Oracle WebCenter Content - Version 7.5.0 to 10.1.3.5.0 [Release Stellent to 10gR3]
Information in this document applies to any platform.
Performance issues that are pervasive across UCM can be created by the growth of a trace file. If the trace file has become several gigabytes, this performance problem can occur. When UCM tries to write to the file, performance degrades since writing to the file requires a large around of memory. The performance problems can become more acute when UCM is performing an action that has tracing enabled, such as a collection rebuild when the "indexer" tracing option is turned on and set to be "verbose."

Loading a large trace file into memory can consume much of the available memory and create excessive swapping. UCM becomes slower as a result.
-----
The UCM system-level trace files on Windows are: /bin/IdcServer.log, /bin/IdcServerNT.log, and /bin/debug.log.
The UCM system-level trace files on UNIX/Linux are: /etc/log and /bin/debug.log.
----


Symptoms

Content Server performance in general has become slower when performing certain actions.  Various processes runs noticably slower than they have in the past and nothing has changed on UCM. 

Cause

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