Could not find input field

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
harryhome
Participant
Posts: 112
Joined: Wed Oct 18, 2006 7:10 am

Could not find input field

Post by harryhome »

getting error in transformer as

Transformer: Error when checking operator: Could not find input field "INPUT_COLUMN".

while field is present in input.
harryhome
Participant
Posts: 112
Joined: Wed Oct 18, 2006 7:10 am

Post by harryhome »

one more observation if this transformer stage is moved to someother part in same job then still give same error on same column and all previous stages gives warning as


Lookup: When checking operator: On input data set 0: When binding input schema variable "inputData": A transfer adapter is renaming the non-existent field "INPUT_COLUMN".
Lookup: When checking operator: The modify operator keeps field "INPUT_COLUMN_1" which is not present in the output interface.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Looks like you have a field on the input link that is not transferred to the output link. Do you really need this field?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
harryhome
Participant
Posts: 112
Joined: Wed Oct 18, 2006 7:10 am

Post by harryhome »

Yes need that field , what can be the reason for not reading one particular field and any workaround?
jwiles
Premium Member
Premium Member
Posts: 1274
Joined: Sun Nov 14, 2004 8:50 pm
Contact:

Post by jwiles »

The error is telling you that the input column does not exist in the in the incoming virtual record's schema. You're seeing this happening with both the transformer and the lookup (when you move the transformer elsewhere), so it's not an issue with the transformer. There is no "workaround" as the column obviously doesn't exist at point.

Somewhere upstream of that location the column has either been dropped (unexpectedly?), or it never really existed in the first place. Is your input source a dataset or database? Maybe the source doesn't contain the column...

Set the environment variable OSH_PRINT_SCHEMAS to display the schemas of all datasets and stages and scan the resulting output in the job log for your missing column.

Regards,
- james wiles


All generalizations are false, including this one - Mark Twain.
Post Reply