For what it's worth, we had the same thing going on here recently and have not resolved it. In our case, it is a visual basic app running what is essentially a batch job (don't ask me why a batch job was written as a VB app; I just work here). The client is a PC, and the database is on Tru64 (again ... I just work here). Three different PC's were tried. It appears that the tcp_nodelay parameter worked on two of them but not the third (which, as you might guess, is the production box and the one on which it NEEDS to run faster ... Of course!). All the PC's are on the same subnet, going through same routers to get to the same database.
If you get the problem resolved, I will be most interested in your solution. Thus far, we have only been able to attribute it either to sunspots or something about the W2K OS on the PC ... both of which, as we all know, are responsible for a lot of unexplained behavior. -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Stephen Lee INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
