DSXchange

No extra steps needed to extract from Table A in server X and load it to table B in server Y. Make sure the tnsnames.ora file on the datastage server has the right entries for both the server X and server Y.

Thispost may help.

There are quite a few parallel routines posted here. Search on keywords like 'parallel routine', 'pxEreplace' etc.

Even if the routine approach works for you now, it might not in 30 days, as it will expire. DataDirect does not allow usage of its drivers outside of the database stage. You might want to take that into consideration.

Try searching. I am sure you will find bits and pieces lying here and there in archive posts.

I say its one of the best.
Don't sweat on 'the best way to do it'. You got a piece working with good logic. Good job.

Clear the logs of a few jobs. Make space. The try clearing the RT_LOG of that particular job.

Reject mode will only work if its Upsert and will not work for Load. That too in the enterprise stage. Not the OCI stage.

Duh....Clumsy me. Sorry about that. Most of the cases I have dealt with is the absence of space between the date part and time part. Anywho, good luck.

A small correction in your stage variable derivation. You need a space between the date part and the time part.

Just in the Administrator. But it will not effect the pre-existing jobs. Ken has a utility that purges logs as well as sets the purge limit. Search for it here.

I think its an issue with SetNull() in a stage variable. I know I have read something about it here. Search in the archives.

Time to mark your post as "Resolved".

Check here.

Is your sequence job multiple instance job? If it aborts, it should be in Aborted/Restartable state. You do not require it to be RESET as far as I remember, its been a while since I worked with job sequences.