6.13 Diagnosing Issues

To help diagnose issues, you can use the Oracle Enterprise Manager logging functionality:

6.13.1 Specifying Logging Information

To specify information to be saved in log files for Reports Server or Reports Application (in-process Reports Server):

  1. Log in to Oracle Enterprise Manager.

  2. Navigate to the EM MBean browser Weblogic Domain > System MBean Browser.

  3. Navigate to logging configuration mbean

    Standalone server - oracle.logging:type=LogConfig,componentType=oracle_repserv,name=<componentName>

    Inprocess server - oracle.logging:type=LogConfig,ServerName=<managedServerName>

    Reports Tools - oracle.logging:type=LogConfig,componentType=oracle_reptools,name=<componentName>

    Reports Bridge - oracle.logging:type=LogConfig,componentType=oracle_repbrd,name=<componentName>.

  4. In Operations tab click updateHandlerProperty enter handler name and change properties like path, maxLogSize, maxFileSize as desired

    zrclient_trace_handler - network trace handler

    rwengine_trace_handler - engine trace handler

    rwserver_trace_handler - server trace handler

    rwservlet_trace_handler - servlet trace handler

    runtime_trace_handler - runtime trace handler

  5. In Oracle Enterprise Manager, the rotation policy for log files can be set by specifying the Max Log size and Max number of files properties. For example, if Max Log size is set to 10MB and Max number of files is set to 10, log file rotation automatically takes place when the first log file (diagnostics.log) reaches 1 MB (Max Log size / Max number of files = 10MB/10). ODL then renames this file to diagnostic1.log and starts logging to a new diagnostics.log. When it reaches a size of 1 MB, it is renamed to diagnostics2.log and logging continues in diagnostics.log. When the number of files reaches 10, the earliest log file is purged (diagnostics1.log) and a new diagnostics11.log is created. In this example, the maximum size of all log files is limited to 10 MB and the maximum number of files to 10, removing the risk of creating huge log files of arbitrary size and the machine running out of space, bringing the production system down.

  6. Restart the component for the changes to take effect.

6.13.2 Diagnosing Font Issues

Refer to Section 6.4.2, "Diagnosing Font Issues".