BI Publisher writes diagnostic log files in the Oracle Diagnostic Logging (ODL) format.
Log file naming and the format of the contents of log files conform to an Oracle standard. You can view log files by using the WLST displayLogs command, or you can download log files to your local client and view them using another tool (for example a text editor, or another file viewing utility).
Log files are created and edited using Oracle Fusion Middleware Control. By default, after installation, the bipublisher-handler log is created. You can configure this log file or create a new logger.
Each log file message category is set to a specific default value between 1-32, and only messages with a level less or equal to the log level are logged.
Various log file message categories exist, as described in the table below.
| Level | Description |
|---|---|
|
IncidentError:1 |
A serious problem caused by unknown reasons. You can only fix the problem by contacting Oracle support. Examples are errors from which you cannot recover or serious problems. |
|
Error:1 |
A problem requiring attention from the system administrator has occurred, and is not caused by a bug in the product. No performance impact. |
|
Warning:1 |
A potential problem that should be reviewed by the administrator. Examples are invalid parameter values or a specified file does not exist. |
|
Notification:1 |
A major lifecycle event such as the activation or deactivation of a primary sub-component or feature. This is the default level for NOTIFICATION. |
|
NOTIFICATION:16 |
A finer level of granularity for reporting normal events. |
|
TRACE:1 |
Trace or debug information for events that are meaningful to administrators, such as public API entry or exit points. |
|
TRACE:16 |
Detailed trace or debug information that can help Oracle Support diagnose problems with a particular subsystem. |
|
TRACE:32 |
Very detailed trace or debug information that can help Oracle Support diagnose problems with a particular subsystem. |
A log file must contain a consistent format.
However, since there can be multiple formats, you can change the format used in a log file. When you change the format used in a log file, and the new format differs from the current log file's format, a new log file is created. For example, a log file that contains ODL-XML, always contains XML, and is never mixed with text.
Configure the log file format in the Edit Log File dialog. See Configuring Log Files. The format can by Text or XML.