DMP Files Generated for EnableServiceArgTracing and EAI Component Logs are Saved in Different Locations on Various Siebel Servers (Doc ID 2879102.1)

Last updated on MARCH 01, 2024

Applies to:

Symptoms

Actual Behaviour:
On a Production environment, the .DMP files generated from various Inbound Web Services requests - are stored into different locations on the 4 servers in this Siebel Enterprise.

On 2 of the servers the DMP files are always generated under the {siebsrvr/log/} directory. On another server the DMPs are always generated under the {siebsrvr/enterprises/<Enterprise_Name>/<Server_Name>log/} directory, while at the forth server there are no DMP files generated at all. This behavior is persistently observed at all these four machines when EnableServiceArgTracing = TRUE.



Expected Behaviour:
That should be consistent - for all servers as long as those are setup similarly, the DMPs should be written in the same locations / folders.
And if there may be any environment variables or individual components' settings to instruct Siebel to write logs and / or .DMP files to a specific location, those should be respected.

Steps to replicate:
1. set the parameter EnableServiceArgTracing = TRUE for the EAI component;
2. test and monitor the inbound requests;
3. check for the DMP files and EAI logs location - and observe these were stored inconsistently in different places on different servers.

Changes

Cause

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