Error in component tOracleSCD - Unknown value in the list

[Anonymous]

Hello everybody,
when trying to update a table i keep getting this error on the tOracleSCD component.
I already set the length of each field on the table schema to a specified value (20 for Integers, 50 for Strings) just to be sure there are no zero-length fields that can cause the problem.
I'll be grateful for any kind of help or hint,
thank you very much.
Jacopo

[Anonymous]

Hi Jacopo
Do you get a warning as Image 1?
If so, please click "Code" tag and show us the error line.
A screenshot is preferred.
Then continue running the job. Do you get some new errors?
Or send me an email and attach the archive file of this export job. I will test it for you.
Regards,
Pedro

[Anonymous]

Hello pedro,
the error message I get is the same that you showed me.

When I switch to the code tab I cannot see where the error is located, there are no red dots signaling an error.

This is the view showing the output of a tMap component synchronized to the schema of the tOracleSCD component, every field has a length.

And finally this is the SCD editor. It's a fairly easy update, I have a single key (numero) and i have to check all other fields for a type 1 SCD update.

[Anonymous]

>> Then continue running the job. Do you get some new errors?
I don't get any new error, the job finishes but the trace going to the SCD component shows 0 records updated.

[Anonymous]

This is the end of the Job Run.

[Anonymous]

Hi
Which version of TOS do you use?
I reproduce the same issue in TOS 5.0.0, TOS5.0.2, TOS5.1.0.
But in TOS4.2.0 it works fine.
Please report it on BugTracker.
Regards,
Pedro

[Anonymous]

So it's a bug, I'm actually using TOS 5.0.2.
I have TOS 4.1 installed, should I try to export the job and import it there?
Thaks

[Anonymous]

Hi
Now it seems that you have to recreate this job in TOS4.1.
Because TOS doesn't support migrating job from new version to old version.
Regards,
Pedro

[Anonymous]

I created the entry on bugtracker, details here: http://jira.talendforge.org/browse/TDI-20675
The fact that I cannot import the job in a previous version of Talend is a really bad news for me, cause the job is a bit complex and I'll have to recreate lots of Metadata.
At least we isolated the problem.
Thank you for your help and support
Jacopo

[Anonymous]

Hi Jacopo
Thanks for your feedback.
The same bug also exists in tPostgresqlSCD.
Regards,
Pedro