Fatal Error: Added field has duplicate identifier(): X

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
ankursaxena.2003
Participant
Posts: 96
Joined: Mon May 14, 2012 1:30 pm

Fatal Error: Added field has duplicate identifier(): X

Post 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.
Thanks,
Ankur Saxena
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post 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?
-craig

"You can never have too many knives" -- Logan Nine Fingers
ankursaxena.2003
Participant
Posts: 96
Joined: Mon May 14, 2012 1:30 pm

Post 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.
Thanks,
Ankur Saxena
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

So, none of the twenty other posts here which mention that error helped at all?
-craig

"You can never have too many knives" -- Logan Nine Fingers
ankursaxena.2003
Participant
Posts: 96
Joined: Mon May 14, 2012 1:30 pm

Post by ankursaxena.2003 »

Nope. Most of them are for older version of datastage.
Thanks,
Ankur Saxena
ankursaxena.2003
Participant
Posts: 96
Joined: Mon May 14, 2012 1:30 pm

Post 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.
Thanks,
Ankur Saxena
chucksmith
Premium Member
Premium Member
Posts: 385
Joined: Wed Jun 16, 2004 12:43 pm
Location: Virginia, USA
Contact:

Post 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.
Post Reply