4.23 Debugger

Use to execute a session in Oracle Data Integrator debugger by manually performing the steps and tasks of the session.

You can view the values of variables as well as uncommitted data through Debug Variables and Debug Data views, only if the editor is displaying a debuggable session to which that instance of studio is connected. You can set breakpoints that are listed in the Debug Breakpoint view.

Active debug sessions are displayed in the Debug Session view, while threads within these sessions are listed in the Debug Session Threads view.

Start the Oracle Data Integrator debugger for a mapping, procedure, package, or scenario. These objects have a Debug... command in the context menu or toolbar. When the debug session is started, the Start Debug Session... Dialog is first opened. Then the session editor in its Blueprint view opens, if Associate with this client option is selected. In the Blueprint view, all steps and tasks of the given scenario are displayed and this allows you to go through individual commands. The debug execution can be controlled by the debug commands in the debug toolbar:

Icon Command Description
Surrounding text describes unverifiedbreakpoint.gif. Add Breakpoint Toggles a breakpoint at the currently selected line in the blueprint.
Start debug session icon Start Debug Session... Starts a debugging session for the editor in focus. In a session editor, this command can be used to restart a session.
Connect to debug session icon Connect to Debug Session... Connects to a debugging session running on an agent. This opens the currently running session and allow to step through the execution. It is not possible to connect to a local agent.
Disconnect debug session icon Disconnect Debug Session Disconnects the current debugging session. After the debugging session is disconnected, the execution continues and any breakpoint is ignored.

It is possible to reconnect to a disconnected session.
It is not possible to disconnect from a session running on a local agent.
Current cursor icon Current Cursor Highlights the current cursor in the blueprint, and opens the session editor, if not already open.
Get data icon Get Data Inserts the SQL code of the currently selected task into the SQL command field of the Debug Data window. Both Source Task Data and Target Task Data windows are populated.
Step into icon Step into Steps to the beginning of the first child node of the currently selected node. If the currently selected node does not have a child, this is disabled.
Run to task end icon Run to Task End Runs to the end of the currently selected task. If the task has children, execute all children until the end of the task is reached.

This is disabled if it is not at the beginning of a task.
Run to next task icon Run to Next Task Runs to the beginning of the next task. If at the last task in a list of tasks, go to the end of the parent task.
Run to step end icon Run to Step End Runs to the end of the current step. Executes all tasks until the end of the step is reached.

This is disabled if it is not at the beginning of a step.
Run to Next step icon Run to Next Step Runs to the beginning of the next step.
Pause icon Pause Suspends the current execution. The execution can be continued by stepping through the steps/tasks, or by resuming execution.
Resume icon Resume Resumes execution at the current cursor and continues until the session is finished or a breakpoint is reached.

4.23.1 Debug Variables

Use to view all the variables used in the current session.

Variable values can be modified to change the execution of the session.

Properties Description
Name Name of the variable.
Value Value of the variable. Can be modified to change execution.
Type Type of the variable.

4.23.2 Debug Breakpoint

Use to view the list of all breakpoints.

The breakpoint execution can be controlled by the breakpoint commands in the main menu:

Icon Command Description
Refresh icon Refresh Updates the window with the latest breakpoint information.
Edit icon Edit Breakpoint Edits a breakpoint.
Enable icon Enable Enables multiple breakpoints.
Disable icon Disable Disables multiple breakpoints.

This list can be used to edit or remove breakpoints throughout the repository. Two lists of breakpoints are shown:

  • Runtime Breakpoints: Defined in a blueprint. Runtime breakpoints can be added in the blueprint tab of a session editor.

    Properties Description
    Breakpoint ID of the breakpoint.
    Scenario Name of scenario on which breakpoint is based on, empty if not started from scenario.
    Blueprint ID of the blueprint.
    Step Name of Step on which the breakpoint is located. This is empty if the breakpoint is located on Task.
    Task Name of Task on which the breakpoint is located. This is empty if the breakpoint is located on Step.
    Suspend after executing the task
    • No: The breakpoint suspends before executing the task or step.

    • Yes: The breakpoint suspends after executing the task or step.

    This property can be changed through the Edit Breakpoint context menu command.
    Pass count Number of times the breakpoint has to be passed before suspending execution; 0 suspends the execution on the initial pass, 1 passes the breakpoint once before suspending execution.
    Status
    • Enabled: The breakpoint is active and suspends execution.

    • Disabled: The breakpoint is ignored during execution.

  • Design Breakpoints: Defined in a design artifact such as package or procedure. When executing, a design breakpoint generates a runtime breakpoint in the blueprint it is associated with. Design breakpoints can be added in Package Editor or Procedure Editor.

Properties Description
Breakpoint ID of breakpoint.
Package Package where the breakpoint is defined.
Procedure Procedure where this breakpoint is defined.
Step Step on which the breakpoint is located. This is empty if the breakpoint is located on Task.
Task Task on which the breakpoint is located. This is empty if the breakpoint is located on Step.
Suspend after executing the task
  • No: The breakpoint suspends before executing the task or step.

  • Yes: The breakpoint suspends after executing the task or step.

This property can be changed through the Edit Breakpoint context menu command.
Pass count The execution is suspended on the configured value; 1 suspends only on the first pass, 2 suspends only on the second pass, 0 suspends the execution on all passes.
Status
  • Enabled: The breakpoint is active and suspends execution.

  • Disabled: The breakpoint is ignored during execution.

4.23.2.1 Breakpoint Properties

Start Breakpoint properties through Breakpoint view or Edit Breakpoint in the blueprint tab. Edit breakpoint properties on the breakpoint icon on the step/task in the Blueprint view.

Properties Description
Enabled If checked the breakpoint is active and execution will be suspended on reaching it.

If unchecked the breakpoint will not be active and will be ignored.
Suspend after executing the task If checked the breakpoint suspends after executing the task or step.

If unchecked the breakpoint suspends before executing the task or step.
Pass Count The execution is suspended on the configured value; 1 suspends only on the first pass, 2 suspends only on the second pass, 0 suspends the execution on all passes.

4.23.3 Debug Session

Use to see the list of all active debug sessions.

It allows you to connect or disconnect the listed sessions.

Session List

Properties Description
Agent Agent executing the session.
Session Number ID of the session.
Session Name Name of the session.
Session Connected Shows whether the session is connected or not connected to the debugger client.

4.23.4 Debug Session Threads

Use to see all threads for the connected session editor in focus.

The icon of the thread shows whether the thread is suspended or executing. The Go To Source context menu command on each thread jumps to the thread location inside the blueprint.

4.23.5 Debug Data

Allows querying of data in the context of the current debugger task.

The data window has two tabs, Source Task Data and Target Task Data, to query the data servers associated with source and target for the current task. The window provides a field to enter a SQL command and execute it by clicking the Run SQL Code button. The Get Data command in the main toolbar inserts the SQL code of the current task into both Source Task Data and Target Task Data fields.

All SQL commands use the transaction context of the current session, uncommitted data can be queried.

Related Topics

"About Sessions and Blueprints" in the chapter "Debugging Integration Processes" in Oracle Fusion Middleware Administering Oracle Data Integrator

"Stepping through a Blueprint in the Session Editor" in the chapter "Debugging Integration Processes" in Oracle Fusion Middleware Administering Oracle Data Integrator