Regarding kill session

Hello Everybody,
I am new to Oracle. I have few questions regarding session kill.
1)Does “killed” session consume any system resources like RAM, CPU?
2)Whether one should kill the process rather than the session?
3) Does ALTER SYSTEM KILL SESSION command kill both user session and server process?
With Regards.

1)Does “killed” session consume any system resources like RAM, CPU? Killed Status In v$Session Indicates PMON is too busy to clean up.
You could refer to
http://www.oracle-base.com/articles/misc/KillingOracleSessions.php
2)Whether one should kill the process rather than the session?Refer to
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:4974573906087
3) Does ALTER SYSTEM KILL SESSION command kill both user session and server process?session is not a process, a process is not a session.
please refer to Tom Link.

Similar Messages

How to find the killed session and machine name

Hi,
At the time of batch job running .somebody killed that session .let me know how to find out the particular user name db level or oslevel .from which machine they killed how to find out at OS level . but when i have set the audit_trail=os only SYSDBA user activities are audited not the other user activities.
The server is AIX and db version 11i .provide the query for finding or os level .
thanks,
DBC.
Edited by: dbc001 on Mar 26, 2013 9:48 PM

Are you sure that somebosy had killed the session? Did you get any error regarding kill session? Is there any other errors you can see in logs?its suspect only....
>
How that job was scheduled?...actually we have lot of source systems, from those source system we are getting the data into BI machine, by using BI apps team process data and trigger load jobs @db
Apps team is having database unix logins aswell as db logins to process their requests.
Your OS admin can check the history upto some extent? Check if he has auditing enabled at OS level?we are in the process of checking with OS sysadmin.
upto now we didnt got any clue....apps team successfully re-ran failed job.

Regarding KILLING the session

Hi..
How to kill the session from the SQL * Plus ...please tell me anyone
regards
Yashavanth

ALTER SYSTEM command. Refer to the [url http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_2013.htm#i2053602]Oracle® Database SQL Reference guide.
However...
1. This needs a SYSDBA priv. End-user and application schemas must NEVER be able to use the ALTER SYSTEM command directly. That will be a very serious and utterly silly security risk. (the type that can get you fired in the corporate world)
2. Killing sessions is an exception. This should not be the run-of-the-mill thing. Why do you need to kill sessions from SQL*Plus? Are you sure that this is the best response to the problem you have? What is that problem? maybe we can offer better alternatives.

Regarding Alter System Kill Session

Hi Guys,
I have to do db refresh from the build .For this I have to kill the sessions and drop the users and recreate the users with the latest build.As the application is running and there are some idle sessions, I have to kill the sessions and drop the users for that I am using a code as below
DECLARE
v_alt_stmt VARCHAR2(1000) := 'ALTER SYSTEM KILL SESSION ''';
v_kill_stmt VARCHAR2(1000);
CURSOR cur_session IS
SELECT s.type type,
s.sid sid,
s.serial# srl_no,
s.username user_name,
s.PROGRAM prog_name
FROM v$session s JOIN gv$process p ON p.addr = s.paddr and s.type='USER';
BEGIN
EXECUTE IMMEDIATE 'ALTER SYSTEM ENABLE RESTRICTED SESSION';
DBMS_OUTPUT.PUT_LINE('The Session has been put in the restricted mode');
FOR v_cur_ssn IN cur_session
LOOP
BEGIN
v_kill_stmt := v_alt_stmt || v_cur_ssn.sid || ',' || v_cur_ssn.srl_no || '''';
DBMS_OUTPUT.PUT_LINE(v_kill_stmt);
EXECUTE IMMEDIATE v_kill_stmt;
EXCEPTION
WHEN others THEN
-- DBMS_OUTPUT.PUT_LINE('The current sessions sid is ' || v_cur_ssn.sid || ' and the srl no is ' || v_cur_ssn.srl_no || ' can not be killed');
END;
END LOOP;
EXECUTE IMMEDIATE 'ALTER SYSTEM DISABLE RESTRICTED SESSION';
DBMS_OUTPUT.PUT_LINE('The restricted mode of the system has been removed');
END;
But sometimes after killing the sessions there are some os processes are going on,to avoid that I have to use 'ALTER SYSTEM DISCONNECT SESSION ''' and 'MMEDIATE' it is workig fine .
Can Any one tell me the logical difference between kill sessions and disconnect
Any information will be highly appreciated.
Thanks in advance
Prafulla

>
Can Any one tell me the logical difference between kill sessions and disconnect
>
Disconnect can be used to disconnect immediately without waiting for any ongoing transactions to complete and recovers all session resousrces.
Kill rolls back ongoing transactions and partially recovers session resources.
Kill is simiilar to SHUTDOWN IMMEDIATE while disconnect is more like SHUTDOWN ABORT.
See DISCONNECT SESSION Clause in the SQL Language doc
http://docs.oracle.com/cd/B28359_01/server.111/b28286/statements_2013.htm
>
Use the DISCONNECT SESSION clause to disconnect the current session by destroying the dedicated server process (or virtual circuit if the connection was made by way of a Shared Sever).
•The IMMEDIATE setting disconnects the session and recovers the entire session state immediately, without waiting for ongoing transactions to complete.
>
And KILL SESSION in the same doc next section
>
The KILL SESSION clause lets you mark a session as terminated, roll back ongoing transactions, release all session locks, and partially recover session resources.
IMMEDIATE Specify IMMEDIATE to instruct Oracle Database to roll back ongoing transactions, release all session locks, recover the entire session state, and return control to you immediately.

Regarding error in alert -- immediate kill session

Dear Gurus
os - linux4.5
oracle -10.2.0.4
i have an error in my alert log file for node 2 as below(i m posting here main text what i found)
Immediate Kill Session#: 73, Serial#: 39455
Immediate Kill Session: sess: 0x402337f0ca0 OS pid: 17058
Immediate Kill Session#: 74, Serial#: 38391
Immediate Kill Session: sess: 0x402337f2208 OS pid: 25083
Immediate Kill Session#: 76, Serial#: 6725
Immediate Kill Session: sess: 0x40233833af0 OS pid: 17018
Immediate Kill Session#: 128, Serial#: 54171
Immediate Kill Session: sess: 0x4023383a5f8 OS pid: 25861
Sun Aug 14 14:25:31 2011
Process OS id : 25861 alive after kill
Errors in file /u01/app/oracle/admin/prod/udump/prod_ora_8179.trc
Immediate Kill Session: sess: 0x40233a3c1f8 OS pid: 28900
Immediate Kill Session#: 534, Serial#: 12002
Immediate Kill Session: sess: 0x40233a598e8 OS pid: 16102
Sun Aug 14 14:35:30 2011
ALTER SYSTEM SET service_names='prod' SCOPE=MEMORY SID='prod2';
Sun Aug 14 21:00:50 2011
Thread 2 advanced to log sequence 3684 (LGWR switch)
Current log# 3 seq# 3684 mem# 0: +RLOG_GROUP/prod/redo03.log
Mon Aug 15 18:56:50 2011
Thread 2 advanced to log sequence 3685 (LGWR switch)
trace file text is as
post info) last post received: 109 0 4
last post received-location: kslpsr
last process to post me: 40233693738 1 6
last post sent: 0 0 24
last post sent-location: ksasnd
last process posted by me: 40233693738 1 6
(latch info) wait_event=0 bits=0
Process Group: DEFAULT, pseudo proc: 0x40233786f80
O/S info: user: oracle, term: UNKNOWN, ospid: 21196 (DEAD)
OSD pid info: Unix process pid: 21196, image: oracle@dbrac2
Short stack dump: unable to dump stack due to error 72
Dump of memory from 0x00000402336539E0 to 0x0000040233653BE8
402336539E0 00000010 00000000 1DC35CE0 00000402 [.........\......]
402336539F0 00000010 000313A7 1DC60660 00000402 [........`.......]
40233653A00 00000003 000313A7 312D7370 00000402 [........ps-1....]
40233653AE0 00000007 000313A7 00000000 00000000 [................]
40233653AF0 00000000 00000000 00000000 00000000 [................]
Repeat 14 times
40233653BE0 00000000 00000000
SO: 0x402336a9318, type: 2, owner: (nil), flag: INIT/-/-/0x00
(process) Oracle pid=55, calls cur/top: (nil)/0x401fe14f1c8, flag: (0) -
int error: 0, call error: 0, sess error: 0, txn error 0
(post info) last post received: 109 0 4
last post received-location: kslpsr
last process to post me: 40233693738 1 6
last post sent: 0 0 24
last post sent-location: ksasnd
last process posted by me: 40233693738 1 6
(latch info) wait_event=0 bits=0
Process Group: DEFAULT, pseudo proc: 0x40233786f80
O/S info: user: oracle, term: UNKNOWN, ospid: 21597 (DEAD)
OSD pid info: Unix process pid: 21597, image: oracle@dbrac2
Short stack dump: unable to dump stack due to error 72
Dump of memory from 0x0000040233655858 to 0x0000040233655A60
40233655850 0000000C 00000000 [........]
40233655860 1DD637A8 00000402 00000010 000313A7 [.7..............]
40233655870 FE14F1C8 00000401 00000003 000313A7 [................]
40233655880 312CC588 00000402 00000013 0003129B [..,1............]
40233655890 33D61950 00000402 0000000B 000313A7 [P..3............]
402336558A0 339F1338 00000402 00000004 0003129B [8..3............]
402336558B0 28A937E8 00000402 00000007 000313A7 [.7.(............]
402336558C0 6259D858 00000401 00000053 000313A7 [X.Yb....S.......]
402336558D0 28A938C8 00000402 00000007 000313A7 [.8.(............]
402336558E0 28A956B8 00000402 00000007 000313A7 [.V.(............]
402336558F0 28A95798 00000402 00000007 000313A7 [.W.(............]
40233655900 28A9F000 00000402 00000007 000313A7 [...(............]
40233655910 28A9E9E0 00000402 00000007 000313A7 [...(............]
40233655920 00000000 00000000 00000000 00000000 [................]
Repeat 19 times
(latch info) wait_event=0 bits=0
Process Group: DEFAULT, pseudo proc: 0x40233786f80
O/S info: user: oracle, term: UNKNOWN, ospid: 27060 (DEAD)
OSD pid info: Unix process pid: 27060, image: oracle@dbrac2
Short stack dump: unable to dump stack due to error 72
Dump of memory from 0x0000040233653FF8 to 0x0000040233654200
40233653FF0 0000000A 00000000 [........]
40233654000 1DC35E78 00000402 00000010 000313A7 [x^..............]
40233654010 1DCD4AF0 00000402 00000003 000313A7 [.J..............]
Repeat 16 times
please give some hint what actually is it and why
also at the end in my alert what does it means
ALTER SYSTEM SET service_names='prod' SCOPE=MEMORY SID='prod2'
regards

By any chance if you back in the alert log just a little more does an ORA-00600 error appear before the immediate kill session messages? I found a few problem reports on the Oracle support site that might be of interest if there is:
ORA-00600 [1301] - Instance Terminated by PMON After Killing Sessions
ORA-600 [4072] Is Possible After Killing A Session Or Cancelling a Operation [ID 1113829.1]
Database Crash ORA-00600: [ksqcmi:res3], [], [], [], [], [], [], [] and ORA-00600: [1100], [ID 1327043.1]
HTH -- Mark D Powell --

RAR 5.3 - kill session of another user

how can RAR admin kill session of another user?

Hi Partha,
There is no way out to kill a user's session in RAR, nor in UME. The only place you can kill a user's session is in backend (R/3 side of a particular system) in T-code: SM04->select a particular session of any user-> end session.
Regards,
Gurugobinda

Kill Session

Hi,
Can someone please help. I just booted up my server (dev server)to try to get rid of some user sessions. I typed the following
SELECT SID,SERIAL#,TYPE,STATUS FROM V$SESSION;
It returned background processes which I understand but what I don't understand is that I show 5 user processes that all active! I should be the only user on the return. I tried everything to get rid of these bogus users but to no avail with a statement such as
ALTER SYSTEM KILL SESSION '7, 97' IMMEDIATE;
and returns and Ora error:Ora-00030 User session ID does not exist.
Can anyone enlighten me on a command that will eliminate these bogus user sessions?
It would be very much appreciated.
Thanks in advance.
Al

Hi,
The user working with apps 11i or 11.0.3?
Straight a way you can kill the process in the windows taskbar.
Second thing is restart the client system.
Killing using alter system session is not adviceable.
Back in the server level automatically will be killed up.
All the best.
Thanks and Regards
Riyas
[email protected]

How to find and kill session similar to forms user session

We have a forms and reports based system that uses the oracle sessions. Sometimes if a form takes a long time we have the need to navigate to iAS>Forms>User Sessions, find the IP of the machine where the form is not responding and kill it based on the IP of the troublesome machine.
I want to add this into our forms environemnt so people can kill their own sessions if need be but not sure how this is handled
is it a simple alter system kill session in the db or something different.
also how is the ip found to match the session?
Thanks

hi,
Instead Set session timeout parameters..So that user gets logged off automatically from the application after a particular interval of time
For this you have to make changes in httpd.conf file,web.xml file and env file
Regards
Fabian

Kill session in shared server

I need to know what i must have into account to perform a kill session to a session in shared server. Is it different to kill a session in dedicated server?

Hi user8820906,
You must gather information of shared server from $server_server like “ name of server,status” use sql prompt “select name, status from v$shared_server”. To kill the session you need information from command select sid, serial# from v$session, then command to kill session is “ALTER SYSTEM KILL SESSION SID,SERIAL# from v$session;
The same sql command is use for both shared and dedicated server.
Regards,
Idrees

Regarding Oracle Sessions

Oracle Database      : 10g EE Release 10.2.0.1.0
Webserver           : Weblogic
Application Language      : Java
Problem : When i connect to Java application it creates following sessions
in Oracle server
SADDR           SID    SERIAL# USERNA MACHINE           PROGRAM
687CAE3C          9      36980 MYUSER WEBSERVER ADDRESS java.exe
687D4EAC         26      26646 MYUSER WEBSERVER ADDRESS java.exe
687ED19C         67      15721 MYUSER WEBSERVER ADDRESS java.exe
68058310        179      14442 MYUSER WEBSERVER ADDRESS java.exeafterwards when i logout from my java application then it doesn't delete
the session. these all remain in the v$session.
And when i am tring to kill the session by following commands.
SQL> alter system kill session '9, 36980';
System altered.
SQL> alter system kill session '26, 26646';
System altered.
SQL> alter system kill session '67, 15721';
System altered.
SQL> alter system kill session '179, 14442';
System altered.But when i again query the v$session view it shows me all the session but the
status is killed..
But i cann't drop that user by runing following query
SQL> drop user myuser cascade;
drop user myuser cascade
ERROR at line 1:
ORA-01940: cannot drop a user that is currently connected.
Is any thing wrong in my process ?
Any suggestions
Regards
Singh

The vast majority of the time, when you're using a J2EE app server like Weblogic, the application server is going to maintain a connection pool. When the application server starts up, it creates a number of physical database connections. When your Java code opens and closes a connection, it's really just getting a connection from the pool and returning it to the pool. From Oracle's standpoint, nothing happens when you logically open a connection in this way, which is generally good because opening and closing physical connections is relatively expensive.
So in summary
- The number of sessions in V$SESSION probably has everything to do with the size of the connection pool you've configured in Weblogic and nothing to do with how many logical connections your application is using at any point in time.
- Do not kill sessions that are part of a connection pool. Oracle will keep the connection around until the client (in this case Weblogic) tries to re-use it, at which point Oracle will inform the client that the connection has been killed, and Weblogic will report the error to whatever application was requesting the connection.
- If you shut down Weblogic, the physical connections should go away.
Justin

Restricted session & Kill Session

Hello everybody,
1) In which case do I need enabled restricted sessions?
2)Where “ALTER SYSTEM KILL SESSION” command will be useful?
Thanks in advance

Salman Qureshi wrote:
Hi,
1) In which case do I need enabled restricted sessions?Whenever you want to perform some maintenance operations in your database and you don't want anyone to access the database except user SYS, you can enable restricted session.
2)Where “ALTER SYSTEM KILL SESSION” command will be useful?When you want to kill a session which is no longer responding or hung or doing some long running operation which is disturbing your performance or you want to stop that processing etc.
SalmanHi Salman,
I think you'll find that "restricted session mode" does not limit login ability to only the SYS user as you mention.
As an example, consider the following.
Session 1:
SQL*Plus: Release 11.2.0.3.0 Production on Tue Jan 1 22:07:03 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
SQL> connect / as sysdba
Connected.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup restrict;
ORACLE instance started.
Total System Global Area 2137886720 bytes
Fixed Size                  2256912 bytes
Variable Size            1258295280 bytes
Database Buffers          872415232 bytes
Redo Buffers                4919296 bytes
Database mounted.
Database opened.
SQL>Session 2:
SQL*Plus: Release 11.2.0.3.0 Production on Tue Jan 1 22:07:51 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
SQL> connect markwill
Enter password:
Connected.
SQL> select logins from v$instance;
LOGINS
RESTRICTED
1 row selected.
SQL>As you can see in Session 2 I am clearly not connecting as SYS user, yet I am capable of connecting to an instance started in restricted mode.
Rather than limiting to only user SYS it limits login ability to users with the RESTRICTED SESSION System Privilege (granted directly or via role).
Regards,
Mark

Alter & Kill Session

Dear all,
when i tried to execute following alter statement it takes almost 10 hours to complete.
ALTER TABLE JUST_STAT_10
ADD ( ZKK_00985 VARCHAR2(20) DEFAULT ' ' NOT NULL,
ZKK_0988 VARCHAR2(96) DEFAULT ' ' NOT NULL,
ZKK_0989 NUMBER(6) DEFAULT 0 NOT NULL,
TKK_0990 VARCHAR2(15) DEFAULT ' ' NOT NULL);
Then I killed session, but the script is now terminating over 12 hours and more.
Is there a way to kill this session without any consequences to the table?
Table stats:
Size: 284 GB
Num_rows:245.222.121
Table_lock:ENABLED
Number_Extents:290.975
Thanks in advance,
Regards,
Robert

user8660054 wrote:
Dear all,
when i tried to execute following alter statement it takes almost 10 hours to complete.
ALTER TABLE JUST_STAT_10
ADD ( ZKK_00985 VARCHAR2(20) DEFAULT ' ' NOT NULL,
ZKK_0988 VARCHAR2(96) DEFAULT ' ' NOT NULL,
ZKK_0989 NUMBER(6) DEFAULT 0 NOT NULL,
TKK_0990 VARCHAR2(15) DEFAULT ' ' NOT NULL);
Then I killed session, but the script is now terminating over 12 hours and more.
Is there a way to kill this session without any consequences to the table?
Table stats:
Size: 284 GB
Num_rows:245.222.121
Table_lock:ENABLED
Number_Extents:290.975
Thanks in advance,
Regards,
RobertYou should check what Oracle was waiting for during execution of SQL.
select event, p1, p2, p3 from v$session_wait where SID = YOUR_SID

Killing session

Dear all,
If we kill session at OS LEVEL by using the command "KILL -9 <SPID>"
or
At the database level if we kill the session by issuing the command <alter system kill session 'sid,serial#' immediate>
If any dml transaction is going on suppose "UPDATE" statement , in the middle of the transaction if we kill the transaction at OS LEVEL or at the DATABASE LEVEL , that particular transaction will rollback or it won't.
Please help me regarding this.
Regards,
Vamsi.

844795 wrote:
Dear all,
If we kill session at OS LEVEL by using the command "KILL -9 <SPID>"
or
At the database level if we kill the session by issuing the command <alter system kill session 'sid,serial#' immediate>
If any dml transaction is going on suppose "UPDATE" statement , in the middle of the transaction if we kill the transaction at OS LEVEL or at the DATABASE LEVEL , that particular transaction will rollback or it won't.
Please help me regarding this.Why you didn't search for this in the Oracle documentation?
http://download.oracle.com/docs/cd/E11882_01/server.112/e17120/manproc008.htm#ADMIN11192
Aman....

Procedure for Killing sessions

Hi All,
Almost everyday we have requirement to kill user sessions for dev user, I'm thinking to create a procedure for this and grant to the users so that they can kill it by themself.
Below is the what I got from Ask Tom forum, however appreciate if someone can share few information if already imlemented in there environment
<quote>
create or replace procedure kill_session( p_sid in number,
p_serial# in number)
is
ignore pls_integer;
BEGIN
select count(*) into ignore
from V$session
where username = USER
and sid = p_sid
and serial# = p_serial# ;
if ( ignore = 1 )
then
execute immediate '
alter system kill session ''' ||
to_char(p_sid,'999999')||','||
to_char(p_serial#,'999999')||'''';
else
raise_application_error( -20001,
'You do not own session ''' ||
p_sid || ',' || p_serial# ||
end if;
END;/
grant execute on kill_session to <username>
</quote>
Regards,
shaan

rp0428 wrote:
>
Instead of killing session with alter systemn kill session, better you opt for below two methods (still perform the same)
>
Please clarify what you mean. KILL and DISCONNECT do NOT perform the same.
From the SQL Language doc
http://docs.oracle.com/cd/B28359_01/server.111/b28286/statements_2013.htm
KILL is the nice one -
>
The KILL SESSION clause lets you mark a session as terminated, roll back ongoing transactions, release all session locks, and partially recover session resources
>
While DISCONNECT is the ogre
>
Use the DISCONNECT SESSION clause to disconnect the current session by destroying the dedicated server process (or virtual circuit if the connection was made by way of a Shared Sever).
>
The difference between the two is roughly analogous to the difference between SHUTDOWN IMMEDIATE and SHUTDOWN ABORT.
I agree that, for OPs use case DISCONNECT (with IMMEDIATE or POST TRANSACTION) may be better since it gets rid of things immediately while KILL can leave things hanging around for a while.From the same link:
DISCONNECT SESSION Clause:
The POST_TRANSACTION setting allows ongoing transactions to complete before the session is disconnected. If the session has no ongoing transactions, then this clause has the same effect described for as KILL SESSION.
The IMMEDIATE setting disconnects the session and recovers the entire session state immediately, without waiting for ongoing transactions to complete.
If you also specify POST_TRANSACTION and the session has ongoing transactions, then the IMMEDIATE keyword is ignored.
If you do not specify POST_TRANSACTION, or you specify POST_TRANSACTION but the session has no ongoing transactions, then this clause has the same effect as described for KILL SESSION IMMEDIATE.
basically the difference is not between DISCONNECT and KILL SESSION, the difference exists if you allow pending/ongoing transactions to finish(IMMEDIATE vs POST_TRANSACTION)
Edited by: Keilor on Jun 25, 2012 12:57 PM
Edited by: Keilor on Jun 25, 2012 1:39 PM

Kill Session with MaxL

Hi all,
I need to do a script to kill sessions with Maxl with more than 8 hours of activity, no matter what they are doing.
The problem is that some sessions are hangs and logout don't work, also not work 'set session_idle_limit' parameter.
Sorry for my english, i'm from Spain. Best regards.

I have a thought on this, as the MAXL script can be automated using essmsh command in batch script. What I will do is run the script for the MAXL script to do following :- "display session on database app_name.db_name"; say now, spool the output to filename1 and schedule the next execution of this script as required say after 8 hours and spool the output to filename2.
Then I will compare the contents of the both files and if any matching records exists for the user, that is the one who is active on database for more than 8 hours.
Hope this solves your requirement..

Regarding kill session

Similar Messages

Maybe you are looking for