| SQL*NET timeout problem [message #367865] |
Tue, 14 November 2000 04:29 |
Geir Waade
Messages: 1
Registered: November 2000
|
Junior Member |
|
|
|
My corporation uses an application built on Oracle on WinNT4. We are currently using v.7.3.4 for the DB, with three instances. After a software patch (the application, not Oracle, although some scripts updating the database was included in the upgrade process), users on WAN links are experiencing timeouts when not using the application within a certain period of time. When they pick up the application after about an hour, they get a "Not connected to Oracle" error message. Support personnel at the software company that wrote the application claims this to be an internal error in the SQL*NET settings. Being the DBA at my corp, I have not tampered with the SQL*NET settings since moving the database to another server about a year ago, so I can hardly see that's a problem. Does anyone have a clue to what might cause this problem? Unstable WAN links? Timers in the database? Other circumstances? I'm all blank. Thanks for all support :-)
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
