MaximumLogAgeDay Parameter Manually Modified in Logconfig.xml was not Loaded/Reflected in Fusion Middleware Control (Doc ID 2824081.1)

Last updated on NOVEMBER 25, 2021

Applies to:

Symptoms

MaximumLogAgeDay Parameter which is manually modified in logconfig.xml is not loaded/reflected in Fusion Middleware Control although <Note:2195581.1> solution is taken.

Reproduce Steps:
1. Set [Maximum Log Age] in Fusion Middleware Control(/em) to be 2 Days. After Activate, MaximumLogAgeDay is updated to 2 both in Fusion Middleware Control(/em) and logconfig.xml file.
2. Shutdown OBI Server Services.
3. Manually modify logconfig.xml and set MaximumLogAgeDay to be 5.
4. Start OBI Server Services.
5. [Maximum Log Age] is still 2 Days in Fusion Middleware Control(/em) although OBI services are stopped while modifying the logconfig.xml.

Cause

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