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.
Fatal Error: Added field has duplicate identifier(): X
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 96
- Joined: Mon May 14, 2012 1:30 pm
Fatal Error: Added field has duplicate identifier(): X
Thanks,
Ankur Saxena
Ankur Saxena
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
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 96
- Joined: Mon May 14, 2012 1:30 pm
-
- Participant
- Posts: 96
- Joined: Mon May 14, 2012 1:30 pm
-
- Participant
- Posts: 96
- Joined: Mon May 14, 2012 1:30 pm
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.
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
Ankur Saxena
-
- Premium Member
- Posts: 385
- Joined: Wed Jun 16, 2004 12:43 pm
- Location: Virginia, USA
- Contact:
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.
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.
Chuck Smith
www.anotheritco.com
www.anotheritco.com