Page 1 of 2
When checking operator: Dropping component
Posted: Tue Oct 27, 2009 5:11 am
by Prakash3366
HI All,
I am having a problem
Tr_DAT_MAJ_SOCLE: When checking operator: Dropping component "DAT_MAJ_SOCL" because of a prior component with the same name.
Could you let me know , for what reason we are getting this warning.
Thanks
Prakash
Posted: Tue Oct 27, 2009 5:41 am
by chulett
First question is always going to be - have you searched here for a portion that message? You're not the first person to have this issue.
Re : When checking operator: Dropping component
Posted: Tue Oct 27, 2009 11:44 pm
by Prakash3366
My problem was not resoved by searching in the forum. So again i posted in the form..
Please send me the suggestion for this problem
Thanks
Prakash
Posted: Wed Oct 28, 2009 12:29 am
by gssr
As the message itself clearly tells you, there is a column name that is similar in the two links that you have used. Try the message handler to avoid the message
Posted: Wed Oct 28, 2009 2:00 am
by ArndW
I prefer not to hide the cause of the problem by using a message handler but to correct the issue. What type of stage is producing this error?
Posted: Thu Oct 29, 2009 12:36 am
by Prakash3366
In transformer i am facing this issue.
Thanks
Prakash
Posted: Wed Nov 04, 2009 2:04 am
by samyamkrishna
the job design is as given below.
[dataset] ----> [Transformer] --------> [Teradata enterprise stage]
the error message is
"Tr_DAT_MAJ_SOCLE: When checking operator: Dropping component "DAT_MAJ_SOCL" because of a prior component with the same name"
The column dat_maj_socl is not present in the dataset.
but in the transformer and Teradata table it is present.
in transformer we are giving dat_maj_socl as StringToTimestamp(L_TIMESTAMP,"%yyyy-%mm-%dd %hh:%nn:%ss")
This warning dosent make sense because there is no other component with the same name and this column is being added in the transformer with above given definition.
I dont even know from where to start.
Need help
Thanks in advance
Posted: Wed Nov 04, 2009 2:37 am
by ray.wurlod
Is dat_maj_socl referred to twice (or more)?
Posted: Wed Nov 04, 2009 3:42 am
by samyamkrishna
no its refered only once.
dataset does not have dat_maj_socl
in transformer we are adding teh column dat_maj_socl with StringToTimestamp(L_TIMESTAMP,"%yyyy-%mm-%dd %hh:%nn:%ss")
in teradata we load dat_maj_socl which is comming from transformer.
Thanks,
Samyam
Posted: Wed Nov 04, 2009 4:33 am
by ray.wurlod
Please post the complete detail of the error message, including the error message ID.
Posted: Wed Nov 04, 2009 4:39 am
by samyamkrishna
Tr_DAT_MAJ_SOCLE: When checking operator: Dropping component "DAT_MAJ_SOCL" because of a prior component with the same name.
it is a warning.
Thanks
Samyam
Posted: Wed Nov 04, 2009 4:40 am
by ray.wurlod
And the error message ID ?
Posted: Wed Nov 04, 2009 4:47 am
by samyamkrishna
There is no error message id in the warning.
or where will i find it?
Thanks,
Samyam
Posted: Wed Nov 04, 2009 5:23 am
by samyamkrishna
Does this have to do anything with partitioning
Thanks,
Samyam
Posted: Tue Sep 27, 2011 3:52 am
by patelamit009
Hi All,
I was also facing the similar kind of error message in one of my job development in transformer stage as below.
Transformer_113: When checking operator: On output data set 0: Dropping component "keyChange" because of a prior component with the same name.
I tried all options that were suggested in the thread and i wasnt successful. Finaly, i realised the problem was due to RCP enabled in the job level. After unchecking it, i get rid of the error.
But, any one could help me out to understand how RCP related to this error ?
Thanks in advance.