DSXchange

The issue is always the same when people feel the need to do this - DataStage strips the quotes from the parameter. You need to 'escape' them to try to preserve them.

Why do you think you need to delete anything to be able to 'redeploy your code'?

reachsam11 wrote:BTW, the version is 8.0

BTW - update, update, update!

You seem to have no namespace information in your actual XML so it should be removed from your job.

Please clarify exactly what this is supposed to mean - "The join is on one dummy value of 1 to fetch one value from the reference table". Are you saying you are fetching the same (essentially) static value over and over from a database table? :? Gory details and examples always appreciated.

I wasn't addressing any specific period of time and what it may (or may not) be doing then, just your concerns regarding how long it was/is taking to do the actual work.

What do you consider a "parallel sub routine" to be? Depending on the answer, we could be talking C++ or BASIC here.

That wasn't clear from anything you've posted so far. Then, as noted, mess or not you'll need explicit triggers.

Those commit values are, in effect, your 'transaction size'. That being said, unless your DBAs have you cranked down pretty tight on redo/undo/rollback space, I would never commit that often for 'large' volumes. There are two sides to every story and while Ray is (mostly) right about the use of a si...

There's also the XML Best Practices document at Kim Duke's website.

Another option would be to build a custom routine that scans the current job log for warnings and aborts the Sequence if it finds any.

Right, for the sqlldr part you need to locate the ".log" file and see what it thinks is wrong.

I'd also be curious if the fields used as Key fields for the update are indexed. If not, that's a classic reason why they might take 'longer and longer' - full table scans.

Doing an exact search for @FM would be the first suggestion, or perhaps this might have enough information in it.

What kind of target columns do you have? You'll primarily see this with CLOB or unbounded NUMBER fields, from what I recall.