Hi :
Is there any way to identify an oracle connection which is idle for <n>
minutes and kill it automatically ? Please let me if you have any clue
on it.
Thanks,
Bala.
by Balakrishnan Subramania » Thu, 31 Jul 1997 04:00:00
Hi :
Is there any way to identify an oracle connection which is idle for <n>
minutes and kill it automatically ? Please let me if you have any clue
on it.
Thanks,
Bala.
by Charles L. Ragan, Jr » Thu, 31 Jul 1997 04:00:00
There is the dead connection detection that SQL*Net provides if that is
what you are looking for. If so, look in the "Understanding SQL*Net"
manual under the sqlnet.ora documentation.
Larry
> Is there any way to identify an oracle connection which is idle for
> <n>
> minutes and kill it automatically ? Please let me if you have any
> clue
> on it.
> Thanks,
> Bala.
1. How do we know if a process is user process or system process
Hi,
I have SqlServer 2000. I need to detach a database and for
this i am making sure to kill the connections to that
database. I am doing this after removing the replication
setup on this database. When i try to kill connections i
am having a cursor for the following sp id's and looping
through each of this pid and calling kill pid
ex:
Select spid, dbid from master..sysprocesses
this procedure of kill i call being in a different
database.
Now sometimes i get an error that Only user processes can
be killed when i run my kill procedure.
How do i make sure to kill only user processes on the
database and if some system process is accessing my
database i do i manage to detach my database.
Also is there any flag to check if it is a user or system
process in the sysprocesses
Regards,
Ravi
3. user process,server process,application process
4. clustered index on separate segment
5. Process ID 216:1112 owns resources that are blocking processes on Scheduler
6. Send alert on stored procedure error
7. dts cubes processing "Invalid processing option"
8. Using blk_bind for single char fields
9. Full Process does not process all the records in the Fact Table
10. Which process is faster, full process or refresh data
11. Analysis Manager failed to process all rows during cube processing
12. Background processing after incremental dimension processing
13. Cancelling OLAP processing from parent process