Oracle Fusion Middleware 12c – selective tracing

Oracle Fusion Middleware 12c – selective tracing

Published on: Category: Oracle

For doing a good diagnosis in case of a problem in your Oracle Fusion Middleware Product, the platform offers you many methods and techniques to do your investigation. The disadvantage from some of these methods is that they have some impact on your system, such as if you would raise the log or debuglevel or use diagnostic snapshots.

Selective Tracing is a facility available through Enterprise Manager to limit the scope of trace logging.This allows for debugging of a production system without overloading the system with logging activity. To use Selective Tracing, perform the following method:

  • On the left expand ‘WebLogic Domain’
  • Open Enterprise Manager: http://<your host>:7001/em
  • Right click your domain name -> Logs -> Selective Tracing. This will bring you to the following screen where you can configure your Selective Tracing session. Click on add fields and select as below:

Select the ‘Option Name’ to choose the scope of your trace session. In this example we choose ‘Composite Name’ and enter the value in the text field.

  • Set your trace level as desired, enter an optional description and specify a duration for the trace session. The default value is 30 minutes. We leave trace to FINEST
  • You have two options for the Trace ID, a system generated alphanumeric value or a custom value that you choose. In this example we’re using a custom string, trn[nn]trace

You may select the loggers that you want to be active for your tracing session by expanding the ‘Loggers’ below the form.

All loggers are enabled by default and there is the option to both sort by the available columns as well as search.  Here we display only the loggers that contain the string ‘oracle.bpel’

Your Selective Tracing session is now configured and ready to be activated by clicking the ‘Start Tracing’ button.  If all is well you will see the following confirmation message at the top of the screen:

Run the composite for which the tracing session is enabled.

When the run is complete, success or failure, we have a couple of options to view the trace output. Since all of the trace entries are logged in the server diagnostic log, <server home>/logs/<server>_diagnostic.log, we can filter by the trace ID using your preferred editor, or by clicking on you trace event.

Each trace log entry is quite long.  Below are some snippets of what to expect.

Your trace session will expire at the end of the specified duration or you may manually disable it in the ‘Active Traces and Tracing History’ tab by highlighting the session and clicking the ‘Disable’ button.  If you should restart your managed server instance during the tracing session the session will be ended and must be recreated when the managed server instance is back up.

Michel Schildmeijer
About the author Michel Schildmeijer

Having made his start in the pharmacy sector, Michel transitioned to IT in 1996, working on a UNIX TTY terminal-based system and the MUMPS language. He currently works as a solutions architect at Qualogy, with a focus on middleware, application integration and service-oriented architecture. His passion for middleware started in 2000 when working as a support analyst for a financial institute with BEA WebLogic and Tuxedo. Michel is an expert on the WebLogic platform. He serves customers in his role as architect and advises them in all aspects of their IT landscape. He became an Oracle ACE in 2012 and wrote two books about WebLogic: Oracle WebLogic Server 11gR1 PS2: Administration Essentials and Oracle WebLogic Server 12c: First Look. He is a well-known speaker at national and international conferences and is recognised as an official Oracle Speaker. Read his blog:

More posts by Michel Schildmeijer
Comments (2)
  1. om 11:11

    Can you please explain for BAM projects

  2. om 12:12

    Very Good Michel ! Thx.. :)