shared container output link problem

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
abyss
Premium Member
Premium Member
Posts: 172
Joined: Thu May 22, 2014 12:43 am

shared container output link problem

Post by abyss »

Hi all:
i got a job involve shared container and I just couldn't make is work...
this is part of my mail job:
Image

I enabled the RCP in the join stage (join mark)
Image

this is the inside of my container
Image

not all the columns from the main job passed into the container. i also enabled the RCP in the transformer stage in this job.
Image

Image

this is how container stage's input tab and output tab setup:
input tab:
Image

output table:
Image

the transfermer stage (trans_fac_own) that after the container stage receive ALL the columns from join stage and one additional column created inside container
Image

the job CAN compile and i receive the following error message when i run the job:

Code: Select all

Error when checking operator: Could not find input field "ENROLMENT_ID".
Error when checking operator: Could not find input field "STD_CRS_ID".
Error when checking operator: Could not find input field "SESSION_ID".
Error when checking operator: Could not find input field "BILLING_TYPE_SKEY".
...... (omit another 20 lines)
and the warning message:

Code: Select all

 Error when checking operator: When binding input schema variable "APT_TRinput0Rec0": A transfer adapter is dropping the non-existent field "FACULTY_OWN".
so basically all the columns that not declared inside the transformer stage in the container are failed to pass. error message is generated from the transformer stage in the main job. However if i change the transfermer stage (trans_fac_own) from the main job to a perk stage the jobs works fine.

I reviewed the thread i posted long time ago, i did the same thing but i still cannot make it work
viewtopic.php?t=153295

does anyone know why?
Last edited by abyss on Tue May 10, 2016 6:44 pm, edited 1 time in total.
Mike
Premium Member
Premium Member
Posts: 1021
Joined: Sun Mar 03, 2002 6:01 pm
Location: Tampa, FL

Post by Mike »

I think this is a likely bug. I've run into a similar issue on version 11.3.

I ended up implementing a workaround for expediency.

My unverified thinking was that it was somehow related to having a transformer stage as first stage after the input with RCP enabled.

I ran into this bug on two different shared containers.

My workaround in one case was to put a copy stage in front of the transformer inside the container, and my workaround in the second case was to replace the transformer stage with a modify stage. Both workarounds were successful.

Mike
abyss
Premium Member
Premium Member
Posts: 172
Joined: Thu May 22, 2014 12:43 am

Post by abyss »

Mike wrote:I think this is a likely bug. I've run into a similar issue on version 11.3.
... to replace the transformer stage with a modify stage.
Hi Mike
thanks for your answer! so the transformer stage is the one inside the container i believe?

abyss
nikhil_bhasin
Participant
Posts: 50
Joined: Tue Jan 19, 2010 4:14 am

Post by nikhil_bhasin »

Check whether column FACULTY_OWN has no spelling mistake, if you have put in manually anywhere before and after shared container. Remaining errors might have been caused due to this warning.
Mike
Premium Member
Premium Member
Posts: 1021
Joined: Sun Mar 03, 2002 6:01 pm
Location: Tampa, FL

Post by Mike »

Yes. The transformer inside the shared container. For whatever reason, RCP seems to fail, which causes those "Could not find input field" errors that you are experiencing.

And it's not all transformers inside a shared container since I have others where RCP worked fine... I never could pin down exactly what combination of factors triggered the bug.

Mike
abyss
Premium Member
Premium Member
Posts: 172
Joined: Thu May 22, 2014 12:43 am

Post by abyss »

thanks so much mike! i did exactly what's you said the my container works now. i been stuck on this part for 2 whole days, i almost cried when i made it work! lol
Post Reply