We are on a mixed bag of versions of the oracle server.
We are in the process of upgrading from oracle 8.0.5.0.0 to oracle
10.2.0.1.0
and our customers are complaining about not being able to re-connect to
our application if
they have a PC that crashes and then they try to go to another work
station and login.
Our software has a policy setup that a user can only be connected from
one IP address at a time
to the system. The v$session table is read and if the ip address for the
username, is different from
that of the session that is connected, then the user is denied access. I
know how to kill the session
but oracle 8 sometimes takes 30 minutes to delete the session from the
v$session table. We have
changed our software to look at the status and see if it is set to
"SUEDO KILLED" then we will allow
for access.
Does anyone know if oracle 10G handles the case when a session is no
longer active due to
the PC crashing that is connected to the database?
Is there a setting in the init.ora file that pertains to inactive
sessions getting cleaned up on either database version?
Does oracle 10G poll back to the application that is connected to
validate if the connection is still active?

Thanks in advance for your time.
Steve St. Laurent


Oracle LazyDBA home page