Logs
A log contains a record of the Data Processor transformation. The Data Processor transformation writes events to logs.
The Data Processor transformation creates the following types of logs:
- Design-time event log
- The design-time event log contains events that occur when you run the Data Processor transformation in the Data Viewer view. View the design-time log in the Events view.
- Run-time event log
- The run-time event log contains events that occur when you run the Data Processor transformation in a mapping. You can view the run-time event log in a text editor or you can drag a run-time event log into the Events view of the Data Processor transformation.
- User log
- The user log contains events that you configure for components in a Script. The Data Processor transformation writes to the user log when you run it from the Data Viewer view and when you run it in a mapping. You can view the user log in a text editor.
Design-Time Event Log
The design-time event log contains the events that occur when you run the Data Processor transformation from the Data Viewer in the Developer tool.
When you run a Data Processor transformation from the Data Viewer view, the design-time event log appears in the Data Processor Events view. By default, the design-time event log contains notifications, warnings, and failures. In the transformation settings, you can configure the Data Processor transformation to exclude one or more event types from the log.
When you save the input documents with the log, you can click an event in the Data Processor Events view to find the location in the input document that generated the event. When you configure the Data Processor transformation settings, you can choose to save the input files for every run or only on failure.
The design-time event log is named events.cme. You can find the design-time event log for the last run of the Data Processor transformation in the following directory:
C:\<Installation_directory>\clients\DT\CMReports\Init\events.cme
The Data Processor transformation overwrites the design-time event log every time you run the transformation in the Data Viewer. Rename the design-time event log if you want to view it after a later run of the transformation,or if you want to compare the logs of different runs. When you close the Developer tool, the Developer does not save any files in the
Run-Time Event Log
The run-time event log records the events that occur when you run the Data Processor transformation in a mapping.
If the Data Processor transformation completes the run with no failures, it does not write an event log. If there are failures in the run, Data Processor transformation runs a second time and writes an event log during the second run. The run-time event log is named events.cme.
On a Windows machine, the run-time event log in in the following directory:
C:<Installation_Directory>\clients\DT\CMReports\Tmp\
On a Linux or UNIX machine, the run-time event log for a root user in the following directory:
/root/<Installation_Dirctory>/clients/DT/CMReports/Tmp
On a Linux or UNIX machine, you can find the run-time event log for a non-root user in the following directory:
/home/[UserName]/<Installation_Directory>/DT/CMReports/Tmp
Use the configuration editor to change the location of the run-time event log.
Viewing an Event Log in the Data Processor Events View
Use the Data Processor Events view to view a design-time event log or a run-time event log.
Open Windows Explorer, and then browse to the event log file you want to view. Drag the log from the Windows Explorer window to the Data Processor Events view. Right-click in the Data Processor Events view, and then select Find to search the log.
Note: To reload the most recent design-time event log, right-click the Data Processor Events view, and then select Reload Project Events.
User Log
The user log contains custom messages that you configure about failures of components in a Script.
The Data Processor transformation writes messages to the user log when you run a Script from the Data Viewer view and when you run it in a mapping.
When a Script component has the on_fail property, you can configure it to write a message to the user log when it fails. In the Script, set the on_fail property to one of the following values:
- •LogInfo
- •LogWarning
- •LogError
Each run of the Script produces a new user log. The user log file name contains the transformation name with a unique GUID:
<Transformation_Name>_<GUID>.log
For example, CalculateValue_Aa93a9d14-a01f-442a-b9cb-c9ba5541b538.log
On a Windows machine, you can find the user log in the following directory:
c:\Users\[UserName]\AppData\Roaming\Informatica\DataTransformation\UserLogs
On a Linux or UNIX machine, you can find the user log for the root user in the following directory:
/<Installation_Directory>/DataTransformation/UserLogs
On a Linux or UNIX machine, you can find the user log for a non-root user in the following directory:
home/<Installation_Dirctory>/DataTransformation/UserLogs