Weblogic Log files on Admin Server And Oacore_server1 seen with Excessive growth

[akhan]

Hi Arslan,

I am facing very strange issue, excessive logs and out files are generating in Admin and oacore server which is eating up storage very quickly. These files have been generated thousands in numbers.

We are on 12.2.6 version.

Please advice

Best regards,
AKhan

[ErmanArslansOracleBlog]

What are stored in those logs? Please check their content.. (any errors, any warnings, any clues...in general)
Did you enable any logging/debugging in EBS 12.2 (especially in Weblogic layer)?

[akhan]

Hi Erman,

Thanks for your reply.

I was working on SR with Oracle Support and was requested to enable BC4J logging from the WLS console.

Steps to enable BC4J loggin in 12.2:

1. From the WLS console:
a. Navigate to Environment -> Servers->oacore_server1>Logging >advanced and
ensure that the two checkboxes are checked.  
Redirect stdout logging enabled
Redirect stderr logging enabled  
b. Go to Environment->servers->oacore_server1->server start
In the arguments append "-Djbo.debugoutput=console"(without
the quotes).
Save whenever you make changes and also activate them.
Restart the oacore_server1.
Note: if you have multiple nodes, then do the same for every nodes

2. Bounce the managed server.

3. System.out and System error logs should be under the following directory:
 
$FMW_HOME/user_projects/domains/EBS_domain_<instance>/servers/oacore_server1/
logs/oacore_server1.out  
   Note: if you have multiple nodes, then collect the logs under every
oacore_server*

 I see that the below message is repeating too fast in the logs.

<Jul 12, 2018 7:30:32 PM AST> <Notice> <Stdout> <BEA-000000> <[222960] OADataBoundValueCustomization.getValue.BEGIN>
<Jul 12, 2018 7:30:32 PM AST> <Notice> <Stdout> <BEA-000000> <[222961] OADataBoundValueCustomization.getValue.NoCustIdRawValue>

Is it all because of enabling BC4J logging. Please confirm.

Best regards,
AKhan

[ErmanArslansOracleBlog]

Did this logging problem start after applying SR 's suggestion? (after enabling BC4J logging?)

This kind of logging activities should be done temporarily.
I mean, if you have an error, you enable the logging , reproduce the error and directly disable that logging..
When you reproduce the error while the logging is on, you gather lots of info about the errors that you are getting.. Thus you can analyze your problem..
So you should'nt be working with "logging on" all the time..

[akhan]

Hi Erman,

I have disabled those logging option and it stopped generating  excessive logfiles.

Thanks for your kind support.

Best regards,
AKhan