Session refused to be killed

Similar Questions

• 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

• 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

• 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.

• Question on v$ session.status = KILLED

  DB version: 10.2.0,4
  Operating system: Solaris SPARC 5.10
  
  Usually, the recording of the session killed will be absent from the result of the query. But sometimes the registration for the session killed will be present when you query v$ session with continuous KILLED = STATUS. When this happens?

  I agree with Satish. As seen in the place where I work, this often happens with very large transactions. Moreover, the transaction is running with the session being ACTIVE before killed, more it will appear as people KILLED due to the CANCELLATION involved in the restoration of the large transaction. The remaining sessions returns with a status KILLED can be such a wretch where several tables can always be locked by the cancellation process.

• Kill a session caused instance bouncing

  Our database is 2 CARS db knots. The version is 10.2.0.3. The database servers are windows 2003 servers. Recently, I tried to kill a session using 'alter system kill session..' to kill a user session but caused the corresponding instance bounced. I created a TAR with Oracle and downloaded alert logs, trace files and files of $ORACLE_HOME/log / < name of the node - > /racg directory. But Oracle has not found anything to explain why the instance was restarted. He said that I may have killed an Oracle background process. My questions are:
  
  (1) can you use command 'alter system kill session..' to kill Oracle process? If you can that happen if you had killed a? Just cause the instance to stop and start?
  (2) I tried to find the session that I killed in gv$ active_session_history, but they are too old for exist. I was wondering is there anywhere I found this kind of info.
  
  Thanks a lot for your help.
  
  Shirley

  I don't think that you can kill a background session with ALTER SYSTEM:

  SQL> select * from v$version;
  
  BANNER
  ----------------------------------------------------------------
  Oracle Database 10g Express Edition Release 10.2.0.1.0 - Product
  PL/SQL Release 10.2.0.1.0 - Production
  CORE    10.2.0.1.0      Production
  TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
  NLSRTL Version 10.2.0.1.0 - Production
  
  SQL> select sid, serial#, program from v$session where program like '%SMON%';
  
         SID    SERIAL# PROGRAM
  ---------- ---------- ------------------------------
          43          1 ORACLE.EXE (SMON)
  
  SQL> alter system kill session '43,1';
  alter system kill session '43,1'
  *
  ERROR at line 1:
  ORA-00029: session is not a user session
  

  But you can always kill with a command to the operating system:

    1  select spid, osuser, s.program
    2  from v$process p , v$session s
    3  where p.addr=s.paddr
    4* and s.sid=43
  SQL> /
  
  SPID         OSUSER
  ------------ ------------------------------
  PROGRAM
  ----------------------------------------------------------------
  2620         Système
  ORACLE.EXE (SMON)
  
  SQL> exit
  Disconnected from Oracle Database 10g Express Edition Release 10.2.0.1.0 - Produ
  ction
  
  C:\>orakill 
  
  Usage:  orakill sid thread
  
    where sid    = the Oracle instance to target
          thread = the thread id of the thread to kill
  
    The thread id should be retrieved from the spid column of a query such as:
  
          select spid, osuser, s.program from
          v$process p, v$session s where p.addr=s.paddr
  
  C:\>orakill XE 2620
  
  Kill of thread id 2620 in instance XE successfully signalled.
  
  C:\>sqlplus / as sysdba
  
  SQL*Plus: Release 10.2.0.1.0 - Production on Tue Feb 23 18:47:12 2010
  
  Copyright (c) 1982, 2005, Oracle.  All rights reserved.
  
  Connected to an idle instance.
  

  -Online Forum was killed. Alert log says:

  Tue Feb 23 18:47:10 2010
  Errors in file c:\oraclexe\app\oracle\admin\xe\bdump\xe_pmon_2512.trc:
  ORA-00474: SMON process terminated with error
  
  Tue Feb 23 18:47:10 2010
  PMON: terminating instance due to error 474
  Tue Feb 23 18:47:10 2010
  Errors in file c:\oraclexe\app\oracle\admin\xe\bdump\xe_q001_3208.trc:
  ORA-00474: SMON process terminated with error
  
  Tue Feb 23 18:47:10 2010
  Errors in file c:\oraclexe\app\oracle\admin\xe\bdump\xe_ckpt_2580.trc:
  ORA-00474: SMON process terminated with error
  
  Tue Feb 23 18:47:11 2010
  Errors in file c:\oraclexe\app\oracle\admin\xe\bdump\xe_dbw0_2556.trc:
  ORA-00474: SMON process terminated with error
  
  Tue Feb 23 18:47:11 2010
  Errors in file c:\oraclexe\app\oracle\admin\xe\bdump\xe_lgwr_2572.trc:
  ORA-00474: SMON process terminated with error
  
  Tue Feb 23 18:47:12 2010
  Errors in file c:\oraclexe\app\oracle\admin\xe\bdump\xe_reco_2652.trc:
  ORA-00474: SMON process terminated with error
  
  Tue Feb 23 18:47:12 2010
  Errors in file c:\oraclexe\app\oracle\admin\xe\bdump\xe_mman_2540.trc:
  ORA-00474: SMON process terminated with error
  
  Tue Feb 23 18:47:12 2010
  Errors in file c:\oraclexe\app\oracle\admin\xe\bdump\xe_psp0_2520.trc:
  ORA-00474: SMON process terminated with error
  
  Instance terminated by PMON, pid = 2512
  

  Edited by: P. Forstmann on 23 Feb. 2010 18:50

• Oralce killed 9i session state

  Hi all
  
  Just a quick question on whether or not it is normal for a session to be marked «killed» for more than 24 hours when I interview sessions DB. It was a session hung for a long time and I had to kill him (via TOAD and he succeeded). I understand it is a restore when killed, but why am I still see it after this long?
  
  What to do next?
  THX

  SQL > col format 999999 sid
  SQL > col username format a20
  SQL > col osuser format a15
  SQL > select a.sid, a.serial #, a.username, a.osuser, b.spid
  2 session of v$, $ v process b
  3 where a.paddr = b.addr
  4 and a.sid = '& sid'
  5 order by a.sid;
  Enter the SID value: 156
  4 old: and a.sid = '& sid'
  4 News: and a.sid = '156'

  SID, SERIAL # USERNAME OSUSER SPID
  ------- ---------- -------------------- --------------- ------------
  156 354 SCOTT ASIAPAC\nkumar5 1276
  6

  C:\>orakill prod 1276

  Kill thread IDs 1276 correctly with prod pending.

  This is the name of the prod instance. serve your sid to 170 and get the SPIDS and kill him with the help of orakill

• kill session vs kill session immediate/post_transactional

  A DBA, I sometimes kill sessions in SQL * more by entering the command ' ALTER SYSTEM KILL SESSION ' xxx, xxxx '; The session ends quickly, sometimes it takes sometimes minutes for the killed session to go.
  
  When to use Enterprise Manager Grid Control to kill a session that I have to choose between a 'kill immediately' or 'transactional Message. When I kill a session by entering a command from SQL * more I do not use one of these options.
  
  I'm trying to understand the consequences of the use of the two options available via the grid control. Clause of some forum posts suggest you use IMMEDIATELY"as a last resort. According to them, he couldn't prevent a session from filling out a cancellation of the updates because the operating system process stops immediately. Read that a description of the clause POST_TRANSACTION makes me think of issueing what the command against a long query term will allow him continue to run and end the session only after the end of the SQL query. For now I avoid using one of the options of the grid control and stick to my original format in SQL * more.
  
  Could someone shed some light on the difference between killing a session with or without KILL it IMMEDIATELY or POST_TRANSACTIONAL' options?
  
  Thank you
  Bill

  Hello

  If I order, "the ALTER SYSTEM KILL SESSION ' xxx, xxxx ';

  allows you to mark a session as null and void, restore the ongoing transactions, releases all session locks and partially recovery of resources from the session. If the session is running an activity that must be completed, as the wait for a response from a remote database or rolling back a transaction, then Oracle Database expects this activity complete, mark the session as being finished and then returns control to you.

  If I order, "ALTER SYSTEM KILL SESSION ' xxx, xxxx" IMMEDIATE. "

  Specify IMMEDIATE to load the Oracle database to ongoing transactions, releases all session locks, recover session state full and immediately returns control to you. You wrote end immediately with no cancellation of updates?. This is not so, it will rollback all not updated.

  If I execute the command ' ALTER SYSTEM KILL SESSION ' xxx, xxxx "POST_TRANSACTION;"

  The POST_TRANSACTION parameter allows operations to be completed before the session is disconnected. If the session has no current transaction, then this clause has the same effect as to KILL SESSION.

  Reference:-[http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_2013.htm#SQLRF00902]

  HTH
  Anand

• Oracle 10 g 2: hanging of session after "select regexp_like.

  Hello

  We use an Oracle database 10 g 2 (10.2.0.5.0) installed on a Windows Server 2003 (x 64).

  Yesterday a simple query (select * from table where regexp_like (upper (filename), ' ^ [aA - zZ] {0,1} * $')) has been started but never came back. Any other question on the same table

  runs without any problem. Trying to kill the session with "alter system kill session...". "the session has maintained the State of being killed (currently for over 24 hrs.).

  Seems quite odd to me since Oracle has no need to restore anything - ist was just the select which was performed at this session. The fort of event wait this session

  is "SQL * Net message from client. However rebooting the computer Client did not help either. The database seems to be in good shape - at least that does not session

  nothing, don't. Rebound of the database is not possible - but certainly will solve this problem.

  Any ideas or maybe a bug known?

  Rgds

  J.

  Good question, system administrator Ask, they should have a windows administration tool (I don't know the name) which will allow them to find all threads of a process Oracle.exe.

  I had a similar problem and windows administrator was able to follow this thread and kill for me.

  Pradeep

• How to check constantly vCenter logon session?

  I need a reliable way to check to see if my vCenter session is active. I am aware of the $global: DefaultVIServer.IsConnected, but no one knows how many times which is updated from $true to $false if vCenter fails? I performed a test fast and connected to a vCenter, valid IsConnected = $true, stopped the vCenter services and it took several minutes before he ever upgrade IsConnected = $false. I even ran a few basic cmds (Get - VM, Get-Cluster, etc.) trying to see if that would update IsConnected = $false, but I had no luck.

  I have a very long interview script that runs throughout the night and I need to be able to check the status of my session of vCenter repeatedly during the maintenance script. My first thoughts were to build a function around the State of IsConnected, but based on my tests and the time it took to update, I'm not sure this is the correct path.

  Does anyone have a better suggestion on checking the status of my session of vCenter or know a way to force IsConnected to update immediately after the session of vCenter is killed?

  This will tell you if the session is connected or disconnected.

  $si = get-view ServiceInstance

  $sessMgr is get-view-Id $si. Content.SessionManager

  {while ($true)}

  {if($sessMgr.CurrentSession)}

  Write-Output "$(Get-Date-Format ' hh) connected Session.

  }

  else {}

  Write-Output "$(Get-Date-Format ' hh) disconnected Session.

  }

  sleep 1

  $sessMgr.UpdateViewData ('CurrentSession')

  }

• Can we get the DB session ID when we log into our own application

  Hello

  I use my local DB with HR/hr and created a table for details of the user.
  Each time running my application (login page is the default page), user enters the USER name and PASSWORD. After you have posted I am allowing it on the next page Jspx have delimited taskflow (having jsff).

  In all the jsff fragments, I have a close button session and whenever the user selects it, I need to make the sign out.actually I was navigate to empty from now page. I'm not saving login details in DB after the connection. Thus, whenever the user clicks the back button, the page navigates to the previously provided login page username and PASSWORD.

  So I would like to kill the session when the user logoff button clicked. Please help if we can do it.

  Is there a provision like get the session DB ID and kill him when ever he logs off or disconnect.

  Kind regards

  Krishna KM.

  In this case, you get disconnected and you killed at the session. You can do this by using a bean method that you call from your button. Inside you get the session, disable it and go to any other page, g .e, see again you ot your login page. A sample for this: http://dba-adf.blogspot.de/2010/02/adf-security-in-oracle-adf-and-session.html

  Timo

• How to run in the background need to be killed

  Hi Experts,

  I have a problem as below.

  We are conducting a procedure that calls the procedure who hear the call of the child through the UI which is built in .net, procedures based on the parameters, he will call many times, we went and inserts data into tables.

  Because of the issue of tablespace we are interrupted the session, but the procedure runs in the background.

  Can you please how to abort the procedure at the bottom.

  Thanks in advance...

  Run a select statement on V$ SESSION and identify the sessions that must be killed and use the command ALTER SYSTEM (KILL SESSION) and kill the session.

• How to kill a job RMAN?

  I'm under 11.2.0.2 on Solaris and want to know what is the right way to kill a RMAN backup task that has already begun?
  
  This looks like something as simple as: ps - ef | grep rman, then, kill-9 the two processes of rman. Right? Fake!
  

  $ /home/oracle>ps -ef |grep rman
    oracle 27493 10700   0 14:08:44 pts/1       0:00 /bin/ksh rman_bkup_db_lvl0.ksh MYDB
    oracle 27524 11155   0 14:09:00 pts/3       0:00 grep rman
    oracle 27508 27493   0 14:08:44 pts/1       0:01 rman target /
  
  $ /home/oracle>kill -9 27493 27508
  
  $ /home/oracle>ps -ef |grep rman
    oracle 27552 11155   0 14:09:56 pts/3       0:00 grep rman

  RMAN process seems to be killed.
  But looking in the database, the process is still ongoing.
  

  SQL> select username, program from v$session where username = 'SYS';
  
  USERNAME                 PROGRAM
  ------------------------ ------------------------------------------------
  SYS                      rman@myhost (TNS V1-V3)
  SYS                      rman@myhost(TNS V1-V3)
  SYS                      OMS
  SYS                      sqlplus@myhost (TNS V1-V3)
  SYS                      rman@myhost (TNS V1-V3)
  
  (and several others from previous runs that I killed off at the OS level)

  When I looked in OEM, I could see a pic of the e/s sys user and the I/O and the processes are the RMAN.
  
  I found a web page that says if I choose to leave and join V$ SESSION_WAIT, V$ SESSION and V$ PROCESS
  WHERE s.client_info LIKE '% rman', I get the SID and serial no to kill the sessions in the database.
  
  Is there an easier way to do that? In my case, I ended up using Toad and killed all RMAN process, but then I hit 11872103 bug which left status showing running and causing a performance problem during resync'ing of the catalogue.

  Hello

  Follow the documentation on this subject:

  Termination of an RMAN command
  http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmtroub.htm#BRADV176

  Any doubt post here.

  RMAN utility is only a Client who has opened on the Oracle server. RMAN doesn't create or read the files in data/backupset but is no Oracle server... RMAN will manage and control.
  If you kill only the RMAN Client process, it is not guaranteed on the Oracle Server session will also be killed. So, if you want to stop RMAN job you have to kill the session not RMAN Client.

  Kind regards
  Levi Pereira

  Published by: Levi Pereira on December 11, 2012 14:26

• script for the murder of session

  Hello
  I prepare a script for the murder of session and I use the following command to generate the script for large number of users. The syntax for the murder of the session is ALTER SYSTEM KILL SESSION * "SID, SERIAL #" * IMMEDIATE. I want my output with SID, SERIAL # values within the single quots *('SID,SERIAL#') *. can someone help me on this?
  
  
  Select "ALTER SYSTEM KILL SESSION ' |" SID | «, » || SERIES # | ' IMMEDIATE '. « ; » FROM V$ SESSION WHERE BLOCKING_SESSION IS NOT NULL
  
  
  
  
  Thanks in advance
  
  Published by: 793097 on December 14, 2010 05:53

  select 'ALTER SYSTEM KILL SESSION '''||SID||','||SERIAL#||''' IMMEDIATE'||';' FROM V$SESSION WHERE BLOCKING_SESSION IS NOT NULL
  

  Nicolas.

• To end a Session

  Anyone know of a way to finish a session (AKA forces a user to logout) is that the same username is used to connect to somewhere else? I have an application where if a user name is used to connect two times for the same application that the user AKA has two open sessions already open session must be deleted.

  When a user opens a session, it records it id sessionid and user to a table in the database, so I have the id of the session session, I want to kill.

  Thanks in advance for any help. Let me know if it still sounds confusing.

  Yes, the code I showed in the other post.

  sessionKill.cfm

  Some files somewhere detects a user has been saved twice

  As I said, this does not actually remove the session from the memory of ColdFusion.  That cannot be done without mucking around with the serviceFactory.  But the session will have no data if a user where there to return they should not be connected or have all recorded data.