| kill database sessions and processes that are no longer in use [message #55200] |
Fri, 10 January 2003 05:41  |
ayesha
Messages: 2
Registered: January 2003
|
Junior Member |
|
|
I am getting an error,The error is
ORA-00020: maximum number of processes (250) exceeded
Its probably becoz there are many processes running. But most of the processes are pbly just running even after they are no longer used. We have oracle on a Solaris system. Is there any way that these sessions and processes can be killed when they are not in use. Is database restart the only option??
|
|
|
|
| Re: kill database sessions and processes that are no longer in use [message #55201 is a reply to message #55200] |
Fri, 10 January 2003 06:09  |
psmyth
Messages: 81
Registered: October 2002
|
Member |
|
|
if your connections use sqlnet, you can configure that to disconnect idle sessions after a certain time period. Depending on what your application is doing, that may or may not be helpful.
You could just increase the number of connections in the init.ora and bounce the database, but again, that may or may not be helpful.
If your connections are individual users, then I'd suggest disconnecting them using the sqlnet method.
If the connections come from an application layer, then maybe you can configure 'connection pools' in the application and it will look after its own connections.
Basically there are options open to you, it just depends on the application architecture.
Check metalink or the oracle documentation for information on configuring sqlnet.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
