DSXchange

Check again, it seems to be telling you that your maximum value is in fact 100000000000000000, if that's what you found in your log.

Your Director log view is Filtered, turn it off or increase the limit. Ctrl-T or 'View / Filter Entries' from the log view.

'Takes time'? 'Aborts'? Of course it takes time, you'd need to let us know how much and why you think it's too long. And post your abort message, of course.

No rows rather than an error usually means a metadata mismatch issue. Can you open a single file directly?

- multi instance jobs: change the autopurging to work on number of days in stead of number of runs. this worked for us This is key as - since this is a single job - there is only a single log for all invocations to share. It gets all kind of confused when you have X invocations running and auto-pur...

... which has already been mentioned.

No, there's no such rule - I suspect your sql is just "too long", but don't ask me how long is too long as I don't know the answer, am just aware of the limit. Sometimes taking out all the carriage returns (so it's "one line") helps or perhaps cutting your aliases from "cur&...

Ah... while most things work that way, forgot that the Schedule tab is only enabled for Windows servers. So it won't be an issue here.

Which is one of the solutions that a search would reveal.

Which would typically mean a scripted call to sqlplus.

That wasn't the question.

Didn't say anything about your table partioning, rather specifically how your data is partition over multiple processing nodes. And the fact that it works on 1 node is a big clue. Have you tried Hash (rather than Auto) partitioning?

Not necessarily the wisest choice. Any chance you could answer my last question?

It means you're not logged in as 'dsadm'.

Process is easier for Server jobs, luckily. You can get the information from the 'Finishing' records in the log or by checking specific links in the jobs using DSGetLinkInfo with the DSJ.LINKROWCOUNT info type. From the command line, you could parse it from the dsjob -linkinfo output.