DSXchange

Good question. I can give it a shot, but since the job ran fine for weeks before this it might take some time to know if it fixed anything. I can do that as a PM, but was hoping someone might have some magic answer for this. Perhaps I'll open a support case with Ascential, let them figure out want m...

I'm afraid this is falling into the Something Weird camp. Got plenty of space and row buffering is off by default - and we're using the project defaults. Unless... There *are* a couple of IPC stages downstream of the transformer that does the lookup on this hash after it is built. Not sure how that ...

Plain vanilla singleton job, OCI -> Transformer -> Hash with no write caching. Only 'odd' thing about this particular one is it is a Type 2 rather than the default dynamic type 30.

Was curious if others have seen this issue. Our hash files are rebuilt every cycle. The option to 'Delete' first is check so that they should be getting 'dropped' and recreated each cycle. However, it doesn't seem like that is always what is happening. This morning, a hash build failed with a write ...

Like I said, I'm pretty sure there is no option to do a Direct Path load in that stage. And I certainly hope you're not running the thing in 'Automatic' mode, that's even slower. You need to look into getting your control files generated once and then you can add the DIRECT=TRUE keyword to the contr...

By the principle, a lookup in DataStage returns only one row to the main stream. I assume it is the last record of the 'record set of multiple records'. Hence if you have an 'Order By' so that the last record retrieved for that query appears at the bottom, you may be able to achieve your desired re...

Or omit it all together as it is the default. You have to explicitly set DIRECT to TRUE to get a Direct Path load.

AFAIK, the 'Ora Bulk' stage only does a Conventional load.

Just some quick points... "Direct path" *is* sqlldr, it is one of two load options - Conventional or Direct Path. Conventional is the slower of the two, obeys constraints and indexes as it goes. Direct Path is faster as it (in essence) defers the constraints during the load which makes it possible t...

Does there exist a technique to do this? Sure, but it involves alot of hand code. You need to be able to start X jobs, constantly loop through and monitor them and - when one finishes - throw another job into the pot. Keep doing that until all jobs are finished. For the Sequencer route, something a...

From what I understand, you need to get your hands on the Java Pack. Not sure if it's something you have to purchase or not, but usually something Ascential has labelled as a 'Pack' isn't free.

Aborts will go through the exception handler and warnings do not. True in 7.5 (as an option) but not before that from what I recall. Aborting is a personal preference, I just don't see a need to do it. I can see where it may make things easier in the latest version with the new Exception Handler, b...

I'm guessing that 'header file' in this context means a custom ".H" type file.

Whether it's 'safe' or not is up to you.

There's no need to abort anything in order to get downstream jobs in a Sequencer to not run, a simple warning in their log (using the 'Warning to Log' routine) works just as well.

I don't believe in forcing anything to abort.

Meaning, if there is no VOC entry you can simply delete them from operating system with your command of choice.

And the 'command prompt' being mentioned would be the Universe/DSEngine/TCL command prompt, I assume. Otherwise, what... prefix the command with 'uvsh'?

Hmmm.... This post might help explain the 'start time from the transformer' part of the problem. Maybe. Depending on exactly how it's being done.