Unable to Kill Session

Good day all
in my db i found the one session hang my table .but when i try to kill it i receive the following message 'session marked as kill'
when i run
SELECT SID, SERIAL#, STATUS
FROM V$SESSION
i found its status is kill but it still make my table busy.
how can i kill it
note : im use oracle 10g under Linux

Then it might be that something else is blocking your session or the os process. Also this is not a PL/SQL or SQL question. One of the DBAs in the Database - General forum might give you a better answer.

Similar Messages

Unable to kill the concurrent program

Hi
I have two cocnurrent programs say TEST_PROG1, TEST_PROG2.
if i am submitting TEST_PROG1 then oracle session id and oracle process id are popluating in fnd_concurrent_requests table
where as if iam doing the same with TEST_PROG2 then oracle session id and oracle process id are populating as null.
Is there any configuration problem with the second problem?
And if i amtrying to kill the request of TEST_PROG2, Using the below query
SELECT s.SID,
s.serial#,s.audsid,r.oracle_session_id
FROM fnd_concurrent_requests r,
gv$session s
WHERE 1 =1
AND r.request_id = 2998345;
AND r.oracle_session_id = s.audsid(+);
AND r.request_date > TRUNC(SYSDATE-1)
AND r.status_code NOT IN ('C','E','D','X');
which is returning null .But iam using serial#, audsid to kill the session
using
l_sql := 'alter system kill session '''|| l_sid || ','||l_serial_number||'''';
but iam unable to kill the session as thwy are getting null from the above sql.
Please help me to resolve this.
Thanks
Satya

HI
Followed the link shared and in one of your replied i found the below
I am not sure why there are no values stored in FND_CONCURRENT_REQUESTS table (for some columns) when you submit such reports, and I believe if this is resolved you will be able to see the trace files generated. So, is it possible to register any of these custom reports in one of the standard responsibilities and see if the values in the table are populated and/or the trace file get generated then?
I have added my concurrent program to US HRMS Reports & Processes request group. But still the same problem
Thanks
Satya

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

EJB 3.0: java.io.IOException: Unable to find session object ...

Hello,
We have an EJB3 application deployed to an Oracle AS 10.1.3.1.0 instance.
Our main point of entry to the application is a stateful session bean (that controls access), that has injected several other stateful session beans.
Like this:
+@Stateful(name = "TstreamUserSession")+
+public class TstreamUserSessionBean extends UserSessionBean implements TstreamUserSession {+
+@EJB(name = "ContactSession")+
private ContactSessionLocal contactSession;
+@EJB(name = "GuestSession")+
private GuestSessionLocal guestSession;
+@EJB(name = "TechCustomerSession")+
private TechCustomerSessionLocal techCustomerSession;
+@EJB(name = "PmSession")+
private PmSessionLocal pmSession;
+@EJB(name = "CustomerSession")+
private CustomerSessionLocal customerSession;
+@EJB(name = "PartnerSession")+
private PartnerSessionLocal partnerSession;
+@EJB(name = "AdminSession")+
private AdminSessionLocal adminSession;
+@EJB(name = "SuperAdminSession")+
private SuperAdminSessionLocal superAdminSession;
+@EJB(name = "VmSession")+
private VmSessionLocal vmSession;
+public TstreamUserSessionBean() {+
+}+
+...+
In this class, we also look up these sessions, because we need several instances of these, in this manner:
+private synchronized Object getSessionInstance(String sessionName) throws AccessDeniedException {+
          +try {+
               InitialContext ic = new InitialContext();
               return ic.lookup("java:comp/env/" sessionName);+
          +} catch (NamingException e) {+
          +}+
     +}+
However, we keep getting the following messages after a certain period.
java.io.IOException: Unable to find session object 2816103596632839360 for location 'AdminSession'
+10/01/12 11:50:04 at com.evermind.server.ejb.EJBInternalInputStream.resolveObject(EJBInternalInputStream.java:70)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.checkResolve(ObjectInputStream.java:1346)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1912)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1836)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1713)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339)+
+10/01/12 11:50:04 at com.evermind.server.ejb.StatefulSessionEJBObject.activateBean(StatefulSessionEJBObject.java:581)+
+10/01/12 11:50:04 at com.evermind.server.ejb.StatefulSessionEJBObject.remove_X(StatefulSessionEJBObject.java:213)+
+10/01/12 11:50:04 at com.evermind.server.ejb.StatefulSessionEJBObject.remove_X(StatefulSessionEJBObject.java:159)+
+10/01/12 11:50:04 at com.evermind.server.ejb.StatefulSessionEJBHome.processTimedOutSessions(StatefulSessionEJBHome.java:371)+
+10/01/12 11:50:04 at com.evermind.server.ejb.StatefulSessionEJBHome.cleanUpMaintenance(StatefulSessionEJBHome.java:306)+
+10/01/12 11:50:04 at com.evermind.server.ejb.EJBTask.run(EJBTask.java:47)+
+10/01/12 11:50:04 at com.evermind.util.Task.schedule(Task.java:51)+
+10/01/12 11:50:04 at com.evermind.util.TaskManager.run(TaskManager.java:221)+
+10/01/12 11:50:04 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)+
+10/01/12 11:50:04 at java.lang.Thread.run(Thread.java:595)+
I guess this occurs when the stateful session TstreamUserSession is reactivated?
Or when the ones being injected are passivated?
Any idea why this occurs, or how to suppress it, because it really spams our logs...
Thanks.

Hello,
We have an EJB3 application deployed to an Oracle AS 10.1.3.1.0 instance.
Our main point of entry to the application is a stateful session bean (that controls access), that has injected several other stateful session beans.
Like this:
+@Stateful(name = "TstreamUserSession")+
+public class TstreamUserSessionBean extends UserSessionBean implements TstreamUserSession {+
+@EJB(name = "ContactSession")+
private ContactSessionLocal contactSession;
+@EJB(name = "GuestSession")+
private GuestSessionLocal guestSession;
+@EJB(name = "TechCustomerSession")+
private TechCustomerSessionLocal techCustomerSession;
+@EJB(name = "PmSession")+
private PmSessionLocal pmSession;
+@EJB(name = "CustomerSession")+
private CustomerSessionLocal customerSession;
+@EJB(name = "PartnerSession")+
private PartnerSessionLocal partnerSession;
+@EJB(name = "AdminSession")+
private AdminSessionLocal adminSession;
+@EJB(name = "SuperAdminSession")+
private SuperAdminSessionLocal superAdminSession;
+@EJB(name = "VmSession")+
private VmSessionLocal vmSession;
+public TstreamUserSessionBean() {+
+}+
+...+
In this class, we also look up these sessions, because we need several instances of these, in this manner:
+private synchronized Object getSessionInstance(String sessionName) throws AccessDeniedException {+
          +try {+
               InitialContext ic = new InitialContext();
               return ic.lookup("java:comp/env/" sessionName);+
          +} catch (NamingException e) {+
          +}+
     +}+
However, we keep getting the following messages after a certain period.
java.io.IOException: Unable to find session object 2816103596632839360 for location 'AdminSession'
+10/01/12 11:50:04 at com.evermind.server.ejb.EJBInternalInputStream.resolveObject(EJBInternalInputStream.java:70)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.checkResolve(ObjectInputStream.java:1346)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1912)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1836)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1713)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)+
+10/01/12 11:50:04 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339)+
+10/01/12 11:50:04 at com.evermind.server.ejb.StatefulSessionEJBObject.activateBean(StatefulSessionEJBObject.java:581)+
+10/01/12 11:50:04 at com.evermind.server.ejb.StatefulSessionEJBObject.remove_X(StatefulSessionEJBObject.java:213)+
+10/01/12 11:50:04 at com.evermind.server.ejb.StatefulSessionEJBObject.remove_X(StatefulSessionEJBObject.java:159)+
+10/01/12 11:50:04 at com.evermind.server.ejb.StatefulSessionEJBHome.processTimedOutSessions(StatefulSessionEJBHome.java:371)+
+10/01/12 11:50:04 at com.evermind.server.ejb.StatefulSessionEJBHome.cleanUpMaintenance(StatefulSessionEJBHome.java:306)+
+10/01/12 11:50:04 at com.evermind.server.ejb.EJBTask.run(EJBTask.java:47)+
+10/01/12 11:50:04 at com.evermind.util.Task.schedule(Task.java:51)+
+10/01/12 11:50:04 at com.evermind.util.TaskManager.run(TaskManager.java:221)+
+10/01/12 11:50:04 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)+
+10/01/12 11:50:04 at java.lang.Thread.run(Thread.java:595)+
I guess this occurs when the stateful session TstreamUserSession is reactivated?
Or when the ones being injected are passivated?
Any idea why this occurs, or how to suppress it, because it really spams our logs...
Thanks.

Unable to set session in Oracle Portal useing reverse proxy

I have deployed a reverse proxy (using Oracle HTTP Server) in front of a Oracle Portal Install (version 10.1.2.0.2). The steps followed to set this up came from the following documents:
Steps mentioned in Section 9.2 Configuring a Reverse Proxy for OracleAS Portal and OracleAS Single Sign-On for a reverse proxy on a Oracle HTTP Server.
http://download-west.oracle.com/docs/cd/B14099_15/core.1012/b13998/variants.htm#ASTED005
Also performed steps mentioned in -> Section 5.3.7 - Step 7: Enable Session Binding on OracleAS Web Cache of the Oracle® Application Server Portal Configuration Guide 10g Release 2 (10.1.2) -- B14037-03.
My current (example names shown only)setup details are as follows:
Reverse Proxy for SSO server (running on internal.oracle.com:7777): proxy.oracle.com:7777
Reverse Proxy for Portal server (running on internal.oracle.com:7778): proxy.oracle.com:7778
With the above steps completed, I can successfully use the http://proxy.oracle.com:7777/pls/orasso for login into SSO without any issues.
Users get authenticated successfully.
I can also use http://proxy.oracle.com:7778/pls/portal for viewing pages on the portal fine . All self referencing links have also been successfully modified to point to proxy.oracle.com:7778.
However, an attempt to login in the portal is not successful. Clicking on the 'Login' link successfully redirects to the SSO login page (http://proxy.oracle.com:7777/<login-page>). However, after successful authentication, the success page fails to show up and the user gets shown the initial login portal home page again.
There are no error messages shown on the screen.But it seems that user session is failing to be initiated/set correctly, as shown by the log file (in $PORTAL_ORACLE_HOME/j2ee/OC4J_Portal/application-deployments/portal/OC4J_Portal_default_island_1/application.log ):
06/11/21 16:49:31 portal: [module=RepositoryServlet, ecid=83928411196,1] Repository Gateway: LWUser: PUBLIC, Cookie: oracle.uix=0^^GMT+10:00;
portal=9.0.3+en-au+us+AUSTRALIA+22BC75924EEAD8A2E040007F010019F7+8DAC5E3559C95F5E0090A6F56FFA58192CB0F437CA57A9102A6394F1EB7FAB5DEE3BFA12C65
91C0C009B6......
06/11/21 16:49:31 portal: [module=RepositoryServlet, ecid=83928411196,1] ERROR: Repository Gateway error: Database Error: ORA=20001 ORA-20001:
Unable to obtain session information from the cookie. Please close your browser and reconnect.
ORA-06512: at "PORTAL.WPG_SESSION", line 149
ORA-06512: at line 22
Any help with this will be appreciated.
Thanks.

Hi Chris,
The begin of the expection stack gives you the reason:
06/11/03 09:13:59 java.sql.SQLException: The method 'setSavepoint' cant be called when a global transaction is active
The reason is, that either the whole global transaction must be commited or rollbacked.
I don't know your actual configuration, but between the methods begin() and commit()/rollback() of the UserTransaction instance, OC4J/OracleAS uses a global transaction (= XA transaction) in your configuration. The state of a global transactions is completely under the control of the application server and several restrictions must be considered. One of them is, that you can't use the method setSavePoint/. E.g. you can't also call the method setAutoCommit(true) in this state, or change the transaction isolation level via setTransactionIsolation(newLevel).
This is NOT a limitation of the OC4J/OracleAS but is true for ALL application servers.
P.S. I can successfully set savepoints and rollback to savepoints in weblogic 9.0This means, that WebLogic 9.0 doesn't use a global transaction in this case.
Because I don't know your configurations (Oracle and WebLogic) I can't say, why the behave different in this situation.
Best,
Manfred

How to kill session in forms

In my application I want to kill session if any user
is idle for 2 minutes.
I am using oracle forms 6i and database oracle 9i

You have to use D2KWutil.pll
In when new form instance write the following code
declare
hWind PLS_INTEGER;
CheckTimer TIMER;
begin
hWind := get_window_property(FORMS_MDI_WINDOW,WINDOW_HANDLE);
Win_API_Session.Timeout_Start_Timer(hWind);
CheckTimer := Create_Timer('CheckTimeout',1000,repeat);
end;
and in when timer expired trigger write the following code
begin
if upper(get_application_property(TIMER_NAME)) = 'CHECKTIMEOUT' then
:timer.t1 := Win_api_session.Timeout_Get_Inactive_Time;
if :timer.t1 > 120 then -- timer is a block and t1 is text item (don't assign a canvas to it, make it invisible)
Win_API_Session.timeout_delete_timer;
exit_form (NO_VALIDATE);
end if;
end if;
end;
hope this helps !!

Unable to kill locks in table

Hi,
I have identified a lock on a table and have killed the id holding the lock
alter system kill session '119,63799'
.SID OBJNAME PROGRAM LOCKTIME SPID PROCESS Mo EVENT STATUS
119 CA850MB sqlplus@ipborbp 02:06:48:24 8067 8066 3 SQL*Net br KILLED
But after this, it shows that the lock is still present for ID 119.
On trying to kill the session again, it says "User session does not exist", but the lock is still present.
Is there a way to solve this problem without a database BOUNCE.
Rgds,
Nagesh

Sounds like something that I often face or faced recently. When the session with sid 119 is killed, and locks still persist on the same object, and when you tried to kill the session again, you got the message "User session does not exist". My suspicion here is that at this moment, it is a different sid that is holding up the object. If you kill that one, another one could suface
I believe Mohamed's suggestion is right - kill the OS process id that they all should be gone at once

Urgent-how to run 'alter system kill session 'sid, serial#' in form 6i ?

I want to write a procedure in Form 6i so that user can kill the session by herself.
I know kill session sql is 'alter system kill session 'sid, serial#'', however, I fould that I can only run it it sql plus screen, how can I run it in Form or in Stored procedure?
Urgent....Please!

try using Forms_ddl('alter system......'); in the forms. it will execute the dml statements in the form.
zaibi.

Killed sessions

Hi,
I kill a session with the commands:
select username, sid, serial#, status from v$session where username like 'RION%'
alter system kill session 'sid, serial#'
and if I give again the first select command at the status column appears KILLED. I want not to have KILLED in the status column.
Thank you,
Mihaela

hi all,
As u know you are seeing the status of at v$session view as killed, I wanna confirm that this will exists in two senario.
When a Session is in inactive state and a kill command on that session is issued then the "status" column of v$session will be updated as killed as to indicate/mark as it is killed, and the "server " column will be updated as psuedo. when the user again try to connect to the session user will receive 0ra-00028 error and the entry will be removed from v$session.
Another senario is that the transaction is at its half way, either in commiting or at the roleback stage for that partucular session then also you can find that the v$table is updated as above.
more information, go through the documentation, at the Server Process handling section.
i hope it cleared your confussion,

Kill Session in Oracle 10g

Oracle 10g r2
I killed a session after fetching the sid and serial from the v$session as under
select * from v$session where username='SAM';
alter system kill session '530,7420'
Now the status showed killed.
But again after some time one i query the v$session the status turn to inactive.
Why so?

Yeah Madrid....
Thanks for that.. at the developer side.. they did get session killed.
But actually my doubt here was. that once i killed the session then i go the status as "killed" in the v$session
but less then a minute when i again query the v$session then i see the status aa inactive. This is what is not clear to me.

Logging into Oracle Apps R12 throws error - unable to authenticate session

Hi All,
Working on R12 OS:AIX
Logging into Oracle Apps R12 throws error - "unable to authenticate session".
Earlier Guest user was end-dated which has now been removed and autoconfig was run.but still the same issue..(services were bounced too)
Guest user password is:ORACLE(uppercase) in xml file,dbc file,GUEST profile options..
could anyone please share such an experience encountered before and suggest resolution...
Would appreciate an early response!
Thanks for your time!
Regards,

Pl see ML Note 342332.1 on steps needed to troubleshooot login. Although this doc is for 11i, it should also apply to R12
Srini Chavali

Unable to Kill the Consolidation task for HFM application

User is unable to kill the Consolidation task in HFM application. Consolidation process which usually takes 2 mins has been showing status as running @79% since 4-6 hrs. User ID is has the provisioning manager, lock Data and unlock data provisions in Shared Services. The stop task button in the Running Tasks list is not enabled . Our Support team has advanced user access which is not also able to stop the task. Please note Admin access is restricted and not allowed for such tasks.

I would check the HFM Log to see if you find anything referring to locked / blocked records.
If your HFM app is killed in the middle of consolidating or performing other activities that requires it to 'lock' a segment of memory in the database, that 'lock' is still held on those data points when the application restarts.
If you then try to perform another consolidation and it hits one of those locked data points, it will sit there for a very long amount of time waiting for the 'lock' to clear.
I forget the exact error message that you will find in the log AND I forget the timeout period; however, it sucks having to wait through that.
The other possibility that comes to mind is that the consolidation really aborted and the status didn't update. (once again check the logs)
Charles

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

ALTER SYSTEM KILL SESSION privilege

Hi All,
Is there any possibility to use this command from a without having DBA priviileges, what is the privilege to be grantd to the ordinary users to execute ALTER SYSTEM KILL SESSION... statement..
Thanks in advance

The procedure proposed by Rusell would be more or less so:
SQL> create or replace procedure kill_session
2 ( v_sid number, v_serial number )
3 as
4 v_varchar2 varchar2(100);
5 begin
6 execute immediate 'ALTER SYSTEM KILL SESSION '''
7 || v_sid || ',' || v_serial || '''';
8 end;
9 /
Procedure created.
SQL> select username, sid, serial# from v$session;
USERNAME                              SID    SERIAL#
                                      147       5078
SYS                                   148       6161
                                      151       6769
                                      156          1
                                      158          1
                                      159          1
REPOS_OWNER                           161      14502
                                      163          1
                                      164          1
                                      165          1
                                      166          1
USERNAME                              SID    SERIAL#
                                      167          1
                                      168          1
                                      169          1
                                      170          1
15 rows selected.
SQL>
SQL> exec kill_session(161,14502);
PL/SQL procedure successfully completed.
SQL>Joel Pérez
http://otn.oracle.com/experts

Kill session permission without alter system permission?

Syntax to kill session is
ALTER SYSTEM KILL SESSION 'session info';
Is there a way to allow a user to kill his/her own session without granting rights to SYSTEM? I don't want anyone to be able to drop the database, but they need to be able to kill their own session. I've looked everywhere...
Thanks in advance!

Yes, assuming you are using standard definer's rights stored procedures. Only if you specify AUTHID CURRENT_USER when creating the stored procedure will you get an invoker's rights stored procedure, which would run with the privileges of the caller, not of the definer.
Justin

Unable to Kill Session

Similar Messages

Maybe you are looking for