My Oracle Support Banner

Customization of Migration Application Log file name (Doc ID 2549996.1)

Last updated on AUGUST 15, 2019

Applies to:

Siebel CRM - Version 18.11 and later
Information in this document applies to any platform.

Symptoms

On : 18.11 version, Installation

ACTUAL BEHAVIOR
---------------
Files such as "migration.log", "CommonLogger.log" and "UI.log" don't seem to be rolling over after their maximum size is reached.

EXPECTED BEHAVIOR
-----------------------
Depending on the configuration in "ai\applicationcontainer\webapps\siebel\WEB-INF\log4j2-siebel.xml", when the file size of "migration.log", "CommonLogger.log" and "UI.log" reach "SizeBasedTriggeringPolicy", then should roll-over (create a new file, while renaming the existing file with a timestamp).

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Define "SizeBasedTriggeringPolicy" in "ai\applicationcontainer\webapps\siebel\WEB-INF\log4j2-siebel.xml" for "migration.log", "CommonLogger.log" and "UI.log" files.

2. Start Siebel application and continue regular day-today operations.

3. Notice how sizes of "migration.log", "CommonLogger.log" and "UI.log" files keep growing and not rolling-over.


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
Cause
Solution
References


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