Mapping Task Logs
You can view Mapping task logs to troubleshoot Mapping task problems or to see information about the mapping run.
The Data Integration service writes a new log file for each Mapping task run. The log file contains information about the events in the Mapping task. Log events are lines of text that contain a timestamp, thread identifier, a severity code, and the log message. The message can contain general information or it can contain an error message.
The following text shows the Mapping task log message format:
2015-02-20 12:49:24 <DTMLoggerThread_2> INFO: READER_1_1_1, DBG_21430, Reading data from input source file [C:\Source\Logging_Source_1.txt]
2015-02-20 12:49:24 <DTMLoggerThread_2> INFO: READER_1_1_1, BLKR_16019, Read [200] rows, read [0] error rows for source table [read_src2] instance name [read_src2]
2015-02-20 12:49:24 <DTMLoggerThread_2> INFO: LKPDP_2, TE_7212, Increasing [Data Cache] size for transformation [Rel_Lookup] from [59652322] to [59654144].
2015-02-20 12:49:24 <DTMLoggerThread_2> INFO: READER_1_1_1, BLKR_16008, Reader run completed.
2015-02-20 12:49:24 <DTMLoggerThread_2> INFO: WRITER_1_*_1, WRT_8167, Start loading table [Router_Target_Default] at: Fri Feb 20 12:49:24 2015
When you set the tracing level to verboseData, the Mapping task log shows the parameters and parameter values for the mapping run.
The following text shows some Mapping task log messages that contain parameter values:
Integration Service will use override value [C:\Source] for parameter [ff_SrcDir] in transformation [map_AllTx\read_src1].
Integration Service will use override value [8] for parameter [exp_Int] in transformation [map_AllTx\Expression].
Integration Service will use override value [Mapping_New] for parameter [exp_String] in transformation [map_AllTx\Expression].
Integration Service will use override value [C:\Source] for parameter [ldo_SrcDir] in mapping \ mapplet [map_AllTx\DO_Lookup\DO_FF_REL_SRC_Read_Mapping].
Mapping Task Log File Name
The default name of each Mapping task log file is based on whether you are archiving the log files by timestamp or you are archiving the log files by run number.
The default name of the Mapping talk log file consists of the Mapping task name, an UID number, a timestamp, and the .log suffix. If you choose to archive the logs by run number, the default log file name consists of the Mapping task name, the run number, and the .log suffix.
In the Mapping task Advanced properties, configure the Mapping Task Log Save Type to indicate whether you want to archive files by timestamp or by run number. If you choose to archive by run number, you can enter the number of runs to keep before the Data Integration Service overwrites a log. If you choose to archive by timestamp, the Data Integration Service keeps an unlimited number of log files.
You can enter a different Mapping task log file name if you do not want to use the default name.
Mapping Task Log File Directory
You can configure the directory where the Data Integration Service writes the Mapping task log. You can parameterize the mapping task log file directory.
By default, the Data Integration Service writes the Mapping task log file in the directory defined by the system parameter, LogDir. An administrator can change the LogDir path in the Administrator tool.
You can configure a different directory for the Mapping task log file in the Mapping task Advanced properties. If you enter a directory name that the Data Integration Service cannot access, the Mapping task fails.
When you run a workflow on a grid, the mapping task log directory is created on the machine where the Data Integration Service master node is running. Configure the mapping task log file directory on a shared directory that all nodes on the grid can access.