Peek space oddity

Link abrufen
Facebook
X
Pinterest
E-Mail
Andere Apps

Mai 22, 2019

While debugging the other problems, I noticed the peek to output spaces for a char column even though the very same value written to the database was NULL. Surprising twist...

Link abrufen
Facebook
X
Pinterest
E-Mail
Andere Apps

Kommentare

Kommentar veröffentlichen

Beliebte Posts aus diesem Blog

main_program: Fatal Error: enablePrinting() was called without a successful validate().

Mai 01, 2019

Well, what ever the actual reason for this mysterious error message, I could reproduce it when I tried to use a Modify stage therewith changing a not-nullable column to nullable.

Error when checking operator: Could not find input field 'field_name'

Mai 21, 2019

Well, you checked and double-checked the existence of respective field and it is there! Yeah, stumbled over it again. And again! Possible solutions You need to compile jobs explicitly. You're done then. Try it. Go! What are you waiting for? If you are really extra sure compiled the job, then double-check the presence of the respective field again, but not in the stage DS tells you but in the very source at the start of the dataflow where this field comes from. It happens that if the column name of your SQL is not identical to the field name propagated. I do absolutely not know why: compilation does not reveal the problem DataStage misses the correct problem location by far

Missing record delimiter "\n", saw EOF instead

September 16, 2020

Actually, this warning is quite simple to fix. Apparently, DS expects the last record of a file to terminate with the record delimiter in any case - maybe there is a setting to alter this behaviour but I did not deem worthwhile the effort to look for it. So the solution is just to terminate the file on a single empty line. Obviously, this case is for Unix like line breaks. The others delimiters are handled analogously.