Last updated on MARCH 02, 2017
Applies to:Siebel CRM - Version 8.1.1  and later
Information in this document applies to any platform.
On : Siebel 126.96.36.199  version
There are several scenarios related to this behavior.
When application server services are started, no information is recorded in enterprise log file. There are several application servers in this enterprise environment and the behavior is the same for all. Individual component logs are generated as expected.
The enterprise log file is created, but it only has the following contents:
2021 2013-11-22 06:16:13 0000-00-00 00:00:00 +0300 00000000 001 003f 0001 09 SiebSrvr 0 17891338 1 /siebel/siebsrvr/enterprises/ETPPRD/srv_prd1/log/ETPPRD.srv_prd1.log 188.8.131.52  ENU
ContextInit ContextInit 0 01467840524ea0c2:0 2013-11-22 06:16:13 SIEBEL_ASSERT_MODE = 0
<<< END OF FILE <<<
Components logs, including enterprise log, are not generated under log directory.
The enterprise log and some individual components logs are not generated under log directory.
Only some components logs with detailed logging enable are placed under log directory.
STEPS TO REPRODUCE
1. Stop the application server services.
2. Start the application server services.
3. Check the log directory:
Scenario 1: No information about components lifecycle is recorded in enterprise log file; the enterprise log file consists of only two lines.
Scenario 2: The log directory is empty.
Scenario 3: The enterprise log does not exist; there are some components logs with detailed logging enabled.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms