About Flight Data Recorder Log Files
Siebel flight data recorder (FDR) files are records of system and server component behavior at run time. In the event of a system or server component failure, the settings and events leading up to the failure are captured and logged. You can send the Siebel flight data recorder log file to Oracle Global Customer Support by creating a service request (SR) on My Oracle Support. The log file is used to troubleshoot and analyze the specific settings and events that occurred before the failure.
The Siebel flight data recorder log files are stored in the binary
(bin) subdirectory of the Siebel Server root directory.
They appear in the following form:
TYYYYMMDDHHMM_PProcess_ID.fdr
where:
YYYYMMDDHHMM is the timestamp.
Process_ID is the identification number of the process that failed or was stopped.
For example:
T201705181601_P001376.fdr
is a filename that is based on a component that was started on May 18, 2017 at 4:01 PM, where the process ID value was 1376.
The Siebel flight data recorder feature is enabled by default. However, FDR activation requires the execution of at least one instrumentation point to generate a log file. If a failure happens before execution of the first instrumentation point, then no log file is generated. Instrumentation points are embedded in some workflow business services to provide capture-processing details in case of a system failure or server component failure. For more information about instrumentation and instrumentation points, see Siebel Performance Tuning Guide and Siebel Business Process Framework: Workflow Guide, respectively.
Setting the environment variable SIEBEL_CRASH_HANDLER to 0 disables the creation of FDR files, in addition to several other logging functions. Only set this variable to 0 in consultation with Oracle Siebel Global Customer Support by creating a service request (SR) on My Oracle Support.