DSXchange

Yah, I meant to ask for that clarification in my first post, but didn't for some reason. Could have saved some churn.

I guess it's not all about how much power you have. This morning was really bad - probably 95% of the posts I made 'stalled' at the posting screen. If I've gotten three or four boxes into the status bar and it's still sitting there, I click 'Stop' and then click the Forum header to avoid double-pos...

Welcome. :D It did not work because we have a license document without an Authorization Code! So... you don't have an auth code for RTI? Without that you're not going to get much working. And you don't (typically) install all of the components on the DataStage server. The 'RTIAgent' is the only piec...

Ok... then explain this:

ramasubba wrote:after the completion of installation then took simple job and run,

seq->tr->seq - compile & run successfully

Was, in fact, this "simple job" a Server job? If so, these kind of minor little details [cough] really need to be included in your posts.

To correct the second problem, apply the MicroSoft standard remedy - reboot!

Didn't we just go thru this recently? Nothing about doing an inner join ensures you only get out as many rows as exist on one side of the join. It's all about the keys and data in both tables. It is about multiple matches on the 'right' table in your case.

... and we are.

Is Roy secretly moving posts with no 'Hey Moderator' bait?

Brief? Version Control.

Hadn't thought of that approach. I would think it means... Starting with sorted input, use stage variables to concatenate values per 'key' but don't worry about constraining the output. You'd get records like... 1, A 1, AB 1, ABC 2, A 2, AB Etc. Then send the rows through an aggregator, group on the...

Any major problem will be reported as a failure of the Transformer as it is the active stage. I'd wager this is an issue with the 'user defined sql', possibly aggravated by their choice of Oracle Client version.

What exact version of the Oracle client are you using?

As long as you understand that will affect all running jobs.

Your job needs to abort in order to rollback any uncomitted records. And I'd suggest you use one target DB stage if at all possible.

If you need an 'urgent reply ASAP', contact your official Support provider. You pay them big bucks for just this kind of thing.

Must be 'Special Character Day'.

http://www.dsxchange.com/viewtopic.php?t=116452

D'oh!