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
PhilHibbs
Premium Member
Premium Member
Posts: 1044
Joined: Wed Sep 29, 2004 3:30 am
Location: Nottingham, UK
Contact:

Added field has duplicate identifier

Post by PhilHibbs »

I'm getting this error message at run time:

Code: Select all

main_program: Fatal Error: Added field has duplicate identifier(): CHG_TYPE_CD
There is no information as to which stage is causing this. I do not have RCP enabled in Administrator. Any tips on tracking it down?

I have only one lookup that I think could possibly be bringing in two columns of that name, and I have tried to avoid the CHG_TYPE_CD from coming in on the reference link by adding a Copy stage between the DataSet component and the Lookup stage and dropping the column in the Copy.
Phil Hibbs | Capgemini
Technical Consultant
PhilHibbs
Premium Member
Premium Member
Posts: 1044
Joined: Wed Sep 29, 2004 3:30 am
Location: Nottingham, UK
Contact:

Re: Added field has duplicate identifier

Post by PhilHibbs »

I found it. There was another lookup that I had forgotten about, and for some reason the CHG_TYPE_CODE had lost its lookup key status.
Phil Hibbs | Capgemini
Technical Consultant
premupdate
Participant
Posts: 47
Joined: Thu Oct 04, 2007 3:37 am
Location: chennai

Post by premupdate »

Enable APT_DISABLE_COMBINATION environmental variable to check which stage produces error...
Cheers,
prem
PhilHibbs
Premium Member
Premium Member
Posts: 1044
Joined: Wed Sep 29, 2004 3:30 am
Location: Nottingham, UK
Contact:

Post by PhilHibbs »

Do I have to change that in the project config? I assume that's a compilation option.
Phil Hibbs | Capgemini
Technical Consultant
premupdate
Participant
Posts: 47
Joined: Thu Oct 04, 2007 3:37 am
Location: chennai

Post by premupdate »

It can be also enabled in job level.

This does not come under compilation category.
Cheers,
prem
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

No, it's a runtime option and that environment variable should be one of the 'standard' ones that you add to every job. Then you can override it to enable it at any time should the need arise.
-craig

"You can never have too many knives" -- Logan Nine Fingers
PhilHibbs
Premium Member
Premium Member
Posts: 1044
Joined: Wed Sep 29, 2004 3:30 am
Location: Nottingham, UK
Contact:

Post by PhilHibbs »

It's already in the paramter list defaulted to TRUE, someone must have already thought of that.
Phil Hibbs | Capgemini
Technical Consultant
KayDye
Premium Member
Premium Member
Posts: 2
Joined: Thu Oct 27, 2011 8:29 am
Location: Athens, AL

We finally found a resolution to this problem

Post by KayDye »

We discovered the problem was that we had made changes to the table and had not imported the table definition since making these changes. Some of the changes were to the NULL/NOTNULL option of fields. We overwrote the table definition and tried it again but still got errors until we reloaded the columns. After reloading the columns into our stage, the error message disappeared!
L. Kay Dye
Post Reply