how to handle the join stage warnings

thumati.praveen · Post by **thumati.praveen** » Tue Dec 05, 2006 3:40 am

hi all,

i am using 4 join stages sequentially ,the join lookup is same table for 4 joins and key column also same and i am using the left outer join on 4 joins and 4 joins are produced same column as output.i got output proper but the problem is it is generating the warnings like.........

JoinNZMISSPL01: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.
JoinNZMISSPL02: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.
JoinNZMISSPL03: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.
JoinNZMISSPL04: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.
JoinNZMISSPL01: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.
JoinNZMISSPL01: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.
JoinNZMISSPL02: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.
JoinNZMISSPL02: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.
JoinNZMISSPL03: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.
JoinNZMISSPL03: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.
JoinNZMISSPL04: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.
JoinNZMISSPL04: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.

can u provide the input for this problem

thanks inadvance
praveen

ray.wurlod · Post by **ray.wurlod** » Tue Dec 05, 2006 3:52 am

Stop regarding it as a problem. DataStage is not allowing two columns with the same name to be output.

ajith · Post by **ajith** » Tue Dec 05, 2006 5:22 am

thumati.praveen wrote:hi all,

i am using 4 join stages sequentially ,the join lookup is same table for 4 joins and key column also same and i am using the left outer join on 4 joins and 4 joins are produced same column as output.i got output proper but the problem is it is generating the warnings like.........

JoinNZMISSPL01: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.
JoinNZMISSPL02: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.
JoinNZMISSPL03: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.
JoinNZMISSPL04: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.
JoinNZMISSPL01: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.
JoinNZMISSPL01: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.
JoinNZMISSPL02: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.
JoinNZMISSPL02: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.
JoinNZMISSPL03: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.
JoinNZMISSPL03: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.
JoinNZMISSPL04: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.
JoinNZMISSPL04: When checking operator: Dropping component "MISCORR" because of a prior component with the same name.

can u provide the input for this problem

thanks inadvance
praveen

That is because you are having the same column name on both sides of the join. If you want to get rid of this warning, change the names.

Or else, as Ray said, Stop regarding this as a problem.

Hope this helps,
Ajith

Raghavendra · Post by **Raghavendra** » Tue Dec 05, 2006 6:24 pm

Try message handlers to demote these warnings to information..

Sreenivasulu · Post by **Sreenivasulu** » Tue Dec 05, 2006 10:00 pm

Hi

Ignoring Warnings is easy but if you have a standard restartability feature (doing truncation of data load in case of warning) then it could be a problem

Regards
Sreeni

Nageshsunkoji · Post by **Nageshsunkoji** » Wed Dec 06, 2006 3:37 am

Hi,

Warning Messages- We have to analyse those warnings properly and by max, we have to find the cause and solution for the same.

Message Handlers are helpful, whenever your warning is not harming your job and if your unable to find a solution for your warning.

Warning like Prior Component with same is quite possible to fix. Don't go for Message Handler.

You have two options here to solve the above problem.
1) Rename the columns at the output of Join stage
2) Switch Off the RCP

thumati.praveen · Post by **thumati.praveen** » Wed Dec 06, 2006 5:41 am

Nageshsunkoji wrote:Hi,

Warning Messages- We have to analyse those warnings properly and by max, we have to find the cause and solution for the same.

Message Handlers are helpful, whenever your warning is not harming your job and if your unable to find a solution for your warning.

Warning like Prior Component with same is quite possible to fix. Don't go for Message Handler.

You have two options here to solve the above problem.
1) Rename the columns at the output of Join stage
2) Switch Off the RCP

hi
thanks for ur input

if i switch off the RCP the data is not visible in the target and
if i rename the out columns that is also the same problem the data is not visible in the target,but in both cases the performence statistics is showing the data is moved all the records from source to target.

thanks
praveen

Nageshsunkoji · Post by **Nageshsunkoji** » Wed Dec 06, 2006 5:44 am

What is your Target ?

Is it a Dataset or Database ?

thumati.praveen · Post by **thumati.praveen** » Wed Dec 06, 2006 5:59 am

Nageshsunkoji wrote:What is your Target ?

Is it a Dataset or Database ?

Dataset

Nageshsunkoji · Post by **Nageshsunkoji** » Wed Dec 06, 2006 6:04 am

thumati.praveen wrote:
Nageshsunkoji wrote:What is your Target ?

Is it a Dataset or Database ?

Dataset

Data is not visible means, is it showing dataset is not created in the mentioned path or it is simply showing dataser created but no data. that means empty dataset.

are you able to view the data without these two options ?

The path your passing at run time is it the right path ?

ray.wurlod · Post by **ray.wurlod** » Wed Dec 06, 2006 7:43 pm

Disabling RCP means that columns that formerly were automatically transferred are now not being transferred. You have to explicitly design in those transfers (mappings) if you require them to occur without RCP.

thumati.praveen · Post by **thumati.praveen** » Thu Dec 07, 2006 3:56 am

Nageshsunkoji wrote:
thumati.praveen wrote:
Nageshsunkoji wrote:What is your Target ?

Is it a Dataset or Database ?

Dataset
Data is not visible means, is it showing dataset is not created in the mentioned path or it is simply showing dataser created but no data. that means empty dataset.

are you able to view the data without these two options ?

The path your passing at run time is it the right path ?

i am not using the parameters.
everithig is correct

sud · Post by **sud** » Thu Dec 07, 2006 4:13 am

Please switch off RCP only in the input stages to the join, keep RCP on in the joiner output.

Nageshsunkoji · Post by **Nageshsunkoji** » Thu Dec 07, 2006 5:57 am

I am still confused ...

Y the RCP switch off and renaming columns is not giving the results to you ?

What is the status now ?

thumati.praveen · Post by **thumati.praveen** » Thu Dec 07, 2006 7:09 am

sud wrote:Please switch off RCP only in the input stages to the join, keep RCP on in the joiner output.

Hi,

i did what u said, but their is no change in my target dataset the data is not come.

DSXchange

how to handle the join stage warnings

how to handle the join stage warnings

Re: join stage warnings