Logging Formats

Most Oracle Enterprise Performance Management System products use the Oracle Diagnostic Logging (ODL) format for logging purposes. EPM System Installer and EPM System Configurator create ODL files for all products. Products not using ODL leave these ODL files empty and write their logs to different file formats, usually log4j.

ODL Log File Naming

Each product, component, service, or servlet has its own log file. Separate log files are generated for license information, configuration, and, if necessary, environment information.

ODL Log Elements

ODL logs use elements that show information about the origins of messages as well as the messages themselves. This information can be helpful in troubleshooting.

ODL log elements:

• Time Stamp–Date and time when the message was generated, adjusted for time difference between the host where the message was generated and the host of the common repository

  Example: <Jul 22, 2011 11:29:57 PM PDT>

• Component ID–Managed server that originated the message

  Example: [FoundationServices0]

• Message ID–A short character string that uniquely identifies the message

  Example: [EPMWKSP-000001]

• Module ID–An identifier for the class name or other code module that originated the message

  Example: [Initialization]

• Execution Context Id (ECID)–Execution context ID, which helps connect multiple log files

  Example: [ecid: 0000IPMCrhW17ic5PjWByd1BMQPg000002,0]

• Message text–Log message

Log4j Log File Naming

Each service or servlet has its own log file. In an environment with several installation locations, all services of one type log their messages to one file. Separate log files are generated for license information, configuration or environment information, and stdout messages. Services and servlets log file names format:

server_messages_OriginatorType.log

where OriginatorType is a specific servlet or service.

Log4j Log Message Elements

Log4j log messages contain this information, in this order:

• Logger—Name of the logger that generated the logging message

• Time stamp—Time stamp in coordinated universal time (UTC); ensures that messages from differing time zones can be correlated

• Level—Logging level

• Thread—Thread name

• Sequence number—Unique number to identify messages with matching time stamps

• Time—When the message was generated

• Context—Information about which component generated the log message:

  • Subject—User name

  • Session ID—UUID of the session

  • Originator Type—Component type name

  • Originator Name—Component name

  • Host—Host name

• Message—Log message

• Throwable—Stack trace of a throwable error