Monitoring the Debugger - Informatica

When you run the Debugger, you can monitor the following information:

  • Session status. Monitor the status of the session.
  • Data movement. Monitor data as it moves through transformations.
  • Breakpoints. Monitor data that meets breakpoint conditions.
  • Target data. Monitor target data on a row-by-row basis.

The Mapping Designer displays windows and debug indicators that help you monitor the session:

  • Debug indicators. Debug indicators on transformations help you follow breakpoints and data flow.
  • Instance window. When the Debugger pauses, you can view transformation data and row information in the Instance window.
  • Target window. View target data for each target in the mapping.
  • Output window. The Integration Service writes messages to the following tabs in the Output window:
  • Debugger tab. The debug log displays in the Debugger tab.
  • Session Log tab. The session log displays in the Session Log tab.
  • Notifications tab. Displays messages from the Repository Service.

While you monitor the Debugger, you might want to change the transformation output data to see the effect on subsequent transformations or targets in the data flow. You might also want to edit or add more breakpoint information to monitor the session more closely.

Monitoring Debug Indicators

During a session, the mapping displays the indicators in the top left corner of transformations that help you monitor breakpoints, data flow, and Debugger status:

  • Breakpoint indicator. After the Integration Service completes initialization, it reads the breakpoints in the mapping and displays a stop sign on each transformation to indicate breakpoint conditions. You can view breakpoint indicators while the Debugger is in the running or paused state. The Mapping Designer does not display global breakpoint indicators.
  • Current source qualifier indicator. When the Integration Service runs the Debugger, it processes data from each source qualifier in a target load order group concurrently by default. The Mapping Designer displays a flashing arrow on all current source qualifiers.
  • Note:You can configure the Integration Service to read sources connected to Joiner transformations sequentially.

  • Current transformation indicator. The Debugger displays a solid yellow arrow that indicates the transformation or mapplet that the Integration Service was processing when it encountered a break. This transformation is called the current transformation. The Debugger displays a solid blue arrow at all other transformations that the Integration Service was processing when it encountered a break at the current transformation.
  • Debugger status. When you start the Debugger, the Mapping Designer displays a Debugger icon by the tool bars that indicates the Debugger state. When the Debugger is initializing or running, the icon rotates. When the Debugger is paused, the icon stops.

Monitoring Transformation Data

When the Debugger pauses, it displays the current row of data in the Instance window for the transformation in the mapping or mapplet where the Integration Service encountered the break. This is the current transformation. You can view the data of any transformation at the point where the Debugger pauses by selecting another transformation from the list in the Instance window.

If you did not select any mapplet to debug after completing the Debugger Wizard, you cannot monitor or view transformations inside the mapplet when the Debugger runs. Click Tools > Options > Debug tab to select columns to display in the Debugger Data Display window.

Note:When the mapping contains a Custom transformation, the Instance window displays information for ports in all input and output groups.

You can display the following information in the Instance window:

  • Port name. Displays all ports that are connected to another transformation or target.
  • RowID. Displays row number passing through the transformation.
  • Value. Displays the value for each port. If the port contains binary data, this column displays <raw data>. If the port does not contain data, or if it is NULL, this column displays <no data available>. For Router transformations, the values display for input ports and output ports that meet the group condition. Output ports that do not meet the group condition display <no data available> in the value column.
  • Datatype. Displays the datatype of the port.
  • Length/precision and scale. Displays the length/precision and scale of the port.
  • Null indicator. If a column contains a null value, the null indicator column is selected, and the value displays <no data available>.
  • Row type. Insert, update, delete, reject, filtered, or not applicable. <<ROW TYPE>> displays in the Port column, and the row type value displays in the Value column. The row type does not display if it is not applicable, such as with Sequence Generator transformations.
  • Port indicator. Displays one of the following indicators next to the port name:
  • Current row. Indicates the port is in the current row.
  • Previous row. Indicates the port is in the previous row.
  • Current row, default value. Indicates the value for the column in the current row is the default value.
  • Previous row, default value. Indicates the value for the column in the previous row is the default value.
  • Current row, modifiable. Indicates an output port in the current row that you can modify.

Tip:Move the pointer across the port indicator to display tooltips about the indicator.
When the Instance window displays the current transformation or any transformation in the pipeline before the current transformation, the current rows display. If you view a transformation in the Instance window that appears in the pipeline after the current instance, the previous rows display. An indicator also displays beside the port name to designate the current or previous row.

For example, in the following mapping, FILTRANS is the current transformation, as shown by the current transformation indicator. When you view the Instance window for FILTRANS or SQ_ORDERS, you see the current row. If you switch to EXPTRANS, you see the previous row because the Integration Service has not processed the current row through EXPTRANS.

The following figure shows transformations with port processing indicators:

Monitoring Transformation Data

Current and previous row indicators can also show when the Instance window displays the default value. The Debugger uses the same rules to display the default value indicator in the Instance window that it uses to evaluate default values for breakpoints.

Note:The Debugger does not immediately drop rows flagged to drop. This includes invalid, error, and filtered rows. The Integration Service sets the ROW_FLAG to NULL and designates the row type by a negative number, such as -3 (error). You see the error indicators in the session logs with verbose data tracing only. The Integration Service drops the rows later in the pipeline.

Continuing the Debugger

After you review or modify data, you can continue the Debugger in the following ways:

  • Continue to the next break. To continue to the next break, click Continue on the toolbar or from the Mapping > Debugger menu option. The Debugger continues running until it encounters the next break.
  • Continue to the next instance. To continue to the next instance, click Next Instance on the toolbar or from the Mapping > Debugger menu option. The Debugger continues running until it reaches the next transformation or until it encounters a break. If the current instance has output going to more than one transformation instance, the Debugger stops at the first instance it processes. If you did not select a mapplet to debug when you completed the Debugger Wizard steps, the Debugger continues to the instance after the mapplet.
  • Step to a specified instance. To continue to a specified instance, select the transformation instance in the mapping, then click Step to Instance on the toolbar or from the Mapping > Debugger menu option. The Debugger continues running until it reaches the selected transformation in the mapping or until it encounters a break.

You can step to connected transformations in the mapping, even if they do not have an associated breakpoint. You cannot step to the following instances:

- Sources
- Targets
- Unconnected transformations
- Mapplets not selected for debugging

Monitoring Target Data

When the Debugger runs, the Designer caches the target data. You can view the cached data in the Target window while the Debugger is running or paused. You can view cached target data even if you configure the Debugger Wizard to discard target data.

You can view the following information for each row of target data:

  • Row ID. Row number of the cached target data.
  • Row type. Insert, update, delete, reject, or filtered.
  • Column name and value. Column name and value for each row in the cache.

If the mapping has more than one target, you can choose the target you want to display. Select a target to view from the list in the Debugger Target Display window. The targets that display in the list are the targets you selected in the Debugger Wizard. If you want to view a target that you did not select in the wizard, click Mappings > Debugger > View Target Data.

The Target window displays up to 1,000 rows. After it reaches 1,000 rows, the Designer begins overwriting data from the first row. You can clear the cache and the Debugger Target Display window by right-clicking in the Debugger Target Display window, and selecting Clear Data.

Monitoring the Debug Log

When the Debugger initializes, the Integration Service begins writing the debug log in the Debugger tab of the Output window. The Integration Service writes the following types of messages to the debug log:

  • Session initialization
  • Acknowledge user request
  • The Integration Service encounters a break
  • Debug errors
  • Debugger status
  • Session stops

When the bottom line in the Output window reads that the Integration Service is ready, you know the Debugger is paused. The Integration Service remains paused until you issue a command, such as Continue, Step to Next, or Stop.

Note:If the Debugger does not start or if it abruptly stops, and the Integration Service does not write any message to the Output window, you can look in the Administration Console Domain page for more information.

The following table shows samples of debug log messages in the Output window:

Monitoring the Debug LogMonitoring the Debug Log

To save the log when the session completes, right-click inside the Debugger tab, and choose Save Output As from the menu.

Using the Workflow Monitor

You can view running and completed workflows and sessions in the Workflow Monitor. The Integration Service uses a debug workflow to run the debug session. The Workflow Monitor displays the debug workflow and session names differently depending on the session type you chose in the Debugger Wizard.

The following table describes the workflow and session names the Workflow Monitor displays for each debug session type:

Monitoring the Debug Log

The Workflow Monitor displays the debug run mode in the Run Type column for all debugger sessions and workflows. You can also access the logs through the Workflow Monitor.

Note:You cannot use the Workflow Monitor to restart, abort, or stop a debug session, debug workflow, or a session run in debug mode.


All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

Informatica Topics