DSXchange

What kind of query - one that does sorting/grouping that would cause it to hold on to all the records until ready? You may have a network/firewall timeout issue if that's the case.

Is the sqlldr "abort" logged only as a Warning in the job's log? I'm wondering if your 45 records aren't aborting the job because they're fewer than the default "abort after 50 warnings" setting when the job runs.

Azzuri wrote:Is it better to store the data on a separate server (Maybe a windows file server?)

Short answer? No.

Welcome! :D

Scheduled how, via Director? What makes you think the Scheduler actually 'runs on time'?

Search the forums for your actual error message, it has been discussed here before and yes, typically involves a permissions problem.

True, true... they tend to do that.

Two actually, but neither has a resolution and even Ernie was stumped, which isn't a good sign. Probably best to open a case with your official Support provider.

I suspect so too.

Also, did you notice Ray's first sentence - " Have you diligently maintained"? Without that, the routine will do you no good. And I'll wager that hardly anyone will be shoving their hand up in the air and proclaiming wildly "Ooo - Me! Me! I have!". Well... except perhaps where the Hand of Wurlod has...

Originally posted and responded to here. Not sure why the repost except to (I suppose) perform the forum move.

A continuation from this question:

http://www.dsxchange.com/viewtopic.php?t=120688

Please do not start a new post to reply to an old one, simply 'Reply' within the old one so that the entire conversation stays in one place.

You are going to have to expand on your requirement here, explain why you are asking this. Short answer, there's no such thing in a Parallel job. There are job control structures for looping, but we need a better idea what you are trying to accomplish before anyone can give a qualified answer to you...

Then I'm out of ideas. Bug? Can you not use an OCI stage rather than <cough> ODBC in your job? Hmmm... is this generated or user-defined sql? If for some odd reason you went user-defined for this, switch to generated and see if the problem goes away.

You can't process "dynamic derivations" like that, they just become strings / data in the job rather than functions. If you really want to do this, you'll need to consider a Routine approach that builds and applies the derivation and then passes back the result.

Interesting. A record certainly has null for that field. What Array Size are you using for that link? If it is great than one, I'd wager the wrong record is being reported as the problem child. Temporarily change the job to use an Array Size of 1 so you can find the culprit.