Error: Field already present in the output interface schema.

yousuff1710 · Post by **yousuff1710** » Tue May 26, 2009 7:36 am

Hi All,

We are doing testing for a convertion project.
While running a job I got a strange following error:
main_program: APT_StatReducer:field IMPO_FSPR_EME_RES_OP_EUR11 is already present in the output interface schema.
This is first time I am facing such an error. I am working on same.
Meanwhile if anybody can give some ideas/inputs, that will be appreciable.

Thanks in advance,
Yusuf

mikegohl · Post by **mikegohl** » Tue May 26, 2009 7:49 am

Are you using RCP?

yousuff1710 · Post by **yousuff1710** » Tue May 26, 2009 8:03 am

No, RCP is disabled in job-level.

yousuff1710 · Post by **yousuff1710** » Tue May 26, 2009 8:04 am

No, RCP is disabled in job-level.

ArndW · Post by **ArndW** » Tue May 26, 2009 8:25 am

What stage type is generating this error?

abhishekraj · Post by **abhishekraj** » Tue May 26, 2009 8:36 am

yousuff1710 wrote:No, RCP is disabled in job-level.

Check whether RCP is enabled at the stage level.
Are you using an aggregrator stage? Make sure the input schema field IMPO_FSPR_EME_RES_OP_EUR11 is not used in "Column for calculation".

yousuff1710 · Post by **yousuff1710** » Tue May 26, 2009 9:03 am

Hi Arndw,

The log is not showing the stage in which error is generated. The error is like:-
main_program: APT_StatReducer:field IMPO_FSPR_EME_RES_OP_EUR11 is already present in the output interface schema.

Abhishek,

Yes, I am using aggregator stage: Here the input schema field for IMPO_FSPR_EME_RES_OP_EUR11 is IMPO_FSPR_EME_RES_OP_EUR1.
Here, aggragator is doing Sum(IMPO_FSPR_EME_RES_OP_EUR1) & its output col. is IMPO_FSPR_EME_RES_OP_EUR11.

Thanks for your replies.

yousuff1710 · Post by **yousuff1710** » Wed May 27, 2009 7:37 am

Thanks guys for all your inputs.
This issue has been resolved.
The issue was in aggregator stage but everything was ok in stage - I mean mapping, properties......
So, I deleted the stage and newly inserted stage & did mappings. Its working fine now.
I dont know what was the problem; may be job was corrupted (it sounds funny

yousuff1710 · Post by **yousuff1710** » Wed May 27, 2009 7:39 am

Also I did all those changes taking copy of original job.
After modiications I deleted original & renamed the copy job back to original.

mpav6450 · Post by **mpav6450** » Mon Dec 13, 2010 3:42 pm

The issue occurs in situations when you incorrectly use the Aggregator stage. It means when you use one output column for more then one calculation (for example will sum up Reveue and Costs and both of them will store into one column RevenueSum.

Martin Pavlik, IBM