why DB file read is still active after the session was killed?
ADanielJun 8 2012 — edited Jun 12 2012Hi,
I have a query that is doing only read only select (no select for update) on a quite big table (500millions rows). The result should return a few million rows (1-10 millions) because is not correctly written.
I killed all the sessions opened by the user that started the query, but after 3 hours, it is still running.
I don't get it. It is a read. There is no rollback data that needs to be rolled back, there is no (low) redo generation because of it.
There are some sorts done in this query.
So, why after I am killing a query that is readonly, the process still runs for a long long time?
It's not the first time I am faced with this issue.
Any ideas?
Thank you,
Daniel