Field is not in the input data set.

prem84 · Post by **prem84** » Tue Jul 20, 2010 1:19 am

hi i have complex job which has many lookups and transformer stages.
i am getting the following error

main_program: Field CURRENCY is not in the input data set.
main_program: Fatal Error: Field not found: CURRENCY.

I am getting the currency details from a shared containers
and currency field from the shared container is a hardcoded value

since job design is complex i am not able to post it fully in the forum
and datastage is not showing which stage the error has orginated.

kindly help

ray.wurlod · Post by **ray.wurlod** » Tue Jul 20, 2010 1:47 am

Welcome aboard.
Can you please post the full detailed text of the error message, and the stage type that threw the error?
If necessary (if the operator is APT_CombinedOperatorController) disable operator combination before re-running, THEN get the error message.

ArndW · Post by **ArndW** » Tue Jul 20, 2010 2:04 am

This type of error message can take a while to track down, particularly in bigger jobs with local and/or shared containers. Sometimes using "$APT_PRINT_SCHEMAS" can help narrow down the location, since you can track which links between stages contain "CURRENCY" and which don't.

prem84 · Post by **prem84** » Tue Jul 20, 2010 3:57 am

hi i tryed these combinations (operator disable combination and print schemas) but i am getting the same two lines as error message .
Director is not showing which stage the error has orginated

main_program: Field CURRENCY is not in the input data set.
main_program: Fatal Error: Field not found: CURRENCY

kindly suggest

Sainath.Srinivasan · Post by **Sainath.Srinivasan** » Tue Jul 20, 2010 4:05 am

The two options mentioned are not to solve the error but to reveal more information on where it appears and which columns are propogated where.

Check the log and see the difference in the logs - before and after setting the property.

My guess is that either someone changed the shared container and you have recompiled it recently to see its impact OR the source dataset is recreated with new/modified job which now does not provide your currency ID.

prem84 · Post by **prem84** » Tue Jul 20, 2010 10:17 am

i have resolved it.
Solution
-------------
There was sparse lookup with database stage and i have given the field LOC_CURRENCY_CODE as CURRENCY_CODE in the where clause.Since my job involves changing CURRENCY_CODE variable name to LOC_CURRENCY_CODE i have missed it there.

Thank you all for your help