Unable to kill infoview session using LogOnToken

Hi All,
I am not able to reuse the EnterpriseSession created in java.
I have a java webapp which displays a list of webi reports with hyper-link.
when user click on a hyper-link, the web app displays the report in infoview in a iframe element.
The problem is whenever user clicks on link a extra session is being created.
I am unable to figure out the problem, why infoview is creating a new session when i am passing a valid Token.
And if i do not pass token then infoview displays login page.
The problem is my webapplication don't have any reference of infoview session so that that i can clean the sessions on webapp log-out.
I am creating session in java and putting it in HttpSession along with logOnToken.
following link i am using to open a document.
http://MyHost/OpenDocument/opendoc/openDocument.jsp?iDocID=<userSelection>&token=<logOnToken>&sWindow=Same&lang=userLocaleLang&sLang=userLocaleLang&NAII=Y
By following way i am creating token.
ILogonTokenMgr tokenMgr=boSession.getLogonTokenMgr();
logOnToken = tokenMgr.createLogonToken("",31,100);
//logOnToken = tokenMgr.getDefaultToken(); also tried with this.
have anyone encountered this kind of problem?
i would approciate even a suggestion.
For info, i have logOntoken as true in InfoViewApp and CMSApp
Thanks,
VijayS.

Thanks Ted, for ur reply.
I am not sure about the why infoviewer is creating extra session on passing token. is this normal behaviour ?
could you please share information on parameter name to pass serialized session?
I have search the web a lot, but found nothing.
Regards,
VijayS.
Edited by: vijaysaraf on Jan 31, 2011 8:55 AM

Similar Messages

Unable to kill a session request

i had started to run a calc script and then decided to cancel it manually on a BSO data base. In the sessions I can see that the request is in "Terminating stage" but has been like that forever( almost 5 hours)
i have tried scripts to kill it but failed
Alter System Kill request all;
ALter system logout session all;
Tried to manually kill it through EAS by even using force but it's still there.
Any ideas on how I can kill the session?
Thanks.

Once in a while these things just won't go away and you need to kill the serprocess running it. If it is on Windows bring up task manager on the server and look for the Esssvr session that has cpu on it. End that task. To make my live easier, I go into EAS and right click on applications and say stop all applications. The one that does not disappear out of Task manager is the one to terminate. You could also look in the Essbase log and find the PID the application started on.
In Uxin it is easier as you gan do a ps -eaf and see the name of the application and kill -9 it's PID

Kill the session Using Pl/sql Script

Hi,
I wrote a PL/SQL Script which kills the Specified Schema name..... the Script Run Successfully i got this output message "PL/SQL procedure successfully completed." But the Problem is in session status the status is in KILLED" state for more than 30 minutes.
Please Advice Why the Session in Killed State for more than 30 minutes and please tell me how to kill the session immediate;
I am Using Oracle DB 11g R1 and OS is Windows 2003 Server R2
My Pl/sql Script
SET SERVEROUTPUT ON;
DECLARE
KILLER1 V$SESSION.SID%TYPE;
KILLER2 V$SESSION.SERIAL#%TYPE;
CURSOR KILL_SESSION IS SELECT SID,SERIAL# FROM V$SESSION WHERE SCHEMANAME='NAME';
BEGIN
OPEN KILL_SESSION;
LOOP
FETCH KILL_SESSION INTO KILLER1,KILLER2;
EXIT WHEN KILL_SESSION%NOTFOUND;
DBMS_OUTPUT.put_line ('ALTER SYSTEM KILL SESSION '''||KILLER1||','||KILLER2||''' IMMEDAITE');
EXECUTE IMMEDIATE 'ALTER SYSTEM KILL SESSION'||chr(39)||KILLER1||','||KILLER2||chr(39);
END LOOP;
IF (KILLER1 > 0)
THEN
EXECUTE IMMEDIATE 'ALTER SYSTEM KILL SESSION'||chr(39)||KILLER1||','||KILLER2||chr(39);
END IF;
CLOSE KILL_SESSION;
END;
Thank You
Shan

Hello,
In fact you may use orakill it's an Oracle utility for Windows so as to Kill the thread corresponding
to the session.
It's equivalent to a kill -9 on Unix.
Please find here a link about the use of orakill:
http://articles.techrepublic.com.com/5100-10878_11-5224960.html
Hope this help.
Best regards,
Jean-Valentin
Edited by: Lubiez Jean-Valentin on Mar 27, 2010 5:17 PM

How can we Kill the session using Maxl

Hi All,
iam using EAS(11.1)
i want to kill the sessions before loading the dimension and data into the cube , if any body connected or workinng on that server cube bcoz
to avoid cube correptions
how can i write MAXl for this scenario.???
If any help,It would be appriciated.
Thanks

Hi,
You can use the following maxl statements
alter system kill request all;
Which will kill all requests on the essbase server, also you can use
alter system logout session all force;
More information available at :- http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_techref/maxl_altsys.htm
Cheers
John
http://john-goodwin.blogspot.com/

Unable to kill a session in SM50 or SM66

One of our developer was working on a program and there was a network failure. When we got the network back the system shows the process is till running since 3 days. Tried to kill it from SM50 and SM66.
While logging in it is giving 3 options and even after selecting "Continue with this logon and end any other logons in system" its not ending that session.
After we logon the program is running good.
How to kill this session??
Details of the session is given below
No Ty. PID      Status Reasn Start Err Sem CPU      Time   Cl. User
3 DIA 6584     Running       No            296:36   168191 130 BYARLAGADDA
Report / Spool action
CL_ABAP_TABLEDESCR============CP
Main Program
SAPLCV110
Action                    Table
Waiting f.                                                                   since
Database                         Number              Time (usec)         Recs.
Direct Read                    14,681             519,103                 524
Sequential Read                18,146            595171                    83
Insert                              0                   0                   0
Update                              0                   0                   0
Delete                              0                   0                   0

Why does no-one understand SAP Architecture well enough anymore, I blame bad trainers.
Its like seeing a car driving badly all over the road and blowing up the car rather than shooting the driver.
The WP is not the problem, it is the task in the WP that is.
Killing a user in SM04 or a job in SM37 often works. Then I would try cancelling the program in SM50, not the work process.
If that fails then normally it is waiting on something - often RFC. If RFC a simple removal of the connection in SMGW removes the task from the WP. In this case it looks like a rogue DB process, in this case the WP is just waiting for a response from the DB... killing the WP just gets rid of the visibility in SM50, it does not remove the problem... in fact it then would make my job of identifying why the system is running slow a lot worse.

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

Killing oracle session in RAC

Hi
Some of the tables ot locked in my database(it is 4 node RAC) so i first identified the session id and serial has to kill the session using belo query
col oracle_username for a10
col os_user_name for a10
set linesize 150
select s.sid,s.serial#,s.inst_id,l.inst_id,l.session_id,l.oracle_username,l.XIDUSN,l.XIDSLOT,l.XIDSQN,l.OBJECT_ID,
l.OS_USER_NAME,l.PROCESS,l.LOCKED_MODE
from gv$session s,gv$locked_object l
where s.sid=l.session_id
and ORACLE_USERNAME='&USERNSME';
it gaves me below result
       168        202          1          1        168 TEST123           72          0      34994      35239 test123   6652            3
so i tried to kill it using below command
alter system kill session '168,202,@1' immediate;
but i m getting below error
SQL> ALTER SYSTEM KILL SESSION '168,202,@1' IMMEDIATE;
ALTER SYSTEM KILL SESSION '168,202,@1' IMMEDIATE
ERROR at line 1:
ORA-00030: User session ID does not exist.plz suggest how do i kill session in oracle rac

yes it is there
SQL> select sid,serial# from v$session where sid=168 and serial#=202;
       SID    SERIAL#
       168        202
SQL> select sid,serial#,inst_id from gv$session where sid=168 and serial#=202;
       SID    SERIAL#    INST_ID
       168        202          1
SQL> alter system kill session '168,202' immediate;
alter system kill session '168,202' immediate
ERROR at line 1:
ORA-00030: User session ID does not exist.
SQL> alter system kill session '168,202,@1' immediate;
alter system kill session '168,202,@1' immediate
ERROR at line 1:
ORA-00030: User session ID does not exist.

Killing Discoverer Session

I need to kill discoverer sessions that are in the process of running queries. If I use the alter system kill session ' sid, serial#' immediate; , the session gets "marked for kill" and continues. I don't understand why it's getting marked for kill as it's simple select statements. Is there a way to immediately kill these sessions from the database?

Hi
You should be ok. In order to kill sessions you will need to have access to V$ views, V$SESSION, V$PROCESSS, V$SQLAREA. Also, V$OPEN_CURSOR will have all currently opened cursors.
From V$SESSION you can then get the SID and SERIAL#.
As a DBA, you can kill the session using the following command. The SID and SERIAL# values of the relevant session can then be substituted into the following statement:
ALTER SYSTEM KILL SESSION 'SID, SERIAL#';
Note: SID and SERIAL# values are separated by a comma and are within single quotes.
In some situations the Oracle.exe is not able to kill the session immediately. In these cases the session will be "marked for kill". It will then be killed as soon as possible.
Issuing the ALTER SYSTEM KILL SESSION command is the only safe way to kill an Oracle session. If the marked session persists for some time you may consider killing the process at the operating system level. Killing OS processes is dangerous and can lead to instance failures, so do this at your own peril.
It is possible to force the kill by adding the IMMEDIATE keyword:
ALTER SYSTEM KILL SESSION 'sid,serial#' IMMEDIATE;
This should prevent you ever needing to use the orakill.exe in Windows, or the kill command in UNIX and Linux.
This statement:
SELECT
S.SID, P.SPID, S.OSUSER, S.PROGRAM
FROM
V$PROCESS P, V$SESSION S
WHERE
P.ADDR = S.PADDR;
will show you the sessions.
The SID and SPID values of the relevant session can then be substituted into the following command issued from the Windows command line:
orakill ORACLE_SID spid
The session thread should be killed immediately and all resources released.
To kill a session using UNIX / LINUX, first identify the session as shown above, then substitute the relevant SPID into the following command:
% kill -9 spid
If in doubt check that the SPID matches the UNIX PROCESSID shown using:
% ps -ef | grep ora
The session thread should be killed immediately and all resources released
For more information, click here: http://www.oracle-base.com/articles/misc/KillingOracleSessions.php
Best wishes
Michael

Killing Sessions using MBeans

Guys,
Am having hung sessions in memory, wondering if anyone knows how to kill
them programatically using MBeans. In other words is there a MBean class which
gives me list of all active sessions in memory ?
Thanks

Guys,
Am having hung sessions in memory, wondering if anyone knows how to kill
them programatically using MBeans. In other words is there a MBean class which
gives me list of all active sessions in memory ?
Thanks

Unable to kill one user's session

Hi SAP Experts,
In SAP SCM system, when I view the users list, there is one EMPTY session with UNIDENTIFIED user. If I click the button End Session, SAP throws a message "Make a selection". It seems not able to kill its session.
I have attached the screenshot for your reference as below.
Could you please tell me how to kill that session or find out who the user is ?
Thanks and regards,
Danny Pham

Hello Danny,
Follow the solution mentioned in the below note:
1040464 - CEN reconnection, blank rows in SM04 AL08, init CCMS agent
regards,
pavan

Script to kill blocking sessions

We use Oracle 10. We have a test database used solely for training and I need the give the trainer the ability to kill all the blocking sessions when a block(s) is holding up
the entire class.
My idea was to create a simple form on our Oracle menu- containing just a single button that when pressed would trigger the script. One press of the button
to kill each and every blocking session. I have no clue as to how to write a script of this nature. Would appreciate any advice.
Regards,
Sandy

This is easier said than done. Numerous reasons. Here's a couple:
You cannot rely on using v$session to identifying blocked sessions.
Some user sessions may be blocked by a system process (e.g. log writer), which means you cannot unblock the user sessions by killing the blocking session. (especially when running into an Oracle bug where a user session will spin on "+enq: RO - fast object reuse+" when dropping an object and then being shown as blocked by a system session/process).
Killing a session in Oracle is a misnomer as the "+alter system kill session+" is a request and not a command. The relevant user session needs to terminate itself (kind of like assisted suicide). No other process actually kills the physical process (or thread) executing that user session. Thus if that user session is waiting on some external response or event, it will be unable (now and forever) to respond to that kill request. In such a case, the only alternative is killing the physical process instead. (or shutting down the database)
A blocking session could be a job process that contains problematic code that leads to the blocking/serialisation. Killing that session will simply fail the job after which the job queue manager will restart the session again.. 16 times in succession. Only then will it mark that job entry as broken and cease trying to restart it.
So killing blocking sessions? It is not easy to identify blocking processes, they cannot always be killed, and even when you do kill them, they may simply reincarnate as a new session.
So what is the solution then?
Blocking sessions are not "+A Bad Thing+". There are very good and technically sound reasons for serialisation. When it does become a problem, there's something more to it. And blindly killing blocking sessions in such a case is treating the symptom of a problem and ignoring the problem all together. Find the reason for this serialisation and address that.

PL/SQL procedure to kill inactive session

Hi all ,
Please i am trying to write a procedure to kill inactive sessions of the shema 'TESTSCHEMA' .This is my first procedure , am not use to pl/sql but i went through many turtorial but have some errors at compliation .when i try to compile the procedure the errors are as below :
15:50:28 Start Find Objects [TESTSCHEMA@TESTDB_UNIX(2)] ...
15:50:28 End Find Objects [TESTSCHEMA@ TESTDB_UNIX(2)]
15:50:32 Start Compiling 1 object(s) ...
15:50:32 Executing ALTER PROCEDURE fib_dead_cnx_cleanup COMPILE ...
15:50:32 [13:2] PL/SQL: ORA-00933: SQL command not properly ended
15:50:32 [9:3] PL/SQL: SQL Statement ignored
15:50:32 [18:12] PLS-00103: Encountered the symbol "(" when expecting one of the following:
15:50:32 constant exception <an identifier>
15:50:32 <a double-quoted delimited-identifier> table LONG_ double ref
15:50:32 char time timestamp interval date binary national character
15:50:32 nchar
15:50:32 The symbol "<an identifier>" was substituted for "(" to continue.
15:50:32 [18:21] PLS-00103: Encountered the symbol "LOOP" when expecting one of the following:
15:50:32 := ; not null default character
15:50:32 The symbol "; was inserted before "LOOP" to continue.
15:50:32 [27:8] PLS-00103: Encountered the symbol "ALTER" when expecting one of the following:
15:50:32 begin case declare exit for goto if loop mod null pragma
15:50:32 raise return select update while with <an identifier>
15:50:32 <a double-quoted delimited-identifier> <a bind variable> <<
15:50:32 close current delete fetch lock insert open rollback
15:50:32 savepoint set sql execute commit forall merge pipe
15:50:32 Compilation complete - 5 error(s) found
15:50:32 End Compiling 1 object(s)
below is the procedure code :
CREATE OR REPLACE
PROCEDURE fib_dead_cnx_cleanup
AS
l_serial     CHAR(100);
l_sid CHAR (100);
l_sid_serial CHAR(100);
l_count      NUMBER(10,0);
CURSOR session_cur IS
          SELECT sid,serial#,sid||','||serial# as sid_serial
     FROM v$session
     WHERE username='EBBFCAT' and schemaname='TESTSCHEMA'
     and status='INACTIVE'
BEGIN
     BEGIN
     l_count := 0;
               OPEN session_cur;
                    WHILE ( 1 = 1) LOOP
                         BEGIN
                              FETCH session_cur INTO l_sid ,l_serial,l_sid_serial ;
                                   EXIT WHEN session_cur%NOTFOUND ;
                              BEGIN
                                   alter system kill session 'l_sid_serial' ;
                              END;
                         END;
                    END;
               CLOSE session_cur;
     END;
END FIB_DEAD_CNX_CLEANUP;
Thanks

Hi,
Never write, let alone post, unformatted code.
When posting any formatted text on this site, type these 6 characters:
{code}
(small letters only, inside curly brackets) before and after sections of formatted text, to preserve spacing.
Among the benefits of formatting: you can indent to show the extent of blocks, such as BEGIN-END.
Different types of blocks need modifiers after the end, such as "END *IF* " and " END *LOOP* ". If each opening statement (BEGIN, IF, LOOP) is directly above its corresponding END, then it's easy to check if you got the right modifier.
Here's what you code looks like with some formatting, and a couple of corrections added. Look for -- comments.
CREATE OR REPLACE
PROCEDURE fib_dead_cnx_cleanup
AS
     l_serial     CHAR(100);
     l_sid          CHAR (100);
     l_sid_serial     CHAR(100);
     l_count          NUMBER(10,0);
     CURSOR session_cur IS
            SELECT sid
            ,       serial#
            ,       sid     || ','
                                  || serial#     as sid_serial
            FROM     v$session
            WHERE      username     = 'EBBFCAT'
            and     schemaname     = 'TESTSCHEMA'
            and     status          = 'INACTIVE';          -- need semicolon here
BEGIN
     BEGIN                                   -- Why?
          l_count := 0;
          OPEN session_cur;
          WHILE ( 1 = 1)
          LOOP
                BEGIN                         -- Why?
                     FETCH session_cur
                     INTO   l_sid
                     ,          l_serial
                     ,          l_sid_serial ;
                           EXIT WHEN session_cur%NOTFOUND ;
                     BEGIN                    -- Why?
                         alter system kill session 'l_sid_serial' ;    -- Not a PL/SQL command
                           END;
                      END;
            END LOOP;                         -- LOOP ends with END LOOP
            CLOSE session_cur;
        END;
END      FIB_DEAD_CNX_CLEANUP;Take baby steps.
I've been wrtiing PL/SQL for 20 years, and I would never write that much code at once. If you're a beginner, all the more reason to start small. Write as little as possible, test, debug and test again (if necessary). When you have someting working, add 2 or 3 more lines and test again.
It looks like you have three BEGIN statements that don't serve any purpose. You should get rid of them (and their corresponding END statements, of course).
One error I did not fix: ALTER SYSTEM is not a PL/SQL statement. It's a SQL statement. You can run a SQL statement inside PL/SQL by using dynamic SQL, where you construct a string containing the SQL statement, and then use dbms_sql or EXECUTE IMMEDIATE to run it.
Edited by: Frank Kulash on Aug 18, 2009 12:37 PM

Cannot kill a session that is running a query on a linked server in SQL Server 2008 R2

Hi,
Cannot kill a session that is running a query on a linked server in SQL Server 2008 R2.
When I try to kill, it status shown as "KILLED/ROLLBACK"
I have facing the issue from long back. I searched many and none of them worked for me
Any help is greatly appreciated
Thanks
Jaison
Carver

I guess its stuck, can you see some blocking or any other process blocking the rollback.
can you check rollback status using below command. Or you can use sp_who2 and check status column
select percent_complete,estimated_completion_time from sys.dm_exec_requests
where spid=xxx
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Call function RFC in a loop and kill old session

Hi,
we have a problem with a program.
here's a part of the code:
DO.
    CALL FUNCTION 'YC_REFRESH_GPT_START_CM25' STARTING NEW TASK 'TEST'
      EXPORTING
        i_profile       = p_prfl
        i_werks         = p_werks
        i_arbpl_low     = s_arbpl-low
        i_arbpl_high    = s_arbpl-high
      TABLES
        t_arbpl = it_arbpl.
    PERFORM wait_for_refresh.
    PERFORM terminate_session.
ENDDO.
So the program does a call function, waits a while, then terminates the session and recalls the function.
Apparently, like this the data should be updated.
But in the terminate session, the session is terminated using:
CALL 'ThUsrInfo' ID 'OPCODE' FIELD opcode_delete_mode
                   ID 'MODE'    FIELD l_mode.
And it works the first time, but the second time there is a dump.
So, is there another way to achieve what this program is trying to do?
Or is there another way to kill the session?
Thanks!!

Hi,
the DLL will stay in memory as long as there is a program running which has not closed (unloaded) the DLL.
Doing repetitive calls to the DLL is irrelevant in this context. LV opens the DLL as soon as needed and will only unload it when there is no VI in memory which has a CLN to that DLL...
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Killing all sessions at once who are locking the objects

Hello all,
i am working in 9i Oracle RDBMS on AIX IBM OS
most of the time we face locking issue and there comes more then different 50 sessions which locking different tables.
here is my script to find out what sessions are locking what tables.
set lines 200
set pages 50000
col SID for 99999
col SERIAL# for 999999
col username format a12
col sql format a55
col event format a50
col program format a40
col MINS for 9999
col ID1 for 999999
col object_name for a35
col locktype for a8;
select /*+ ORDERED */ s.sid,s.serial#,s.status,round(s.last_call_et/60) MINS,s.program,l.ID1,d.object_name,d.object_type,l.type as locktype
from v$lock l,v$session s, dba_objects d
where l.sid = s.sid
and l.ID1 = d.object_id
and s.username = 'MULDMS'
and last_call_et > 120 and l.type <> 'TX' order by s.status,MINS,l.ID1,l.type; and the out put it gives something like
SID SERIAL# STATUS    MINS PROGRAM                                      ID1 OBJECT_NAME                         OBJECT_TYPE        LOCKTY
8981    1069 ACTIVE       2 frmweb@Appsdms31 (TNS V1-V3)               30407 VH_BTN                              TABLE              TM
1642     512 ACTIVE      15 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
690    1057 ACTIVE      17 [email protected] (TNS V1-V3)    28846 AM_DOCS                             TABLE              TM
699    1787 ACTIVE      17 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
690    1057 ACTIVE      17 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
690    1057 ACTIVE      17 [email protected] (TNS V1-V3)    30643 VT_CHECK_INOUT                      TABLE              TM
10877     895 ACTIVE      18 [email protected] (TNS V1-V3)     28846 AM_DOCS                             TABLE              TM
6654    1085 ACTIVE      18 [email protected] (TNS V1-V3)    28846 AM_DOCS                             TABLE              TM
1912    1655 ACTIVE      18 [email protected] (TNS V1-V3)    28846 AM_DOCS                             TABLE              TM
10877     895 ACTIVE      18 [email protected] (TNS V1-V3)     30407 VH_BTN                              TABLE              TM
6654    1085 ACTIVE      18 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
1912    1655 ACTIVE      18 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
1754    1582 ACTIVE      18 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
10877     895 ACTIVE      18 [email protected] (TNS V1-V3)     30643 VT_CHECK_INOUT                      TABLE              TM
6654    1085 ACTIVE      18 [email protected] (TNS V1-V3)    30643 VT_CHECK_INOUT                      TABLE              TM
10708     982 ACTIVE      19 [email protected] (TNS V1-V3)    28846 AM_DOCS                             TABLE              TM
5428     855 ACTIVE      19 [email protected] (TNS V1-V3)    28846 AM_DOCS                             TABLE              TM
10708     982 ACTIVE      19 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
5428     855 ACTIVE      19 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
10278     897 ACTIVE      20 [email protected] (TNS V1-V3)     28846 AM_DOCS                             TABLE              TM
6261    1056 ACTIVE      20 frmweb@appsdms12 (TNS V1-V3)               28846 AM_DOCS                             TABLE              TM
6598    1413 ACTIVE      20 [email protected] (TNS V1-V3)     28846 AM_DOCS                             TABLE              TM
1312    1000 ACTIVE      20 [email protected] (TNS V1-V3)    28846 AM_DOCS                             TABLE              TM
10278     897 ACTIVE      20 [email protected] (TNS V1-V3)     30407 VH_BTN                              TABLE              TM
6261    1056 ACTIVE      20 frmweb@appsdms12 (TNS V1-V3)               30407 VH_BTN                              TABLE              TM
1312    1000 ACTIVE      20 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
3521     717 ACTIVE      20 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
6598    1413 ACTIVE      20 [email protected] (TNS V1-V3)     30407 VH_BTN                              TABLE              TM
6598    1413 ACTIVE      20 [email protected] (TNS V1-V3)     30643 VT_CHECK_INOUT                     TABLE              TM
1312    1000 ACTIVE      20 [email protected] (TNS V1-V3)    30643 VT_CHECK_INOUT                   TABLE              TM
9131    1002 INACTIVE     2 [email protected] (TNS V1-V3)    30455 VH_PSF                              TABLE              TM
4887    1040 INACTIVE     2 [email protected] (TNS V1-V3)     30455 VH_PSF                              TABLE              TM
151    1982 INACTIVE     2 [email protected] (TNS V1-V3)     80224 RD_ENQEXD                           TABLE              TM
846     988 INACTIVE     3 [email protected] (TNS V1-V3)    29228 GM_VIN                              TABLE              TM
5364    1149 INACTIVE     3 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
9934     789 INACTIVE     3 [email protected] (TNS V1-V3)     30455 VH_PSF                              TABLE              TM
7511    1092 INACTIVE     3 [email protected] (TNS V1-V3)    30455 VH_PSF                              TABLE              TM
3595    1104 INACTIVE     3 [email protected] (TNS V1-V3)    30455 VH_PSF                              TABLE              TM
846     988 INACTIVE     3 [email protected] (TNS V1-V3)    30455 VH_PSF                              TABLE              TM
945     670 INACTIVE     3 [email protected] (TNS V1-V3)    30455 VH_PSF                              TABLE              TMand then i have to kill the session one by one . thaat is a tedious task to do.
i want to modify this script which will give me all the kill statement and i just have to run it
can someone help me in this regard as i am weak in sql/plsql
thanks and many thanks

>
i want to modify this script which will give me all the kill statement and i just have to run it
>
Karthick's script will 'kill' the sessions but before you use that script you may want to read the docs about the KILL and DISCONNECT clauses.
See the DISCONNECT SESSION and KILL SESSION clauses in the SQL Language doc
http://docs.oracle.com/cd/B28359_01/server.111/b28286/statements_2013.htm#sthref4724
>
DISCONNECT SESSION Clause
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.
KILL SESSION Clause
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.
>
For DISCONNECT the IMMEDIATE clause will recover the session state 'immediately'.
Using KILL, even with the IMMEDIATE clause, you are telliing Oracle to roll back any ongoing transactions and that can take a lot of time.
Make sure you are really doing the operation you want to do. If you want to get the locks released immediately you need to use 'DISCONNECT IMMEDIATE'.

Unable to kill infoview session using LogOnToken

Similar Messages

Maybe you are looking for