Killed sessions still appear in V$SESSION

[jdemmi]

It is my understanding that KILLED sessions will appear in v$session until the session user tries to use the session again.

But here's my problem. The user, in my case, has long since shut down his PC. He will NEVER attempt to use that session ID again.

So, when will these sessions drop out of v$session? Only when the DB is bounced?

If you're wondering how these were created...

A user connects to Discoverer (web) viewer and runs some queries. He exports at l least 1 to Excel Web quwery format and then logouts out of the viewer (this session is closed). He then opens the Excel web query and refreshes the data -- the sheet calls Discoverer and passes his credentials to the server and the data is returned. The user then closed the sheet and is done. The session stays as INACTIVE forever? (best we can tell) and then, when killed still remains in v$session but is marked (status) as killed.

Which raises another question...is there a session timeout setting on the Discoverer viewer side that we're not aware of?

-- Jason
"It's Just Ones and Zeros

 

[SantaMufasa]

Frankly, Jason, this "housekeeping" problem is an annoyance that Oracle hasn't addressed for as long as I have worked with Oracle (i.e., since 1988). This is a particular problem if the absent(minded) user of the killed session had locked one or more rows in one or more tables before they abandoned their session (and the lock doesn't disappear until the session disappears). The only way that I have found to remove their session is to bounce the database.

If anyone has a more graceful work around, then I'd love to see it (and award a well-deserved

!)

Mufasa
(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]
“Beware of those that seek to protect you from harm or risk. The cost will be your freedoms and your liberty.”

 

[jdemmi]

Thanks -- you confirmed what I had hoped wasn't true.

-- Jason
"It's Just Ones and Zeros

 

[Turkbear]

Hi,
Sorry to say this, but I have been working with Oracle since the SCO Unix days and that problem ( although it is rarely a serious problem in a well-sized installation) has never been solved, as far as I can tell.





To Paraphrase:"The Help you get is proportional to the Help you give.."