Success! I've now learnt, from our network security admin guy, that the Firewall Manager on the new network is configured by default to timeout inactive connections after 60 minutes. Even though all the user clients are inside the firewall, the server is specially ringfenced because the third-party application suppliers have access to it via PC Anywhere. Therefore the users have to access the server via the firewall, and therein lies the problem! Apparently the old firewall had this feature either disabled or set ludicrously high, but those responsible for the new firewall are unwilling to change the 60-minute default. Obviously they're being far more cautios about accumulating idle connections this time around!
So we now have our solution choices - either someone makes the decision to up the timeout period, or the application vendors fix the app to issue a dummy query every so-many minutes of inactivity... or the users get used to logging in and out of the app when they need it, rather than leaving it running idle all day... It's now a political decision rather than a technical problem. A satisfactory end to the problem, which may well have not been the case without the input from this list, for which many thanks, particularly to Tim Onions, Paul Drake and Tim's resident firewall guru. Paul Vincent DBA University of Central England -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Paul Vincent 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).
