Cannot kill vty sessions

Hi ,
yesterday I've added my core switch (WS-C4507R+E) to our Cisco Prime infrastructure server to perform some tests. This morning I've noticed that many vty sessions have been opened by the Prime server and I was trying to close them but I'm not able to close them.
SW-CORE-1#who
    Line       User       Host(s)              Idle       Location
* 1 vty 0     user1 idle                 00:00:00 10.159.240.24
   2 vty 1     user1 idle                 18:22:52 10.162.2.13
   3 vty 2     user1 idle                 18:20:51 10.162.2.13
   4 vty 3     user1 idle                 18:18:50 10.162.2.13
   5 vty 4     user1 idle                 18:16:49 10.162.2.13
   6 vty 5     user1 idle                 18:14:03 10.162.2.13
   7 vty 6     user1 idle                 18:12:03 10.162.2.13
   8 vty 7     user1 idle                 17:56:33 10.162.2.13
   9 vty 8     user1 idle                 18:08:15 10.162.2.13
10 vty 9     user1 idle                 17:54:32 10.162.2.13
11 vty 10    user1 idle                 17:52:31 10.162.2.13
12 vty 11    user1 idle                 17:50:31 10.162.2.13
13 vty 12    user1 idle                 17:47:45 10.162.2.13
14 vty 13    user1 idle                 17:45:44 10.162.2.13
Interface    User               Mode         Idle     Peer Address
SWPIL138P4#clear line vty 1
[confirm]
[OK]
SW-CORE-1#who
    Line       User       Host(s)              Idle       Location
* 1 vty 0     user1 idle                 00:00:00 10.159.240.24
   2 vty 1     user1 idle                 18:24:07 10.162.2.13
   3 vty 2     user1 idle                 18:22:06 10.162.2.13
   4 vty 3     user1 idle                 18:20:05 10.162.2.13
   5 vty 4     user1 idle                 18:18:04 10.162.2.13
   6 vty 5     user1 idle                 18:15:19 10.162.2.13
   7 vty 6     user1 idle                 18:13:18 10.162.2.13
   8 vty 7     user1 idle                 17:57:48 10.162.2.13
   9 vty 8     user1 idle                 18:09:31 10.162.2.13
10 vty 9     user1 idle                 17:55:47 10.162.2.13
11 vty 10    user1 idle                 17:53:47 10.162.2.13
12 vty 11    user1 idle                 17:51:46 10.162.2.13
13 vty 12    user1 idle                 17:49:00 10.162.2.13
14 vty 13    user1 idle                 17:46:59 10.162.2.13
Interface    User               Mode         Idle     Peer Address
I cleared the respective TCP Session using the command : clear tcp tcb XXXXXX but I can't kill the vty session.
I've also removed the switch form the Cisco Prime device inventory.
The switch is a Catalyst C4507R+E with the following IOS-XE cat4500e-universalk9.SPA.03.05.01.E.152-1.E1.bin
Do you have any ideas? A bug software?
thanks
F.Coppotelli

Hi ,
Issue this command,
show line
Clear line 1
Clear line 2
Please let me know if this work
BR // Sanjay

Similar Messages

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

Cannot kill a session immediately

i got an application which update the database. however, the process hang up every time probably due to the app problem. the server process and the sql statement still reside in the database. when i kill it by kill session, it takes more than 3 hrs. In v$session_wait, the event is 'SQL*Net more data from client'.
is it the dB or the app problem?

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

Cannot kill a active session

I tried to kill a active session which is running a scheduled procedure.
The procedure is as follow:
begin
loop
update table1 set column1=column1+1;
end loop;
end;
After I use ALTER SYSTEM KILL SESSION..., the serial# is turned into another number and the session is still alive. Even I restart the DB, the session is still running.
Please help. Thanks.

since the entry from user_jobs is gone, it should not come back in the queue.
did you remove the entry from user_jobs first or did you kill the running job first?
did you do a commit after dbms_job.remove ?
did you check if the job has an entry in the user_jobs view after removing and if it does, does it have a different jobid?
On my system, the job does not come back once the entry from user_jobs has been removed.
If you kill the session first, (before removing the user_jobs entry), it will come back to run again with a different serial#
value. make sure you do these two steps in correct order.

How to kill a session in stored procedure or trigger.

Can anyone let me know, how to kill a particular session in stored procedure or trigger.
Regards
KVSS

also you cannot attempt to kill ur own current session.
But on what circumstances you want to kill the session.
When anyone trys to access a table and lets suppose the trigger onthat table activates
and you want to kill that very session which activated the trigger ???
i dont think its possible. To kill a session definitely you should be in a different session and
then only you can achieve that.
pls check it out
prakash
[email protected]

Killing Oracle Sessions

Please ignore it. By mistakely i posted this thread here.
Hi All,
I want to drop one user. If i made a attempt to drop that user, I rec'd "ORA-01940: cannot drop a user that is currently connected." error. So I checked with sessions with the username. No one is using this user. But it resists some inactive sessions.
SQL> DROP USER test cascade;
DROP USER test cascade
ERROR at line 1:
ORA-01940: cannot drop a user that is currently connected
SQL>select sid,serial#,username,status from v$session where schemaname='TEST';
SID SERIAL# USERNAME STATUS
131 4026 TEST INACTIVE
143 29325 TEST INACTIVE
SQL> alter system kill session '131,4026' immediate;
system altered.
SQL>alter system kill session '143,29325' immediate;
system altered.
SQL> alter system kill session '131,4026' immediate;
system altered.
SQL>alter system kill session '143,29325' immediate;
system altered.
SQL> alter system kill session '131,4026' immediate;
system altered.
SQL>alter system kill session '143,29325' immediate;
system altered.
SQL> alter system kill session '131,4026' immediate;
system altered.
SQL>alter system kill session '143,29325' immediate;
system altered.
Now. I checked in v$sessions,
SQL>select sid,serial#,username,status from v$session where schemaname='TEST';
SID SERIAL# USERNAME STATUS
139 12982 AGILITY_QA INACTIVE
141 54482 AGILITY_QA INACTIVE
It shows some other inactive sessions. so i am trying to kill these 2 sessions again some inactive sessions will show.
Please assist me to fix that problem.
Message was edited by:
Moorthy GS

Try the output of the query to kill all sessions:
select 'alter system kill session '''||sid||','||'4026''' immediate;' scr
from v$session
where schemaname='TEST' and status <> 'KILLED'
Regards
RK

Kill a session that is holding library cache lock!!

Hi, all.
What will happen if I kill a session that is holding library cache lock??
Currently, the session is pending with library cache lock.
I cannot see any locks in v$lock.
If I kill the session, will oracle release the library cache lock??
Thanks and Regards.

What output do you get from the following script?
liblock.sql:
select decode(lob.kglobtyp, 0, 'NEXT OBJECT', 1, 'INDEX', 2, 'TABLE', 3, 'CLUSTER',
                      4, 'VIEW', 5, 'SYNONYM', 6, 'SEQUENCE',
                      7, 'PROCEDURE', 8, 'FUNCTION', 9, 'PACKAGE',
                      11, 'PACKAGE BODY', 12, 'TRIGGER',
                      13, 'TYPE', 14, 'TYPE BODY',
                      19, 'TABLE PARTITION', 20, 'INDEX PARTITION', 21, 'LOB',
                      22, 'LIBRARY', 23, 'DIRECTORY', 24, 'QUEUE',
                      28, 'JAVA SOURCE', 29, 'JAVA CLASS', 30, 'JAVA RESOURCE',
                      32, 'INDEXTYPE', 33, 'OPERATOR',
                      34, 'TABLE SUBPARTITION', 35, 'INDEX SUBPARTITION',
                      40, 'LOB PARTITION', 41, 'LOB SUBPARTITION',
                      42, 'MATERIALIZED VIEW',
                      43, 'DIMENSION',
                      44, 'CONTEXT', 46, 'RULE SET', 47, 'RESOURCE PLAN',
                      48, 'CONSUMER GROUP',
                      51, 'SUBSCRIPTION', 52, 'LOCATION',
                      55, 'XML SCHEMA', 56, 'JAVA DATA',
                      57, 'SECURITY PROFILE', 59, 'RULE',
                      62, 'EVALUATION CONTEXT',
                     'UNDEFINED') object_type,
       lob.KGLNAOBJ object_name,
       lk.KGLLKMOD lock_mode_held,
       lk.KGLLKREQ lock_mode_requested,
       ses.sid,
       ses.serial#,
       ses.username
FROM
       x$kgllk lk,
       v$session ses,
       x$kglob lob,
       v$session_wait vsw
WHERE
   lk.KGLLKUSE = ses.saddr and
   lk.KGLLKHDL = lob.KGLHDADR
   and lob.kglhdadr = vsw.p1raw
   and vsw.event = 'library cache lock'
order by lock_mode_held desc
/It should provide a locking graph of all sessions that are blocked on the 'library cache lock' event, and what sessions are the blockers.
Hope that helps,
-Mark
PS It needs to run as SYSDBA, due to the X$KGLLK reference.

How to find killed form session

Hi All,
I have killed a form session in production.
is there any way to find the killed form session.
web and forms or on one server and concurrent managers or on other server
and also can we find out how many users have connected to applications and database .
our application version is 11.5.10.2 and database version is 9.2.0.8.
Thanks,
sandeep.

I have killed a form session in production.
is there any way to find the killed form session.If the session is no longer marked as killed then you cannot find it.
http://forums.oracle.com/forums/search.jspa?threadID=&q=Inactive+AND+Sessions&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
and also can we find out how many users have connected to applications and database .http://forums.oracle.com/forums/search.jspa?threadID=&q=Users+Connected&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
Thanks,
Hussein

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.

Kill user sessions dynamically through PL/SQL

Hello,
Every night I have to DROP one user in order to recreate the entire schema. In order to do this I have to disconnect the user from the DB by killing its sessions. I am using following PL/SQL code
ALTER SYSTEM ENABLE RESTRICTED SESSION;
begin
    for x in (
            select Sid, Serial#, machine, program
            from v\$session
       where username = 'STARSTAGING_DB'
   ) loop
          execute immediate 'Alter System DISCONNECT Session '''|| x.Sid
                  || ',' || x.Serial# || ''' IMMEDIATE';
    end loop;
end;
DROP USER starstaging_db CASCADE;
ALTER SYSTEM DISABLE RESTRICTED SESSION;
I have also tried using keyword KILL instead of DISCONNECT of session.
Most of the day this works, user is dropped and new one is created, but sometimes I get the following problem.
The problem that has occurred in a log file is:
PL/SQL procedure successfully completed.
DROP USER starstaging_db CASCADE
ERROR at line 1:
ORA-01940: cannot drop a user that is currently connected
System altered.
CREATE USER STARSTAGING_DB IDENTIFIED BY *****
ERROR at line 1:
ORA-01920: user name 'STARSTAGING_DB' conflicts with another user or role name
Does anyone have an idea how I can make sure that the user for sure disconnects, so that I can drop him?
Best Regards,
Vladimir

Cannot comment on a better approach as that means a proper analysis of the business requirements. Just keep in mind that killing sessions is a brutal way to manage user connectivity to the database - and should be seen as an exception and the last resort.
You can wrap your schema drop code into a retry loop. Something as follows:
loop
   begin
      ..do the drop..
      success := true;
exception when FAILED then
      dbms_lock.sleep(60); -- sleep 60 seconds
end;
retry := retry + 1;
exit when success or retry > HAVE_WAITED_LONG_ENOUGH;
end loop;

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

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

Cannot create a session after the response has been committed (Tomcat 6)

I'm getting a rather annoying error when I try to open a pretty basic JSP page.
I'm rather new to the whole JSP scene, so I'm following the example found on pages 287 and onwards in "JSF in Action - Manning" in case anyone wanted to check my code against the source.
I've searched for about 4 hours now, coming back to this site a couple of times, once reading about writeouts and stuff. But I'm not really sure this is the issue in this case and if it is, where exactly the problem lies.
I've already fixed a number of errors I got (jtsl.jar and standard.jar missing etc...) but this particular problem is driving me (and my co-workers for that matter :-) ) up the wall.
Anyone willing to help me out here?
Error:
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: Cannot create a session after the response has been committed
     javax.faces.webapp.FacesServlet.service(FacesServlet.java:152)
root cause
java.lang.IllegalStateException: Cannot create a session after the response has been committed
     org.apache.catalina.connector.Request.doGetSession(Request.java:2301)
     org.apache.catalina.connector.Request.getSession(Request.java:2075)
     org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:833)
     org.apache.myfaces.context.servlet.SessionMap.setAttribute(SessionMap.java:53)
     org.apache.myfaces.util.AbstractAttributeMap.put(AbstractAttributeMap.java:103)
     org.apache.myfaces.util.AbstractAttributeMap.put(AbstractAttributeMap.java:35)
     org.apache.myfaces.application.jsp.JspStateManagerImpl.saveSerializedViewInServletSession(JspStateManagerImpl.java:523)
     org.apache.myfaces.application.jsp.JspStateManagerImpl.saveSerializedView(JspStateManagerImpl.java:358)
     javax.faces.application.StateManager.saveView(StateManager.java:47)
     org.apache.myfaces.application.jsp.JspViewHandlerImpl$StateMarkerAwareWriter.flushToWriter(JspViewHandlerImpl.java:387)
     org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:322)
     org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41)
     org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:132)
     javax.faces.webapp.FacesServlet.service(FacesServlet.java:138)
Source Code of login.jsp:
<%@ page language="java" contentType="text/html; charset=ISO-8859-1"
    pageEncoding="ISO-8859-1"%>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f"%>
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%>
<f:view>
<html>
<head>
     <title>
          <h:outputText value="ProjectTrack"/>
     </title>
</head>
     <body>
          <table>
               <tr>
                    <td>
                         <h:graphicImage url="/images/logo Skillteam.jpg"
                         alt="Welcome to ProjectTrack"
                         title="Welcome to ProjectTrack"
                         width="435" height="120"/>
                    </td>
               <td>
                    <font face="Arial, sans-serif"
                    size="6">
                    <h:outputText value="ProjectTrack"/>
                    </font>
               </td>
               </tr>
     http://forum.java.sun.com/post!default.jspa?forumID=45#
Click for bold     </table>
     </body>
</html>
</f:view>
web.xml & faces-config
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xmlns="http://java.sun.com/xml/ns/javaee"
     xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
     xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" id="WebApp_ID" version="2.5">
     <display-name>ProjectTrack</display-name>
     <welcome-file-list>
     <welcome-file>faces/login.jsp</welcome-file>
     <welcome-file>index.html</welcome-file>
     </welcome-file-list>
     <servlet>
     <servlet-name>Faces Servlet</servlet-name>
     <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
     <load-on-startup>1</load-on-startup>
     </servlet>
     <servlet-mapping>
     <servlet-name>Faces Servlet</servlet-name>
     <url-pattern>/faces/*</url-pattern>
     </servlet-mapping>
</web-app>
<?xml version="1.0"?>
<!DOCTYPE faces-config PUBLIC
"-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.0//EN"
"http://java.sun.com/dtd/web-facesconfig_1_0.dtd">
<faces-config>
     <navigation-rule>
          <from-view-id>/login.jsp</from-view-id>
          <navigation-case>
               <from-outcome>success</from-outcome>
               <to-view-id>/inbox.jsp</to-view-id>
          </navigation-case>
          <navigation-case>
               <from-outcome>failure</from-outcome>
               <to-view-id>/login.jsp</to-view-id>
          </navigation-case>
     </navigation-rule>
</faces-config>Setup:
Eclipse Europe 3.3.0
Tomcat 6.0.13
MyFaces 1.2
JRE 1.6.0_02

When searching for this error, this was the first page google gave me. I found the answer and just in case anyone else stumbles in here with the same question I thought I'd share my findings.
Unfortunately, if your problem is the same as mine, you're going to feel pretty silly. I was navigating to the wrong page. If MyFaces(when running tomcat) tries to resolve to a page that doesn't exist, the error given above is what happens.
In my case I accidentally put my .jsp page into the wrong directory and ended up banging my head against the wall for an hour figuring that out. Hope this helps someone.

ALLOW A USER TO KILL A SESSION WITHOUT ALTER SYSTEM PRIVILEGE.

Hi
I need a user to have permission to kill a session without having the ALTER SYSTEM privilege. I created a procedure on sys schema and granted the EXECUTE privilege to the user but it doesn't work, how can I do, help please.
CREATE OR REPLACE PROCEDURE SYS.PRC_SESSION_KILLER (P_SID IN NUMBER, P_SERIAL IN NUMBER)
AS
BEGIN
     EXECUTE IMMEDIATE 'GRANT ALTER SYSTEM TO SYSADMIN';
     EXECUTE IMMEDIATE 'ALTER SYSTEM KILL SESSION ''' || P_SID || ',' || P_SERIAL || ''' IMMEDIATE';
     EXECUTE IMMEDIATE 'REVOKE ALTER SYSTEM FROM SYSADMIN';
END;
Thank you very much.

Hi,
I second everything John said.
Are you sure the arguments are correct?
Below is the procedure I use. You may want to run it, just to see what the error is.
PROCEDURE     kill_internal
     s_id          IN     NUMBER,
     serial_num     IN     NUMBER,
     stat_out     OUT     VARCHAR2
IS
     alter_handle     INTEGER;
     ex_val          INTEGER;     -- Returned by dbms_sql.execute
BEGIN
     alter_handle := dbms_sql.open_cursor;
     dbms_sql.parse
          alter_handle,
          'ALTER SYSTEM     KILL SESSION '''     ||
               TO_CHAR (s_id, '999990')     ||
               ', '                    ||
               TO_CHAR (serial_num, '999990')     ||
          dbms_sql.native
     ex_val := dbms_sql.execute (alter_handle);
     dbms_sql.close_cursor (alter_handle);
     stat_out := 'Success: '                    ||
               TO_CHAR (s_id, '999990')     ||
               ', '                    ||
               TO_CHAR (serial_num, '999990');
EXCEPTION
     WHEN OTHERS
     THEN
          stat_out := 'Failure:'          ||
               SQLERRM;
--          dbms_output.put_line (stat_out);
          dbms_sql.close_cursor (alter_handle);
END     kill_internal
;

Cannot kill vty sessions

Similar Messages

Maybe you are looking for