Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
I sort of remember that if users are inactive and killed by alter
session kill, then they will still exist in v$session.
The only chance they go away is while they try to use the terminated
session again, they will get ORA-00028.
Or maybe you can try "alter system disconnect session 'sid, serial#'
post_transaction;" and see if that can "scare" away these "spirits"...
Please correct me if I am wrong.
Gautam_Reddy_at_Dell.com wrote:
Hi All,We have 8.1.6 database on an NT server and we have webserver
which accesses database. Due to some problems with the application on
the webserver we have to bounce it once a week. When we bounce the
connections to the database are still existing with the database
forever. Over a period of time this connections pile up. Has anyone
see this behavior. When we talked to oracle support they suggested us
to put the sqlnet.timeout parameter to timeout the session. This would
be a big overhead on the already exhausted system. Any pointers on how
this could be resolved would be appreciated. ThxGautam
--which accesses database. Due to some problems with the application on
the webserver we have to bounce it once a week. When we bounce the
connections to the database are still existing with the database
forever. Over a period of time this connections pile up. Has anyone
see this behavior. When we talked to oracle support they suggested us
to put the sqlnet.timeout parameter to timeout the session. This would
be a big overhead on the already exhausted system. Any pointers on how
this could be resolved would be appreciated. ThxGautam
Keith Shum
kshum_at_iLux.com
iLux Corporation
Phone (510) 226-5600 x 643
Fax (510) 226-8182
Cellular Phone (510) 435-0286
5600 Mowry School Road, Newark, CA 94560
http://www.iLux.com
Web site analysis for NT and Unix
"Share what you know. Learn what you don't." -- From Deja.com
--------------7600D9D61246EEB81E737A8C
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
I sort of remember that if users are inactive and killed by alter session
kill, then they will still exist in v$session.
The only chance they go away is while they try to use the terminated
session again, they will get ORA-00028.
Or maybe you can try "alter system disconnect session 'sid, serial#'
post_transaction;" and see if that can "scare" away these "spirits"...
Please correct me if I am wrong.
Gautam_Reddy_at_Dell.com wrote:
Hi
All,We
have 8.1.6 database on an NT server and we have webserver which accesses
database. Due to some problems with the application on the webserver we
have to bounce it once a week. When we bounce the connections to the database
are still existing with the database forever. Over a period of time
this connections pile up. Has anyone see this behavior. When we talked
to oracle support they suggested us to put the sqlnet.timeout parameter
to timeout the session. This would be a big overhead on the already exhausted
system. Any
pointers on how this could be resolved would be appreciated. ThxGautam
--
Keith Shum
kshum_at_iLux.com
iLux Corporation
Phone (510) 226-5600 x 643
Fax (510) 226-8182
Cellular Phone (510) 435-0286
5600 Mowry School Road, Newark, CA 94560
http://www.iLux.com" rel="nofollow">http://www.iLux.com">http://www.iLux.com
Web site analysis for NT and Unix
"Share what you know. Learn what you don't." -- From Deja.com