DSXchange

10g is officially supported, 11g is not but I believe people here have had success with it.

I missed the mention you made of having to change the "hosts" file, never seen a need to do that before. You should be able to hit an individual RAC instance just like any other but you set up all nodes so it can do it's own balancing from the virtual node. Here's an example with the names...

What, you don't like the "guess what I am thinking" game? So many opportunities to play it here.

In all honesty you shouldn't need to do that but it is the proper solution.

Sorry, but what does "job is working fine with old database" mean?

OK, not syntax I've ever seen before. What happens if you remove the "%" from the query?

I think we've gone beyond assumption here.

Check your math and add an explicit check to stop dividing by zero.

ray.wurlod wrote:As far as I'm aware it's not possible. The Hashed File stage does not even support parameters for the File Name property.

As noted, certainly possible, fully supported and quite handy.

myukassign wrote:do u tink

No, U no tink.

So, this is resolved? Can you post the resolution, please?

Assuming all of your parameters are properly resolving, the 'illegal character' is the percent sign. What is %DateTimeIn() supposed to be, a stored function?

ProfileStage. Can't forget the 'Stage', man.

So... everything is handling decimals "properly" now except for the Aggregator? Is that the only place where this issue remains or are there other places where you still see this?

Hmmm... the only way to implement a 'conditional' lookup is as you've noted - split the stream, do the lookup only on the appropriate rows and then merge the two back together. I, however, never really found it worth the trouble. A properly set up hashed reference shouldn't be a bottle-neck in a job...

Patience. If anyone has any, they will.