DSXchange

No need to yet-another-post on the same subject.

What 8.x version? For 8.1 there is the istool utility for which the syntax has been documented here by Andy Sorrell. Before that, with earlier versions you're "stuck" with client side processes using dsexport and dscmdexport as noted here and elsewhere.

I would split this into two pieces, seperate the Teradata unload from the Oracle load. And for a "one time" process I'm not sure if I'd even use DataStage for that unless there were transformations involved. Also, I would definitely take this to my Oracle DBA to get their input on how best...

Deja vu. No clue what you mean by a "flowchart" here, however. :? If you want an actual script that will export all projects on your server to date stamped output files, there's a script on Kim Duke's website in the DS Tips section you can take and modify to your heart's content, if so des...

It's not a script, just a single command. If you want an actual script that will export all projects on your server to date stamped output files, there's a script on Kim Duke's website in the DS Tips section you can take and modify to your heart's content, if so desired.

That's certainly one technique, which a search would reveal.

Depends on your network topology, it seems. This is exactly what we've seen here, works for some but not for others. Adding the domain option makes it work for everyone.

From what we've seen here, for 8.x you need to include the "domain" credential as well.

That would be a "vertical pivot".

7.5x2 actually. Other versions before 8.x will not even attempt to run PX jobs and the 'error' it logs is pretty clear on that point.

Found the message:

"This jobtype is not currently runnable on this platform"

You do not need any new lines, formatting is for peoples and XML doesn't care. What happens if you simply send that string directly to an XML Input stage?

You've given us no clues about your hashed file design - which are the key field(s) you are looking up on? Basically you need to ensure the values used to build the hashed file are identical to the values used in the lookup key expression or the lookup will fail. And "identical" means iden...

Can you please post the full, unedited error? And explain when/where exactly it is that you get this error 'once in a while'?

Is your input already a timestamp or is it coming in as a string?

Ok, I'm afraid I don't know the answer but just wanted to get a clarification so that those that could help won't have to ask. Hopefully someone more smarter will be along (like Ray or Vincent) to help you with this.