This content has been marked as final. Show 3 replies
You may need to wait for the session to get killed.
May it would be reading undo records. Check that if it reads undo or not.
In our production environment Concurrent request "Gather Schema Stats" was running 2 days. Hence we cancelled the request.Try "alter system kill session 'SID,serial#' immediate".
Request completed as terminated status. Unfortunately the oracle session of that concurrent request went to "Killed" status. Still utilizing CPU resource.
If we try, "alter system kill session 'SID,serial#';"
it gives below message,
ERROR at line 1:
ORA-00031: session marked for kill
Could you please provide steps to kill this oracle session.Concurrent Processing - How to Find Database Session & Process Associated with a Concurrent Program Which is Currently Running. [ID 735119.1]
I did try "Alter system kill session 'sid,serial#' immediate;" but session still remained in "KILLED" status for more than 3 days.
Forcefully i killed the unix process spid from V$process. Now the session got killed and expired.
1. Obtained SID and SPID from given concurrent request id.
FROM v$session ses, v$process pro
WHERE ses.paddr = pro.addr
AND pro.spid IN (SELECT oracle_process_id
WHERE request_id = &request_id);
2. from unix prompt, killed unix process using spid obtain from above query.
#kill -9 <SPID>
Thanks for the response.