In which condtions we can not use joiner transformation(Limitaions of joiner transformation)?

Both pipelines begin with the same original data source.
Both input pipelines originate from the same Source Qualifier transformation.
Both input pipelines originate from the same Normalizer transformation.
Both input pipelines originate from the same Joiner transformation.
Either input pipelines contains an Update Strategy transformation.
Either input pipelines contains a connected or unconnected Sequence Generator transformation.

Showing Answers 1 - 34 of 34 Answers

Surendra

  • Jan 25th, 2006
 

This is no longer valid in version 7.2

Now we can use a joiner even if the data is coming from the same source.

SK

  Was this answer useful?  Yes

kanak3

  • Mar 30th, 2007
 

You cannot use a Joiner transformation in the following situations(according to infa 7.1):
♦Either input pipeline contains an Update Strategy transformation.
♦You connect a Sequence Generator transformation directly before the Joiner
transformation.

Vaibhav

  • Apr 3rd, 2007
 

I don't understand the second one which says we have a sequence generator? Please can you explain on that one?

  Was this answer useful?  Yes

swapna

  • Apr 7th, 2007
 


Can you please let me know the correct and  clear answer for Limitations of joiner transformation?


swapna

  Was this answer useful?  Yes

kanak3

  • Apr 7th, 2007
 

You cannot use a Joiner transformation in the following situations(according to infa 7.1): When You connect a Sequence Generator transformation directly before the Joiner transformation.

for more information check out the informatica manual7.1

  Was this answer useful?  Yes

Saurabh

  • Jul 9th, 2007
 

What about join conditions. Can we have a != condition in joiner.

  Was this answer useful?  Yes

utsav mamoria

  • Jul 22nd, 2007
 

No in a joiner transformation you can only use an equal to (=) as a join condition
Any other sort of comparison operators is not allowed

>,<,!=,<> etc are not allowed as a join condition

Utsav

  Was this answer useful?  Yes

vineela

  • Aug 18th, 2007
 

Yes, joiner only supports equality condition

The Joiner transformation does not match null values. For example, if both EMP_ID1 and EMP_ID2 from the example above contain a row with a null value, the PowerCenter Server does not consider them a match and does not join the two rows. To join rows with null values, you can replace null input with default values, and then join on the default values.

divakar

  • Nov 5th, 2007
 

We cannot use joiner transformation in the following two conditions:-

1. When our data comes through Update Strategy transformation, or in other words after Update strategy we cannot add joiner transformation
2. We cannot connect a Sequence Generator transformation directly before the Joiner transformation.

  Was this answer useful?  Yes

Twinkle

  • Jul 25th, 2012
 

Why Joiner transformation cannot be used when either of the input pipeline contains an Update Strategy transformation.

  Was this answer useful?  Yes

We cannot use Joiner t/r immediately after sequence generator and upd strategy t/r as
1. Joiner will join 2 sources and it cannot join 3rd source as seq generator. Also if we select seq generator as 1 source the equi join condition will not match, as seq generator will generate new number every time.
2. The output of upd strategy t/r is flag for (insert, update, delete or reject) which will violate the equi join condition.

Hope this clarifies.

Cheers Mahi

  Was this answer useful?  Yes

Tejas

  • Jun 7th, 2019
 

We cannot use Update strategy in a pipeline when using joiner condition, because update strategy has property i.e treat row as which has insert,update,delete, which are processed at runtime, this limit joiner transformation to know exact properties values till runtime, and then proceed further.

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions