You have killed a session at the os level. Now, the session is showing "killed" in v$session but v$access is showing objects locked by this session id and v$lock shows locks held by this sid.
You may have killed the client process and there is still a shadow process for this session running. The shadow process can be tricky to identify. It may take considerable searching by the dba who is familiar with the os and database environment to identify the process.
You might look for processes with a parent pid of 1, meaning that they are owned by the system. Also, look for processes with a start time that matches the start time of the killed process.
Even though you shouldn't kill the session at the os level before killing it in Oracle, Oracle should release locks and cleanup after the session is killed at the os level. If locks are not being released, it is an indication that there are other os processes running that are associated with the session.
来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/26706/viewspace-64603/，如需转载，请注明出处，否则将追究法律责任。