DSXchange

Pre-sorting is not required, however it does significantly speed the aggregation process if done properly, and is the only way to aggregate 'large' volumes.

Ok, now take a generic but unique portion of that message and search the forums here. For example, I got something like 40 hits when I did an Exact search for "does not fulfill the sort requirements of the downstream operator".

If you assert that the rows are sorted in a certain order and they are not, the stage will abort with the message you've posted. So, either ensure they are actually sorted as you've specified or remove that information from the Aggregator.

Can you post (copy/paste) the exact, unedited message from your logs?

Unless it aborts.

Have you tried searching the forums for that message?

Ok. Since there doesn't seem to be a resolution here, have you opened a ticket with your official support provider?

Define "fine"? Keeping the file directories separate is good, accessing the same source db / tables (from the same or different projects) can lead to problems, including locking, but it depends on your job designs and run timings.

Welcome. First suggestion - search the forums for your topic, more than likely you're not the first person with the question. For example, searching for "dsexport.exe" got 51 hits including this post: m Which would lead you to the OMIT flag, the answer to your second question. I would think the answ...

"Errors" generated during the Server job reset process are normal and can safely be ignored.

Search the forums for "deadlock daemon", all will be revealed.

And what did you find in the LOG file?

I can't answer the question, but check with whomever administers that server, have them verify the SMTP server (etc) you should be using.

Which "first column" - in the XML or outside of the XML?

You linked to a non-existent topic.

What O/S - AIX? The hits I got searching for "util/pathutils.C" problems all seemed to be on AIX.