Error <50505>: Unknown error in transform <Key_gen

dataservices job design
1

This data flow has been working for years and we never had this error before. What may be the reason? I do not see any duplicate records or anything wrong with the data

I have an error in the data flow
|Dataflow DF_DLY_Load_Vehicle_Dim_T1|Loader Key_Generation_VEHICLE_DIM
Unknown error in transform <Key_Generation_VEHICLE_DIM>.
(11.5) 01-16-14 10:35:08 (4868:5896) RUN-050505: |Dataflow DF_DLY_Load_Vehicle_Dim_T1|Transform Table_Comparison
(11.5) 01-16-14 10:35:17 (E) (4824:3572) SYS-170101: |Session Jb_AutoDataMart_Daily|Workflow WF_DLY_Load_QM3|Workflow WF_DLY_Load_QM3_Dimensions|Workflow WF_DLY_QM3_Load_Dimension_Data|Workflow WF_DLY_QM3_Load_Other_Dim|Workflow WF_DLY_QM3_Load_Vehicle_Dim|Dataflow DF_DLY_Load_Vehicle_Dim_T1
System Exception <> occurred.
Call stack:
(null)
Registers:
EAX=002176D0 EBX=7C1A7A08 ECX=00000000 EDX=0027DAE8 ESI=00217760
EDI=00217760 EBP=00217720 ESP=002176CC EIP=77E4BEF7 FLG=00000206
CS=7C82001B DS=210023 SS=7C820023 ES=210023 FS=7C37003B GS=7C370000
Exception code: E06D7363

oshestak (BOB member since 2014-01-20)

2

Field types on the source and target? Have you checked those?

indy (BOB member since 2004-04-08)

3

Does it matter for the ket generation? Error is in the Key geveration…

oshestak (BOB member since 2014-01-20)

4

I suspect that the problem is in the target table object. Likely with the target table itself. You may have encountered a piece of data that is different from what has been seen in the past.

eganjp :us: (BOB member since 2007-09-12)

5

Error is maybe not in the key generation. The error is in the transform called “key_generation”.

Johannes Vink :netherlands: (BOB member since 2012-03-20)

6

I face exactly the same problem. The job fails with unknown error 50505 on key generation transform. The target table didn’t change, data types didn’t change and the max(Id) is not too large or anything. What I noticed is that it throwed an error after it generated all the id’s first (don’t know what happens after that?)…

rubenjonathan (BOB member since 2017-08-09)

7

Fixed the issue by changing the caching type to ‘pageable’ from ‘in memory’. Can’t put my finger on the root cause exactly, but it worked.

rubenjonathan (BOB member since 2017-08-09)

8

Normally, I would say that going to pageable implies that you ran out of memory. Is it possible that you had some other process running on the O/S that consumed all the other memory or perhaps your Dataflow itself requires a lot of memory?

eganjp :us: (BOB member since 2007-09-12)