Recently I hit some transformation errors.
By default these errors are swallowed by the Integration Engine. It does not
try to write the row to target.It does not add row level details to the session log.
Looking at the session log only reveals a
hint of what the error may be:
2013-09-03
09:10:38 : INFO : (11652 | TRANSF_1_1_1) : (IS | DOMAIN) :
node01_SERVER : CMN_1053 : : Rowdata: ( RowType=-4(error) Src Rowid=854 Targ Rowid=854
lkp_Key_(lkp_EDW_ID_Passthrough:Int:): "(NULL)"
lkp_Start_DT
(lkp_Start_DT:Date:): "11/27/2012 00:00:00.000000000"
)
There was no clear definition in Communities
for this error. The sess log was not clear where it occured.
I had my QA person do the following to the session throwing the transformation error
Check out and open the session
Click Config Object
Scroll to Error Handling
Change Error Log Type - Flat File
Change Error Log File Directory to
$PMLookupFileDir
Save and run the session
Undo the checkout...as this change
makes the session run at a row by row level that can impact performance.
The following was produced.
Transformation||Transformation Mapplet
Name||Transformation Group||Partition Index||Transformation Row ID||Error
Sequence||Error Timestamp||Error UTC Time||Error Code||Error Message||Error
Type||Transformation Data||Source Mapplet Name||Source Name||Source Row
ID||Source Row Type||Source Data
FIL_Expire||N/A||Output||1||38||1||09/03/2013 16:34:19||137829999||11999||There
is an error in the port [lkp_Key]:
The default value for the port is set to: ERROR(Transformation error:
FIL_Expire).||3||D:004sfsdfsdfs655E914DD833FF5CBAA88A|D:11/27/2012
00:00:00.000000000|D:1|D:0||N/A||SQ_Shortcut_to_SourceOfDimensionTbl123||38||0||D:0040484394655E914DasdasdasdA88A|D:12/13/2012
00:00:00.000000000|D:6384 XMJWRFS XY|N:|D:Dim1|D:Dim2|D:Dim3|D:Dim4
This was 100% more useful than the sess
log, as I use that lkp port in several objects, it was now clear which one and which port was impacted.
No comments:
Post a Comment