DSXchange

The fundamental question here is - How to run a Sequence job that has finished as Stopped\Restartable without explicitly recompiling or resetting it? That's a different question than the one we started with - and one you'd need to pose to Support. I agree - it makes no sense to mark it as 'Restarta...

#1. Without knowing your specifics, a qualified Yes. #2. No. That is a bulk loader stage, not OCI, so it only does inserts. That doesn't mean you can't use it however. You could leverage Oracle by bulk loading your changes into a work table and then issuing a MERGE command. Talk to your DBA to see h...

Also, Craig relying on the 'Automatically handle activities that fail' option alone does not work since the subsequence does NOT stop or abort, although the MasterSequence aborts. Just wanted to check before we spent too much time on a more... esoteric... solution. In my other comment, I just meant...

KYX wrote:Got it from IBM, limit is 999, solving that problem.

Actually, you heard that here first.

Yes.

I don't think I've got a job with this issue - a 'normal' job and a Sequence job at the same level and a failure of the normal job needs to abort the Sequence. So you've got an Exception Handler and an explicit Terminator at this level as well? What happens when you take those out and just rely on t...

If you've checked and the file still isn't renamed, then you are a victim of the bug I mentioned earlier. It's hard to track down because everything gets translated properly in the log but the actual command run still has the '#'s in it. You'll need to pursue the Routine Activity route. Or upgrade.

Or perhaps just putting the indexes back.

WaitForFileTest..JobControl (ExecSH): Executed command: mv /ascential/datastage/70/d02/test.txt /ascential/datastage/70/d02/test.arc *** No output from command *** That all looks fine. What makes you think it didn't work? There is no 'output from command' when it works properly - it just renames th...

Of course it is. How large is your hashed file when the job completes? As a rough rule of thumb, take the two files - DATA.30 and OVER.30 and add up their byte sizes. Divide that by 2048 and use that number as the minimum modulus. See what happens.

well in the execute_command stage , in exeCommand tab under command i have given this command mv #Path#/#OldFile# #Path#/#NewFile# and in the parameter i have not given anything . What happened to your assurances that you'd put the parameter portion of this command into the Parameter area? What hap...

You dropped the indexes and disabled constraints on the table you were reading from? What in the world for? Put them back.

What hashed file properties are you using? The default minimum modulus of 1? Not properly sizing your target hashed file will kill your performance.

mv #Path#/OldFile# #Path#/#NewFile# Well, there's one obvious problem - assuming this accurately represents what is in your job, you are missing a 'hash' or 'pound' sign: mv #Path#/#OldFile# #Path#/#NewFile# However, since none of the properly formatted job parameters were translated in the log, yo...

Technically, that's actually an 'Ordinal' date - the year followed by the number of the day within that year. However, from what I recall, that DateFromJulianDay function is actually expecting an Ordinal date.

Thats good to see that. According to document its both AT and CRON. Not sure where, what is been used. Yes, both - and it depends on whether your scheduling request is a 'recurring' request or not. A 'one time' request - run this job next Tuesday at 8AM - will be scheduled using AT. One that repeat...