DSXchange

Bah... it's a perfectly valid strategy, even for 'millions' of records as long as your database is properly setup for it.

Are you asking how can you change it or how can you know what to change it to? And are you thinking about changing the default?

Be very careful there, it can have quite unexpected consequences.

Is there really a difference between 'executing' and 'calling' a job? Regardless, an exact search for dsjob with an author of kcbland should turn at least one up.

What issue are you having? They should "load" just fine, typically.

Right... 'read only' means they can't be modified but they can still be run. And if you want to discuss that, please start a new post.

Actually, no. The Server Transformer is not the same as the BASIC Transformer. You'll find the latter in the repository browser under Stage Types \ Parallel \ Processing.

"Load"? To expand on this a little, a description of your complete job would be helpful, so we have some idea what "load" means in this context.

Have you searched here? An exact search for "could not create operator sync table" got me 15 matches, see if any of them help.

Dang, missed that it was a Parallel question. [sigh]

As with most things PX, you've got a stage for that.

Try switching the position of 'Server' and 'Body' in the string you build, Body should be last AFAIK.

Both are correct. You do want to avoid writing to disk to improve performance. However, given the choice of throttling down the upstream operator or writing buffers out to disk, they're saying the latter is preferred to eliminate the 'pushback'. I don't seem them as being contradictory.

That doesn't necessarily mean their solutions are not applicable to you. If you're sure nothing there helps, then ping your official support provider 'cuz that's all we've got here. Unless someone else chimes in, of course...

Do an exact search for "Oracle client version 0 is NOT supported", there are two Resolved threads here on that topic. They should help.

Odd. Can you post the complete, unedited error and let us know if this is only an issue with jobs that access Oracle or if somehow this is affecting all jobs?

So, that's just the way it works, eh? Interesting.