DSXchange

No, you do not need any "type conversion", your problem is all in the command you are executing. And we need to see the individual log message from when that particular Execute_Command_DEFAULT stage ran, we need details not summary information. Details.

Yes, you can use the OCI stage in a Server job to access 10g, that's what it is there for. The setup steps are documented - an Oracle client on the DataStage server and changes to your dsenv file are all you need.

No, not possible. Please answer my previous questions... and now also explain what "couldn't able to" means here as well.

Please mark your post as Resolved using the big button at the top of the screen.

Doesn't matter, integer or string it will work. Post the log message where it shows the command being run, it will list the 'Output from command' as well. I'll wager it's not what you think it is.

That's an error code. I'd suggest opening the routine and see why/where you are getting it. Permissions? It may not be able to create the hashed file it uses to store the keys.

A couple of points: First, there's no need for the if-then-else construct in a trigger, just the expression itself is all that is needed: Convert(@FM,"",Execute_Command_Stage.$CommandOutput)='0' Secondly, this technique is fine as long as the file does not have a header record, then you ne...

I'm unsure exactly what kind of changes those processes would need to be aware of, and things have (seemingly) been fine without a 'bounce' but point taken.

You know the next question - define "never". And "finishes" while we're at it. How long did you give it before deciding it was never going to finish? What did the job look like at that point - were rows processing slowly, not at all, was it part way thru when you stopped it or ha...

It looks like you've got a reject link coded to abort the job after 1 row is sent down it.

Can you not do something like Shane posted as #2 above - retrieve the max value using SQL and pass that as a job parameter that is the starting value for the job run.

Which Pivot stage did you use and what exactly did you try?

Job design?

Ah good, either way should work but as noted it can depend on your version as "earlier" versions don't support the same variety of expressions that the "later" ones do.

Please make sure you mark your post as Resolved using the big button at the top of the screen. Thanks!

Also keep in mind the fact that encrypted data takes most of the "T" out of "ETL" unless (for example) you perform matching encryptions to things like lookup data as well. Less of an issue if you're just moving the data through the job, of course.