Fatal Error: Added field has duplicate identifier()

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
vinsashi
Participant
Posts: 150
Joined: Mon Aug 20, 2007 4:52 am
Location: singapore

Fatal Error: Added field has duplicate identifier()

Post by vinsashi »

Hi,
I am performing Lookup.at the run time i am facing this problem
Fatal Error: Added field has duplicate identifier():PD_ID

Code: Select all

inputtablecolumns:
IP_ID
PD_ID(it contains data like AAA,BBB)

RefenceDatasetColumns:
PD_ID(it contains data like 1,2,3)
UNQ_ID_SRC_STM(it contains data like AAA,BBB)

in lookup stage 
i am mapping
   input.PD_ID---Reference.UNQ_ID_SRC_STM(this is key mapping)
IN TargetStage i have these columns
IP_ID(This comes from INPUT IP_ID)
PD_ID(this comes from refrence PD_ID)

I have disabled RCP at Project level.But still i am facing Problem
Note:
But i have to maintain Those column names as same in target ,source,and refrence
any solution with out changing columns names as above
Thanks in adavance
vin..
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

What happens if you map your target IP_ID field from the reference IP_ID field?
-craig

"You can never have too many knives" -- Logan Nine Fingers
vinsashi
Participant
Posts: 150
Joined: Mon Aug 20, 2007 4:52 am
Location: singapore

Post by vinsashi »

In the reference i have only PD_ID,UNQ_ID_SRC_STM fileds only ..So I have to map IP_ID from Source input.
Thanks
vin..
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

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

Post by ray.wurlod »

vinsashi wrote:Note:
But i have to maintain Those column names as same in target, source, and refrence
No you don't. You can change them (to get things to work) and reinstate them downstream.

Check that RCP is not enabled in the job and in the Lookup stage, even though you state that it is disabled as a project default.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply