DSXchange

Rules always get tightened up release to release and we see this all the time where something was working that technically shouldn't have been and then an upgrade closes the loophole. Have you done an exact search here for that error?

Not always the case, no... seen circumstances where the ETL tool is waiting for a reply that never comes. Seemed like a good place to start at least.

Spell out your requirements in words. This not only helps us but often times you as well.

Firewall timeout? Oracle idle timeout?

Ah.... THOSE errors.

So seems like we can mark this particular topic as resolved?

How are you planning on processing these files, especially with them arriving 'every two minutes'... looping job? Multi-instance jobs? Is it going to take longer than two minutes to process any given file? Getting the order of the files is just a small part of what you need to do and that can be as ...

I'm unclear why you think it wouldn't work, you should be fine. Do you have access to the documentation for the stage?

Still curious what the issues are that you may be having...

That sounds like a support question.

Have you tried it yet? That's usually the quickest way to answer a question like that. Also, those aren't "duplicates" but rather un-changed records.

A search here should have turned your answer up pretty easily:

http://www-304.ibm.com/support/docview. ... wg21386517

Sure seems like someone turned something on there...

I agree... and done.

sangi1981 wrote:What can cause a deadlock?

Have you talked to your DBA yet? They love to answer questions like that and should be able to dig up the trace from the alert log for you as well to know more about what is going on.