DSXchange

No, it is not.

Why not disable Buffering? I can't imagine it is buying you anything here, other than trouble that is.

Sounds like you've already tried everything we could suggest, time to ask your official support provider for help.

Same way as in any other version - typically, a routine that gets and formats the time. A Routine Activity in a Sequence job can then easily pass it to the job. @DATE, @TIME, TimeDate() etc can be used to get this information.

Just pass it. Sorry, but if you want a better answer you're going to need to ask a better (more detailed) question. Perhaps an example would help.

But if i do that as a normal process, all the records are fetched at once and all records are processed and loaded into database at once and that is what i do not want. No, they are not. They are "processed and loaded" one at a time as noted. Your issue is the fact that your database writ...

Yup. While Oracle may not notice you stopping the job, DataStage will notice you killing the Oracle session.

Right, set the interval higher or turn the refresh off altogether. And on the off chance you think you need to leave the Director open after starting a job until it completes - you don't.

Any chance you have a trigger on your target table?

You can't get that information from that "report". You need to either farm the logs or query the appropriate links directly for their counts. Exactly what "statistics" are you interested in?

You can query the repository for that and a search for OLETYPE and/or CSeqInput should turn up the previous conversations on the subject.

Or you can just wait for someone to post the query for you.

Good to know.

For DataStage? The pdfs in your PC's "Docs" directory. Otherwise, the vendor: http://www.datadirect.com/index.ssp would be a good place, I would think.

There must be some "Access People" there you can work with to accomplish that. Me, I have no clue and don't really want one.

You can do separate steps - one to dump the Access data to files and transfer them to UNIX, then a DataStage job to load to Oracle. An Enterprise Scheduler can easily tie them together. Or purchase ODBC drivers and do everything from DataStage.