Oracle Database Discussions

Hi,

I'm having some troubles with Terminal Services and Dead Session as described below.

Users connect in our server using Terminal Services (Remote Desktop Connection). Once inside the server, they start an application. In a given moment, the application needs to run a very long Stored Procedure, and sometimes the connection between the users' PC and the Terminal Service Server is lost due to any reason, without doing the logoff and the Stored Procedure still running.

This is constantly happening, sometimes blocking new users to connect into the database, raising an ORA-00018 error (maximum number of sessions exceeded). To allow these new users to connect, we increased the number of possible sessions, changing the parameter SESSIONS to a higher value.

I've tried to use the Dead Connection Detection, setting the parameter SQLNET.EXPIRE_TIME, into the sqlnet.ora file, to 5, and see if the sessions are killed when it detects as broken connection between client/server, but happens that it only detects when the client PC is rebooted, as reported in Bug#280848, from Oracle Metalink, and thats not the case.

I also tried to wake up PMON process sometimes, but as I read, it already wakes up from 3 to 3 seconds.

My question is: Is there any way to detected these "broken" sessions and kill them without using OS resources, like the kill -9 command, preferentially using a Stored Procedure?