Very Computer

by **Sigrid Staudt** » Tue, 02 Dec 1997 04:00:00

In the database a session is running that
runs and runs and blockade ressources, locks tables
and so on. The session is never ending.
It is not possible to kill this session
with the alter system kill session command. The
session is only marked for kill. The only way to
terminate the session is shutting down the database.
Knows anywhere another way to solve this problem?

Bye...Sigrid

by **Billy Verreynn** » Wed, 03 Dec 1997 04:00:00

>It is not possible to kill this session
>with the alter system kill session command. The
>session is only marked for kill. The only way to
>terminate the session is shutting down the database.
>Knows anywhere another way to solve this problem?

You can make sure that the session is dead by looking for the process for
that session in v$process. The Unix PID is in the column SPID. If that Unix
process is still running it means that the session/process has not been
killed. You can then probably just kill that Unix process.

But I think that an Oracle session marked as killed is actually killed and
do not have a corresponding active v$process.

regards,
Billy

by **hans-peter sloo** » Wed, 03 Dec 1997 04:00:00

I think that this session will go away eventually automatically.
Probably recovery needs to be done.

Quote:> In the database a session is running that
> runs and runs and blockade ressources, locks tables
> and so on. The session is never ending.
> It is not possible to kill this session
> with the alter system kill session command. The
> session is only marked for kill. The only way to
> terminate the session is shutting down the database.
> Knows anywhere another way to solve this problem?

> Bye...Sigrid

by **Joseph Sumalba** » Wed, 03 Dec 1997 04:00:00

> I think that this session will go away eventually automatically.
> Probably recovery needs to be done.

I concur .... Once you killed the session , what the instace
does is make sure to rollback all the uncommitted transaction
that had been done but not committed . This will take sometime
depending on how long the transactions and how much data has
been changed, then once the rollback has been done , then the
client tried to contact oracle again using the same session that
will be the time that sqlnet will inform the client that the
session has been killed and the marked for killed or killed will
be removed from your system tables .

> > In the database a session is running that
> > runs and runs and blockade ressources, locks tables
> > and so on. The session is never ending.
> > It is not possible to kill this session
> > with the alter system kill session command. The
> > session is only marked for kill. The only way to
> > terminate the session is shutting down the database.
> > Knows anywhere another way to solve this problem?

> > Bye...Sigrid

--
================================================================
============================
| Joseph Sumalbag
|
| Oracle DBA
|
|
|
| The opinions expressed above are my own and doesn't
necessarily |
|reflect the opinion of any of my client company or my employer.
|
================================================================
============================

by **David Russel** » Wed, 03 Dec 1997 04:00:00

Because Oracle can not drop open network sockets, you should make sure that
you have setup Dead Connection Detection (sqlnet.ora
(sqlnet.expire_time=...)).

Regards
David Russell

by **Greg Vitetzaki** » Thu, 04 Dec 1997 04:00:00

I agree with all the above menthioned information...Just to add. I've
noticed when you kill
a session it will stay marked a killed on the Server as long as the process
thread on the client
machine is still active.

Simply kill the process on the client machine or restart the client. It
should shortly after
remove the userid from the v$session view.

Greg Vitetzakis.

> > I think that this session will go away eventually automatically.
> > Probably recovery needs to be done.

> I concur .... Once you killed the session , what the instace
> does is make sure to rollback all the uncommitted transaction
> that had been done but not committed . This will take sometime
> depending on how long the transactions and how much data has
> been changed, then once the rollback has been done , then the
> client tried to contact oracle again using the same session that
> will be the time that sqlnet will inform the client that the
> session has been killed and the marked for killed or killed will
> be removed from your system tables .

> > > In the database a session is running that
> > > runs and runs and blockade ressources, locks tables
> > > and so on. The session is never ending.
> > > It is not possible to kill this session
> > > with the alter system kill session command. The
> > > session is only marked for kill. The only way to
> > > terminate the session is shutting down the database.
> > > Knows anywhere another way to solve this problem?

> > > Bye...Sigrid

> --
> ================================================================
> ============================
> | Joseph Sumalbag
> |
> | Oracle DBA
> |
> |
> |
> | The opinions expressed above are my own and doesn't
> necessarily |
> |reflect the opinion of any of my client company or my employer.
> |
> ================================================================
> ============================

by **Sigrid Staudt** » Thu, 04 Dec 1997 04:00:00

> Because Oracle can not drop open network sockets, you should make sure that
> you have setup Dead Connection Detection (sqlnet.ora
> (sqlnet.expire_time=...)).

Do you mean the sqlnet.ora at the server or the client ?

With regards

Sigrid

Very Computer

how to kill a session that marked for kill

how to kill a session that marked for kill

how to kill a session that marked for kill

how to kill a session that marked for kill

how to kill a session that marked for kill

how to kill a session that marked for kill

how to kill a session that marked for kill

how to kill a session that marked for kill