Memory problem?! [message #52686] |
Tue, 06 August 2002 11:39 |
Mike Muller
Messages: 4 Registered: July 2002
|
Junior Member |
|
|
We do have the following problem. We've got an Windows 2000 Server with Oracle 8.1.7.3 installed. The machine has 2096 MB of physical and 4095 MB of virtual RAM. Connection to the DB have 3 "Application-Server" via JDBC. The problem is, that we do get very often the following error (in the listener.log):
TNS-12500: TNS:listener failed to start a dedicated server process
TNS-12540: TNS:internal limit restriction exceeded
TNS-12560: TNS:protocol adapter error
TNS-00510: Internal limit restriction exceeded
32-bit Windows Error: 8: Exec format error
Actually, we do not have a real clue, what exactly the problem is. Okay, "Windows Error: 8" means "not enough memory". But that can't be (imho) possible. Coze when it happens, Oracle uses "only" around 1,7-1,9 GB. So there is memory left.
Could maybe someone explain, what the problem could be?!
Thanx in advance
Mike
|
|
|
Re: Memory problem?! [message #52687 is a reply to message #52686] |
Tue, 06 August 2002 11:56 |
Silpa
Messages: 23 Registered: July 2002
|
Junior Member |
|
|
Did you check the parameter PROCESSES in init.ora file.
PROCESSES specifies the maximum number of operating system user processes that can simultaneously connect to an Oracle Server.
Try to increase the number and see if it will solves your problem.
|
|
|
|
Re: Memory problem?! [message #52691 is a reply to message #52686] |
Tue, 06 August 2002 13:51 |
Mike Muller
Messages: 4 Registered: July 2002
|
Junior Member |
|
|
Hi,
it does cloes them right-away. Except those, which are in the pool (30 per app-server). There's a timeout for the connection at 30 minutes.
Mike
|
|
|
Re: Memory problem?! [message #52702 is a reply to message #52691] |
Wed, 07 August 2002 06:41 |
Silpa
Messages: 23 Registered: July 2002
|
Junior Member |
|
|
I think the connections need to be closed instead of timing out.
The connection Pool which we use in Servlets, we run a simple SQL query select sysdate from dual, if it runs fine the pool gives the connection to the servlet
if not it closes it and opens a new connection and gives it.
We are running this from two years till now we never had a problem except in one instance where a servlet was not releasing a connection.
B'coz if connections are not closed properly , you will have max cursors problem after few days. Or else you should reboot your database or Web Server more often that way it closes all the connections.
|
|
|