Page 1 of 1
Fatal Error: Added field has duplicate identifier(): X
Posted: Fri Oct 24, 2014 1:38 pm
by ankursaxena.2003
Hi,
I am getting below error....
main_program: Fatal Error: Added field has duplicate identifier(): X
The job was created in DataStage 8.5 and it was running fine. But when I moved the job to DataStage 9.1... I started getting error and the job is aborting.
Posted: Fri Oct 24, 2014 1:58 pm
by chulett
Rules always get tightened up release to release and we see this all the time where something was working that technically shouldn't have been and then an upgrade closes the loophole. Have you done an exact search here for that error?
Posted: Mon Oct 27, 2014 11:40 am
by ankursaxena.2003
Yeah I know.... I tried searching the web but all of them are asking to make changes to RCP. But, we have same setting on both DS version. So I dont know if that will make any thing different.
I will open a PMR with IBM today and keep you posted.
Posted: Mon Oct 27, 2014 12:40 pm
by chulett
So, none of the twenty other posts here which mention that error helped at all?
Posted: Mon Oct 27, 2014 3:13 pm
by ankursaxena.2003
Nope. Most of them are for older version of datastage.
Posted: Wed Nov 19, 2014 3:33 pm
by ankursaxena.2003
I found the issue....
The issue was that on one of the link in the job had Range Look up check box clicked but the key expression was missing.
Same job was running fine in DataStage 8.5, but with DS 9.1 release they have tightened the rule and now it is looking for key expression if range look up check box is clicked.
Posted: Wed Sep 13, 2017 9:12 am
by chucksmith
In my case, the primary input of the Lookup stage had two range key columns. One range call was RANGE(lkp.A, "<", lkp.B, ">", 0), and the other was RANGE(lkp.C, "<", lkp.B, ">", 0).
I duplicated column lkp.B, creating column lkp.Btoo, then change the second range call to: RANGE(lkp.C, "<", lkp.Btoo, ">", 0), which got me past this problem.