DSXchange

That's probably all the utility does.

What exact version are you running? If you're on 7.5 or later you have it but it may not be installed.

It involves editing the registry. Get some help from someone who's done that before if you haven't - wrong moves there can render Windows totally inoperable.

Run 'regedit' and remove any 'Ascential' keys.

When you uninstalled, did you clean out any leftover registry entries as well? That can be key.

AFAIK, you can't. Dbms output must be polled for to be retrieved and Oracle knows and does this (as do other tools like Toad if that option is enabled) but that won't happen in the OCI stage. Have you tried using the Stored Procedure stage instead?

A Sequence job run with a warning limit will pass that limit along to all jobs it runs, meaning they will all inherit the warning limit of the controlling job.

consulting wrote:I checked Do no Check point run

Uncheck that, then read the help on what that does.

arvind_ds wrote:Is this happening because of archival logging in DB2?

That seems like a pretty obvious 'yes' to me. As noted, a chat with your DBA is in order, see what your options are for dealing with your newly slow loads.

Checkpoints are automatic, but as noted they restart you from the point of failure, not the activity after the failure.

Looks to me like it is saying that it can't find 'default.apt' not 'sh.exe'. And that whole 'rsh issued, no response received' is problematical as well.

You don't need a patch, you need to post your code and explain more fully the nature of your problem. And where exactly you are using this code.

Yes, it requires a filename but like you've found you can use /dev/null when you "don't need one" or if you need to use the filename differently than it would otherwise do. Much like you've seen, I've found that it does seem to do a "cat <filename> | <filter>" under the covers, s...

Note the use of the word 'should' rather than 'must'.

Delete those files and break the logging, meaning not being able to run the job until that was resolved. And simply viewing a hashed file updates those timestamps, from what I recall.