(For Oracle versions that don't support execute immediate, change the procedure to use dbms_sql)Д¬reate procedure kill_your_session (in_sid in sys.v_$session. The user EXECUTING the procedure will need some way to find sid and serial# for their various sessions, to know which one to kill. In this case the UNIX command top may report the. These all steps can be done with Oracle Sql developer tool also. As a solution to the above, the solution that I like the most is to give permission through a stored procedure to which the user has permission to execute. SQL> select from dual select from dual ERROR at line 1: ORA-00028: your session has been killed. (perhaps the best option) create a packaged. Examples: (1.1) You suspect that a database session is spinning and consuming a significant amount of CPU time. In Oracle it would be the alter system privilege but this apart from doing a kill or disconnect session does a few other things so it is quite dangerous. You have a few options: ask the DBA to kill the session ask to be granted the ALTER SYSTEM privilege (which is a very poor practice) have a 'supervisor' (however defined - responsible specifically for these situations) be granted the ALTER SYSTEM. However, if the operating system process related to a terminated Oracle user session remains active, you can kill the session-related operating system. Procedure: (1) Determine the process ID (PID) of the operating system process which corresponds to the database session. This procedure will allow you to kill any session that has the same username as your current username. Kill an unwanted Oracle database session in a clean way.

'select on sys.v_$session' or 'select any table' The OWNER of the procedure will need the following privileges granted DIRECTLY, NOT via a role.

>Write a procedure that kills the relevant session(s) and grant the user

Oracle kill session privilege