Managing tracing specification

Edit online

Setting trace for Oracle components “oracle.*” results in the underlying Oracle JDBC jar file being changed to a debugging jar file. This might have adverse effects on performance and as such Oracle tracing should only be enabled for debugging purposes and disabled once complete.

About this task

Procedure

  1. Select the Runtime Tracing link from the top of this page. You can also access this panel from the top menu by selecting Monitor > Logs > Runtime Tracing.
  2. Use one of the following ways to edit the trace level of a component.
    • Select the component name from the Component list. Select the ideal trace level for this component from the Trace Level list. Then, click Add. Repeat this process to modify trace levels for other components if needed. To clear all of the tracing levels, click Clear.
      To log all events, select ALL as the trace level.
      Note: This setting increases the amount of data in logs, so use this level when necessary.
      com.tivoli.am.fim.authsvc.*
com.tivoli.am.fim.trustserver.sts.modules.*
      Table 1. Valid trace levelsThe following table contains the valid trace levels.
      Level Significance
      ALL All events are logged. If you create custom levels, ALL includes those levels and can provide a more detailed trace than FINEST.
      FINEST Detailed trace information that includes all of the details that are necessary to debug problems.
      FINER Detailed trace information.
      FINE General trace information that includes methods entry, exit, and return values.
      DETAIL General information that details sub task progress.
      CONFIG Configuration change or status.
      INFO General information that outlines the overall task progress.
      AUDIT Significant event that affects the server state or resources.
      WARNING Potential error or impending error. This level can also indicate a progressive failure. For example: the potential leaking of resources
      SEVERE The task cannot continue, but component, application, and server can still function. This level can also indicate an impending unrecoverable error.
      FATAL The task cannot continue, and component, application, and server cannot function.
      OFF Logging is turned off.
    • Enter the name and value of the trace component in the Trace Specification field. To modify multiple components, separate two strings with a colon (:). Here is an example.
      com.x.y.*=WARNING:com.a.b.*=WARNING:com.ibm.isva.*=INFO
  3. Click Save.