To configure an error handling policy at the transformation level, do the following steps:
From the Transformation View, select the transformation for which you want to define a Runtime error handling policy.
In the Properties pane on the right, under Data Transform Error Handling Policy, select one of the following options from the list:
Stop: To stop the transformation when any data conversion, filter, or DML command substitution error occurs. This is the default option.
Note: When the transformation stops, the event is logged in the log file DataTransformError.log in the Runtime Service installation folder and in the Windows event log.
TruncateOrReject: To truncate or reject the source data depending on the data type and size of the target column. If the Data Exchange Runtime cannot successfully truncate the source data, then the data is rejected.
Note: In this case the transformation continues and the error is logged in the log file DataTransformError.log in the Runtime Service installation folder.
Example 1
Assume that you have defined a mapping from a numeric (10,3) source data type to a numeric (4) target data type, and the source value is “50000.123”. If the target data type cannot hold any decimal values, then the Data Exchange Runtime truncates the decimal value and tries to save the integer value (50000) in the numeric (4) target data type.
Assume that the maximum value that the numeric (4) target data type can hold is 9999. In this case, the Data Exchange Runtime rejects the source value (50000.123) from being transformed.
However, if the target data type was numeric (5), then the Data Exchange Runtime would have successfully stored the integer part (50000) after truncation of the decimal values.
Example 2
Assume that you have defined a mapping from an alpha (10) source data type to a char (3) target data type, and the source value is “ABCDEFG”, then the Data Exchange Runtime truncates the string value and tries to save the string value (“ABC”) in the char (3) target data type. In case of a mapping from a string data type to a target string data type, the "Reject" scenario will not happen.
Example 3
Assume that you have defined a mapping from an alpha (10) source data type to a numeric (4) target data type, and source value is “50000.ABC”, then the Data Exchange Runtime tries to convert the source value “50000.ABC” to a numeric value first. But, in this case, “50000.ABC” is not a valid numeric string. Therefore the data will be rejected.
Note: The number of records rejected and the number of records truncated appear in the Changed Data Transformation Details subtab on the Summary tab in the Data Exchange Runtime Administration Site
Click OK.