Setting Traces
After validating your job, you can proceed to testing.
You can trace the execution to analyze and understand the resulting data.
When a job runs, the system generates a trace log that provides detailed information for each step.
The level of detail displayed depends on the options configured in the job or execution properties.
Common Trace Options
| Trace | Description |
|---|---|
| Row | Logs a message when a transform imports or exports a row. |
| Work flow | Logs messages for workflow lifecycle events, including repository reading, optimization, execution, and completion. |
| Data flow | Logs messages when a data flow starts, completes successfully, or terminates due to an error. |
| Transform | Logs messages when a transform starts, completes, or terminates. |
| SQL readers | Logs the SQL query blocks submitted by scripts, query transforms, or SQL functions, along with the results. |
| Tables | Logs a message when a table is created or dropped. |
| Scripts and script functions | Logs messages when a script or function is called and when a script completes successfully. |
| Trace parallel execution | Logs details about how data is processed in parallel within a data flow. |
| Stored procedure | Logs messages when a stored procedure starts and finishes, including key values. |
| Audit data | Logs audit point statistics and indicates whether audit rules pass or fail. |
Setting Traces in Job Execution Properties
- Defines the specific information recorded in the log.
- Can be configured temporarily via Execution Properties or persistently via Job Properties.
- Supports generating single traces or detailed traces for every row (such as Trace Row or SQL).
After starting the job, use the Trace, Monitor, and Error icons to view the log files generated during execution.
Watch the following video to learn how to set up traces.
Examining Trace Logs
Use trace logs to identify execution failures, verify the sequence of steps, and pinpoint time-consuming processes, as shown in the figure below.
Examining Monitor and Error Logs
Monitor logs quantify job component activities, listing the time spent per component and the number of rows processed, as shown in the following figure.
Error logs help diagnose execution failures. If the job completes successfully, the error log remains empty.
Log Files
Logs are visible during job execution in SAP Data Services Designer and can also be accessed later.
During execution, SAP Data Services produces two or three log files (depending on errors). These typically display automatically in the workspace, but you can also access them via the Monitor and Log tabs in the project area.
Using the Monitor Tab
The Monitor tab displays trace logs for current or recent job executions.
The traffic-light icons indicate the following statuses:
- A green light indicates the job is running.
To stop a running job, right-click it and select Kill Job. The icon will then change to a yellow triangle with an exclamation point.
- A red light indicates the job has stopped.
Right-click and select Properties to add a description to the trace log, which is then accessible from the Log tab.
- A red cross indicates an execution error.
Using the Log Tab
Use the Log tab to review the execution history of a job.
To locate a specific log file:
- Select the desired job.
- In the workspace, use the + dropdown list to select the log type.
- Double-click a log in the list to view its details.
- To copy content from an open log, select the relevant lines and press [CTRL+C].
Summary
In this lesson, you have learned how to enable traces for your job execution.
- Set traces in execution or job properties to log detailed information about job executions.
- Use trace, monitor, and error logs to analyze performance and diagnose failures.
- Access logs during and after execution using the Monitor and Log tabs.