I have two sessions in a database that are exhibiting high CPU an have been for over a week. I killed the sessions yesterday, but they are still present in v$session and still consuming a lot of CPU.
I've tried both “alter system kill session ‘X,Y’ immediate" and "alter system disconnect session ‘X,Y’ immediate” to no avail. They're not transactions doing a lot of rollback or anything.
The sql_id in v$session is null. The prev_sql_id refers to a select statement that parsed out some JSON and XML data. The event column liksts “SQL*Net more data from client”, but the SQL Developer client has long since disconnected.
As I recall, killing the process at the OS level can have bad consequences for the database, so I've avoided that. I'm at a loss for what to do next, any suggestions?