Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: Oracle refuses to shutdown
markp7832_at_my-deja.com wrote:
First thanks to all people contributing to solve my problem.
> I do not know the cause of you problem, but here is a sql*plus script
> that will generate the sql to terminate all connected sessions using an
> 'alter system kill session': We run this on our older VMS system to
> aid shutdown in a timely fashion. I recommend that you run this script
> in sql*plus then alter the system into restricted session before going
> into svrmgrl to do the shutdown.
Seems to be the best way to go for me. Now, how can I avoid, that
someone
attempts to connect after the old sessions were killed and before the
db is shut down? In my case this could be quite likely, since some
automated applications are running which detect a connection loss and
try to restablish the connection immediately.
Second question: is there any problem having a lot of killed sessions? Is there any session limit, where the killed sessions also account? If there is such a limit, how can the sessions effectively removed, so that they aren't listed anymore in v$session rather then displayed as KILLED?
bye
--
Sam Jordan
Received on Mon May 31 1999 - 01:45:46 CDT
![]() |
![]() |