kill session vs kill session immediate/post_transactional

Similar Questions

• Why kill him the session is not immediate

  Hello
  I'm on 8.1.7.4 company
  I have a loop that takes hours
  When I kill the sesison running this loop
  I can still see the loop is still to work (selects, inserts,...)
  and I have to wait a time loooooooong
  
  Why kill the session is not immediate, not to make it faster?
  
  Thank you

  Take a look at this... He talks to kill sessions using the ORAKILL utility...
  http://articles.TechRepublic.com.com/5100-10878_11-5224960.html

  Concerning
  Z.K.

• Can't kill session 11g WINDOWS 2008

  Hoping someone can tell me how to kill a job that won't die :)
  
  We had network maintenance during the weekend that interrupted the connection between our server and the database. It caused a lot of jobs to get stuck. I could kill all but a job. The last task seems to be busy reading, but the session info does not appear any sql.
  
  BOTH OF THE COMMANDS RETURN ERROR below: "ora-00030: user session id does not exist ' and info session continues to say"active">
  ALTER SYSTEM KILL SESSION '8,46534' immediate;
  change the session disconnect system '008,46534' post_transaction;
  
  
  
  Any idea what I can do to kill this work? Startup of the database is not a possibilities.
  
  Thank you!
  Kathie

  you try to kill a job, not a session, right?

  Check this box:
  http://levicorp.com/2009/05/22/how-to-kill-the-running-job/
  http://www.Pythian.com/blog/killing-an-Oracle-job-dead/

• delete the entry for killed / sniped v$ session meeting

  Hi all
  In our database (11.2.0.1.0) of production running on windows server 2008 several client session list inactive last hour of 4-5 and I want to kill this session because that all sessions are dedicated to do this so I've created a set of resource plan his idle time after certain interval session status shows killed , but he is not removing of session entries $ v but our customer demand is there must be clear v $ session so for this I used command BACK utility taskkill to kill the particular operating system process, so I want to know what is the smart way to do it.

  We're talking about behavior, not a problem.

  In a dedicated server environment when the session is killed and the rollback ends the process so a join between v$ session and v$ process will fail. The v$ entered session also disappears usually fairly quickly, although I've seen cases where the v$ session entrance hung around until the instance has rebounded. But normally the Oracle will overlap the v$ session entry with a new session using the same sid but another serial # seconds on a busy system.

  Mark @ http://dbaspot.com/oracle-server/40419-killed-sessions.html

  Doc-id 1023442.6 MetaLink is also something confirm it.

  Also see link below and the last reply by Mr. Braj Kishore Mahto.
  http://dbaforums.org/Oracle/index.php?showtopic=3039

  Concerning
  Girish Sharma

  Published by: Girish Sharma on November 21, 2012 17:35

  So what is preferable in this respect:

  ALTER SYSTEM DISCONNECT SESSION

  The ALTER SYSTEM DISCONNECT SESSION syntax is an alternative method for killing Oracle sessions. Unlike the KILL SESSION command requesting the session to kill himself, the DISCONNECT SESSION command kill the dedicated server process (or virtual circuit when the shared use of Sever), equivalent to kill the operating system server process. The basic syntax is similar to the KILL command SESSION with the addition of the POST_TRANSACTION clause. The SID values and serial of the meeting concerned can be replaced in one of the following instructions.

  SQL > ALTER SYSTEM DISCONNECT SESSION ' sid, serial # ' POST_TRANSACTION;
  SQL > ALTER SYSTEM DISCONNECT SESSION ' sid, serial # ' IMMEDIATE;

  http://www.Oracle-base.com/articles/Misc/killing-Oracle-sessions.php#disconnect_session

• Kill the Session procedure file

  Hello

  I want to develop a process where the user can shoot session by themselves.

  Currently I use the following script to kill all idle sessions.

  If I try to create a procedure and pass in the form, it gives me an error

  EXECUTE IMMEDIATE does not work.

  Set serveroutput on

  declare

  sqlStmt VARCHAR2 (1000);

  BEGIN

  For x in (SELECT SID, SERIAL # FROM V$ SESSION WHERE STATUS = 'INACTIVE' AND last_call_et > 300) loop

  sqlStmt: = ' EDIT the SYSTEM KILL SESSION "' | X.SId | «, » || X.Serial # | " ' ;

  dbms_output.put_line (sqlStmt);

  EXECUTE IMMEDIATE sqlStmt;

  End loop;

  end;

  Sandy

  Dear SPathak ,

  Try to add IMMEDIATE too in the KILL statement. So the code will be

  declare
       sqlStmt VARCHAR2(1000);
  BEGIN
       For x in (SELECT SID,SERIAL# FROM V$SESSION WHERE STATUS='INACTIVE' AND last_call_et > 300) loop
            sqlStmt := 'ALTER SYSTEM KILL SESSION ''' || X.SId || ',' || X.Serial# || ''' IMMEDIATE' ;
            dbms_output.put_line( sqlStmt );
            EXECUTE IMMEDIATE sqlStmt;
       End loop;
  end;
  

  Manu.

• How to kill the session running from work processes

  How to kill the session work processes running... What is the process to be programmed

  BEGIN
  FOR c IN (
  SELECT s.sid,
  s.serial#
  FROM v$session s
  WHERE s.username = 'your_user_name'
  )
  LOOP
  EXECUTE IMMEDIATE 'alter system kill session ''' ||
  c.sid || ',' || c.serial# || '''';
  END LOOP;
END;

• session is not killed properly

  I use oracle 10g (10.2.0.1) in Redhat Ent Linux 5.0.

  In my production database, one of my session which is connected thorugh 'TOAD' program is hanged.

  I kill this session several times but not removed from the session and it shows the status is 'DEAD '.

  Here is the result:

  SQL > select username sid, serial #, session state $ v where status = 'KILLED ';

  USERNAME SID SERIAL # STATUS

  ------------------------------ ---------- ---------- --------

  1860 37381 KILLED DBPROD

  SQL > alter system kill session '1860,37381';

  alter system kill session ' 1860,37381'

  *

  ERROR on line 1:

  ORA-00031: session marked for kill

  SQL > alter system kill session '1860,37381' immediate;

  alter system kill session '1860,37381' immediate

  *

  ERROR on line 1:

  ORA-00031: session marked for kill

  Also during the session to kill, there is no show message in the log file of the alerts associated with the kill command.

  Now, please help me how I can fix this without closing the database.

  EDIT the SYSTEM KILL SESSION does not remove the session.  The session dies only when the user actually tries another SQL operation and is thrown a mistake - that is to say when Oracle kills the process.

  The other option is to use an OS command to kill the server process - but you need to know how to do this and identify the right process to kill (assuming not shared server and dedicated server connections).

  Hemant K Collette

• kill all sessions owned by a user

  
  Hi guys

  can someone help me with the script to kill all sessions belong scott username in a database.

  Thank you all in advance

  Hello

  There you go

  create or replace procedure kill_sessions(p_username varchar2) is
  begin
    for rec in (select 'ALTER SYSTEM KILL SESSION ''' || sid || ', ' || serial# || '''' txt from v$session where username=p_username) loop
        execute immediate rec.txt;
     end loop;
  end;
  /
  

  Best regards

  Nikolai

• Killed the remaining sessions in the session $ v

  Hello
  
  There are 42 sessions that are KILLED but still present in the view v$ session. v$ Resource_limit must keep 300 sessions. My question is: are these sessions killed count for example if session $ v shows 250 lines and 50 are marked Killed. 200 sessions will be counted or 250?
  
  Secondly, how can I KILL all open or multiple sessions or find them at the level of the Unix operating system which process id to kill at the level of the OS also?
  

  select sid,serial#,osuser from v$session where status='KILLED';
  
         SID    SERIAL# OSUSER                                                       
  ---------- ---------- ---------------
       56      8542 SYSTEM     
  - - 
  42 rows selected

  Thank you very much in advance.
  
  Concerning

  Is it possible that I have kill all sessions that are marked as being KILLED to CHANGE the SYSTEM COMMAND?

  No such statement available, you have to kill one by one with alter system kill session command but you can generate all the cmd like

  select 'alter system kill session ' || '''' || sid || ',' || serial# || '''' || ' immediate;' from v$session
  where status='KILLED';
  

  There is a PROCEDURE that is created for the normal user to kill user sessions

  put Word IMMEDIATE in alter system kill command inside the procedure.

• Why DB read file is still active after that the session was killed?

  Hello
  
  I have a query which is only select read only (no selection for update) on a big enough table (lines 500millions). The result must return a few million rows (1-10 million), because it is not properly written.
  
  I killed all the sessions opened by the user who started the application, but after 3 hours, it is still ongoing.
  
  I don't understand. It's a read. There is no data restoration that must be set aside, there is no generation of redo (low) because of this.
  There are a few kinds made in this query.
  
  So, why after that I'm killing a query that is read-only, the process runs for a very long time?
  
  It is not the first time I'm facing this problem.
  
  Any ideas?
  
  Thank you
  Daniel

  >
  I killed all the sessions opened by the user who started the application, but after 3 hours, it is still ongoing.
  >
  Have Yes - but you used the IMMEDIATE clause to kill HER?
  >
  IMMEDIATE specify IMMEDIATE load the Oracle database to ongoing transactions, releases all session locks, recover session state full and immediately returns control to you.
  >
  If you really want the process completed rather than simply "marked" termination then use DISCONNECT SESSION with the IMMEDIATE clause

  See the "Clause of DISCONNECT SESSION" in the doc of the SQL language
  http://docs.Oracle.com/CD/B28359_01/server.111/b28286/statements_2013.htm
  >
  Use the DISCONNECT SESSION clause to disconnect the current session to destroy the dedicated server process (or virtual circuit if the connection was made through a shared server).
  . . .
  The IMMEDIATE environment disconnects the session and retrieves the status of entire session immediately, without waiting for open transactions to complete.
  >
  View the results of the use of DISCONNECTION

• alter system kill session

  Hello
  
  While killing a session, I get a message like
  
  QL > alter system kill session '802,30515' immediate;
  alter system kill session '802,30515' immediate
  *
  ERROR on line 1:
  ORA-00031: session marked for kill
  
  I checked after a few hours again, I get the sid and the n serial form v$ session
  
  
  but the status of the user of the user is as 'dead '.
  
  SQL > select user name, session status $ v where sid = 802;
  
  STATUS OF USER NAME
  ------------------------------ --------
  APPS KILLED
  
  
  If the session was killed or not?
  
  Thank you
  Vijay

  887400 wrote:
  Its Linux X 86 64-bit

  But for some sessions, they will be killed immediately after alter system kill session command.,.

  but in this case it is not end immediately?

  What could be the cause?

  Internal Oracle session remains as long as the remains of operating system processes.

  Kill - 9

  Since you have already issued ALTER SYSTEM KILL SESSION
  You can't get the process ID of the Oracle's OS.

  You can associate up to the session Oracle with OS time as evidenced by time of CONNECTION
  ps - ef | LOCAL grep

• Kill several session

  Hello
  
  There are 100 sessions are active in the database, which is the best way to kill all the session using a single query.

  is it possible or not?

  Yes, with a bit of Pl/Sql, something like this (connected as SYS)

  SQL> declare
    2     str varchar2(100);
    3  begin
    4     for S in (select sid,serial# from v$session where username is not null
    5         and username != 'SYS')
    6     loop
    7         str := 'alter system kill session '||chr(39)||S.sid||','||S.serial#||chr(39);
    8         execute immediate str;
    9     end loop;
   10  end;
  

• Why can't I kill this session?

  DB version: 10.2.0.4
  Operating system: Solaris SPARC (5.10)
  Number of nodes of CARS: 2
  
  
  
  I wanted to kill the session that was connected to the Instance 2 below.
  So, I first connected to instance1 tried running the command below.
  
  
  -Connected to Instance1

  SQL:orcl1 > ALTER SYSTEM KILL SESSION '586,53926,@2' IMMEDIATE;
  ALTER SYSTEM KILL SESSION '586,53926,@2' IMMEDIATE
  *
  ERROR at line 1:
  ORA-00026: missing or invalid session ID

  Tried running of instance2 and succeeded after removing the part of ID of Instance of KILL command
  
  -Connected on Instance2 from the

  SQL:orcl2 > ALTER SYSTEM KILL SESSION '586,53926,@2' IMMEDIATE;
  ALTER SYSTEM KILL SESSION '586,53926,@2' IMMEDIATE
  *
  ERROR at line 1:
  ORA-00026: missing or invalid session ID
  
  
  SQL:orcl2 > ALTER SYSTEM KILL SESSION '586,53926' immediate;
  
  System altered.

  I can't kill a session connected to Instance2 from the 1st Instance using the syntax
  

  ALTER SYSTEM KILL SESSION 'sid,serial,@inst_id' IMMEDIATE;

  ?

  Hello

  session function kill via. another instance introduced with 11 GR 1 material.

  If this does not work in 10.2

  Concerning
  Sebastian

• How to kill a session by the non privileged user

  Hello
  
  I use the oracle 10.2.0.3 version.
  
  I have to give privileged kill session to a user non-preferred, below 2 ways, I know that this can be done with.
  
  1. by giving change the system to this user privilege.
  
  2. by creating a procedure in any user with DBA privileges, which has the statement to execute immediate change the system kill session & by granting execute this procedure to this user.
  
  Apart from the above two ways, I heard that there is a procedure/priviledge etc. also well integrated into Oracle. Which can be granted to individual users.
  
  No idea if there is something of this kind?
  
  
  Thanks in advance.
  
  Best regards
  Oratest

  Each session has a partner gets server process created in OS that Oracle creates (the setting of the dedicated server), so if you kill even the session in Oracle and the corresponding operating system process is not killed, then the session is marked for KILL and do not get killed instantly or marked as snipped.

  Also, there is no explicit privilege in Oracle to grant only the ability to kill session, you will need to ALTER SYSTEM privilege and, of course, it gives you much more capacity than to simply kill the session and therefore impossible to give all users who does not keep a database.

• Script to kill the blocking sessions

  We use Oracle 10. We have a database of test used only for training and I need to give to the teacher the ability to kill all sessions blocking when a block continues
  the entire class.
  My idea was to create a simple form on our Oracle containing just a single menu-button when you press on would trigger the script. Press the key
  to kill each session blocking. I have no idea on how to write a script of this nature. Would appreciate any advice.
  Kind regards
  Sandy

  You can use something like this

  SQL> DECLARE
    2  CURSOR c IS
    3  SELECT c.owner,
    4        c.object_name,
    5        c.object_type,
    6        b.SID,
    7        b.serial#,
    8        b.status,
    9        b.osuser,
   10        b.machine
   11   FROM v$locked_object a, v$session b, dba_objects c
   12   WHERE b.SID = a.session_id AND a.object_id = c.object_id
   13   and c.object_name in ('JSW_CRM_C_HR_COIL_INFO','T_SPCL_BARCODE_CRS2');
   14  c_row c%ROWTYPE;
   15  l_sql VARCHAR2(100);
   16  BEGIN
   17  OPEN c;
   18  LOOP
   19  FETCH c INTO c_row;
   20  EXIT WHEN c%NOTFOUND;
   21  l_sql := 'alter system kill session '''||c_row.SID||','||c_row.serial#||'''';
   22  EXECUTE IMMEDIATE l_sql;
   23  END LOOP;
   24  CLOSE c;
   25  END;
   26  / 
  

  Be sure to use your own SQL statement in the CURSOR!