Wine kills my X session

Ive just installed Beryl and was gonna give WoW a go with wine from the repos.
When installed i noticed that i got alots of strange .wine dirs, like .wine-Uo87xt and so on.
and no Program Files dir was created either.
But i created one and put my WoW folder there.
The thing is that when i run any wine application like
# wine /path/WoW.exe -opengl
or just
# winecfg
it kills X and im thrown out to vc/1 terminal.
i cant really tell if it is a Beryl error-message or not.
Does anyone know why this is happening?
i followed this guide to install wine and WoW but with very little success since i even cant get wine running.
http://wiki.archlinux.org/index.php/Wow#Installing_Wine

well, the sending the output to a logfile didnt do jack
but! i did start X with just startx instead of startxgl 1 xfce4-session nvidia
and now it works! but though with somewhat low fps and no beryl candy.
is it possible to have both or do i have to make this hearthbreaking choice?
edit: i startx and then choose beryl as windowmanager, then both wine and beryl work together.
But does this startx work just aswell as startxgl? or do i loose any performance by this option?
The loadingtime in shattrah city was terrible, even though the Fps was good.
Last edited by sund (2007-07-15 23:54:37)

Similar Messages

Killing Parallel Query Session

Hi,
I am running Oracle 11.2.0.1.0 on Solaris 5.10.
Couple of hours ago, I ran a job through DBMS_JOB (Yes, I need to use dbms_schedular), and in the job I used parallel query. Now I want to remove the job. Also I want to clean up the sessions. I can remove the job by doing DBMS_JOB.remove(job id). Is there a way that I kill one parallel query coordinator session, and it would automatically kill all the slave sessions?
Thanks and regards
Edited by: Fahd Mirza on Apr 22, 2010 11:57 AM

Thanks for the answer.
I have run the following query with output:
SQL> select ps.sid,s.username,ps.qcsid
from v$session s, v$px_session ps
where s.sid=ps.sid
and s.username='BIADM'; 2    3    4
       SID USERNAME                            QCSID
        91 BIADM                                 147
       267 BIADM                                 147
       290 BIADM                                 147
       332 BIADM                                 147
       345 BIADM                                 147
        69 BIADM                                 147
        92 BIADM                                 147
       102 BIADM                                 147
       222 BIADM                                 147
       112 BIADM                                 147
        73 BIADM                                 147
       126 BIADM                                 147
       136 BIADM                                 147
       145 BIADM                                 147
       170 BIADM                                 147
       180 BIADM                                 147
       276 BIADM                                 147
       190 BIADM                                 147
       221 BIADM                                 147
       234 BIADM                                 147
       214 BIADM                                 147
       246 BIADM                                 147
       270 BIADM                                 147
       256 BIADM                                 147
       278 BIADM                                 147
       291 BIADM                                 147
       309 BIADM                                 147
       298 BIADM                                 147
       323 BIADM                                 147
       344 BIADM                                 147
         2 BIADM                                 147
       331 BIADM                                 147
       134 BIADM                                  94
       125 BIADM                                  94
       156 BIADM                                  94
       168 BIADM                                  94
       181 BIADM                                  94
       205 BIADM                                  94
       191 BIADM                                  94
       215 BIADM                                  94
       232 BIADM                                  94
       245 BIADM                                  94
       255 BIADM                                  94
       269 BIADM                                  94
       292 BIADM                                  94
       302 BIADM                                  94
       280 BIADM                                  94
       311 BIADM                                  94
       147 BIADM                                 147
        94 BIADM                                  94
50 rows selected.If I kill sessions with sid 147 and 94, shouldn'it it be killing all the sessions of BIADM?
REGARDS

URGENT!!! How to kill a SYS session

What is the command to kill a SYS session? Let's say someone figured out the SYS password and logged in. Now I want to kill the session. What do I do?
The ALTER SYSTEM KILL SESSION 'SID,SERIAL#' does not work.
URGENT!!!!

Hi,
>>The ALTER SYSTEM KILL SESSION 'SID,SERIAL#' does not work.
Why not ?
C:\>sqlplus sys/******* as sysdba
SQL*Plus: Release 10.1.0.2.0 - Production on Fri Jun 15 17:06:26 2007
Copyright (c) 1982, 2004, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
SYS@ORACLE10> SELECT userenv('ISDBA') from dual;
USEREN
TRUE
SYS@ORACLE10> select sid,serial# from v$session where sid=(select distinct sid from v$mystat);
SID SERIAL#
236 22100
Other session:
[pre]
C:\>sqlplus system/*********
SQL*Plus: Release 10.1.0.2.0 - Production on Fri Jun 15 17:07:02 2007
Copyright (c) 1982, 2004, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
SYSTEM@ORACLE10> alter system kill session '236,22100';
System altered.
Back to one ...
SYS@ORACLE10> select sysdate from dual;
select sysdate from dual
ERROR at line 1:
ORA-00028: your session has been killedCheers

How to kill the blocking session

hi expert,
when i m going to run the below query
Update rcv_transactions_interface rti set rti.processing_mode_code ='BATCH' where rti.interface_transaction_id = 3671265
it gives the error:
ORA-00054 resource busy and acquire with NOWAIT specified.
i find out the blocking session by using the blow query;
SELECT a.SESSION_ID, a.SESSION_SERIAL#, min(A.SAMPLE_TIME) start_time,max(A.SAMPLE_TIME) end_time,a.inst_id, a.blocking_session,a.user_id,s.sql_text,A.EVENT,O.OBJECT_NAME,max(A.SAMPLE_TIME) - min(A.SAMPLE_TIME)
FROM GV$ACTIVE_SESSION_HISTORY a ,gv$sql s, dba_objects o
where a.sql_id=s.sql_id
and A.CURRENT_OBJ# = O.OBJECT_ID
and blocking_session is not null
and a.user_id != 0 -- exclude SYS user
and a.sample_time > sysdate - 7
and a.event = 'enq: TX - row lock contention'
group by a.SESSION_ID, a.SESSION_SERIAL#, a.inst_id,a.blocking_session,a.user_id,s.sql_text,A.EVENT,O.OBJECT_NAME
it gives the output
SESSION_ID
SESSION_SERIAL#
START_TIME
END_TIME
INST_ID
BLOCKING_SESSION
USER_ID
SQL_TEXT
EVENT
OBJECT_NAME
MAX(A.SAMPLE_TIME)-MIN(A.SAMPLE_TIME)
369
45,849
9/4/2013 8:29:33.119 AM
9/4/2013 11:40:27.508 AM
1
554
173
SELECT POL.UNIT_PRICE   FROM PO_LINES POL WHERE POL.PO_LINE_ID = :b1
enq: TX - row lock contention
PO_LINES_ALL
+00 03:10:54.389000
554
18,872
9/4/2013 8:29:33.119 AM
9/4/2013 11:40:27.508 AM
1
365
173
SELECT POL.UNIT_PRICE,POL.QUANTITY,POL.UNIT_MEAS_LOOKUP_CODE,POL.AMOUNT   FROM PO_LINES POL WHERE POL.PO_LINE_ID = :b1
enq: TX - row lock contention
JA_IN_PO_LINE_LOCATION_TAXES
+00 03:10:54.389000
572
168
9/4/2013 8:29:33.119 AM
9/4/2013 11:40:27.508 AM
1
554
173
select line_location_id into :b0 from po_line_locations_all where line_location_id=:b1 for update of line_location_id
enq: TX - row lock contention
PO_LINE_LOCATIONS_ALL
+00 03:10:54.389000
581
4,973
9/4/2013 10:49:38.157 AM
9/4/2013 10:50:39.259 AM
1
572
173
Update rcv_transactions_interface rti set rti.processing_mode_code ='BATCH' where rti.interface_transaction_id = 3671265
enq: TX - row lock contention
RCV_TRANSACTIONS_INTERFACE
+00 00:01:01.102000
my problem is in the above output among 4 which i have to delete so sove my issue.
its very urgent for me.
plz plz suggest me and how can i kill the session.
thanks & regards
pritesh ranjan

priteshranjan wrote:
hi expert,
when i m going to run the below query
Update rcv_transactions_interface rti set rti.processing_mode_code ='BATCH' where rti.interface_transaction_id = 3671265
it gives the error:
ORA-00054 resource busy and acquire with NOWAIT specified.
i find out the blocking session by using the blow query;
SELECT a.SESSION_ID, a.SESSION_SERIAL#, min(A.SAMPLE_TIME) start_time,max(A.SAMPLE_TIME) end_time,a.inst_id, a.blocking_session,a.user_id,s.sql_text,A.EVENT,O.OBJECT_NAME,max(A.SAMPLE_TIME) - min(A.SAMPLE_TIME)
FROM GV$ACTIVE_SESSION_HISTORY a ,gv$sql s, dba_objects o
where a.sql_id=s.sql_id
and A.CURRENT_OBJ# = O.OBJECT_ID
and blocking_session is not null
and a.user_id != 0 -- exclude SYS user
and a.sample_time > sysdate - 7
and a.event = 'enq: TX - row lock contention'
group by a.SESSION_ID, a.SESSION_SERIAL#, a.inst_id,a.blocking_session,a.user_id,s.sql_text,A.EVENT,O.OBJECT_NAME
it gives the output
SESSION_ID
SESSION_SERIAL#
START_TIME
END_TIME
INST_ID
BLOCKING_SESSION
USER_ID
SQL_TEXT
EVENT
OBJECT_NAME
MAX(A.SAMPLE_TIME)-MIN(A.SAMPLE_TIME)
369
45,849
9/4/2013 8:29:33.119 AM
9/4/2013 11:40:27.508 AM
1
554
173
SELECT POL.UNIT_PRICE   FROM PO_LINES POL WHERE POL.PO_LINE_ID = :b1
enq: TX - row lock contention
PO_LINES_ALL
+00 03:10:54.389000
554
18,872
9/4/2013 8:29:33.119 AM
9/4/2013 11:40:27.508 AM
1
365
173
SELECT POL.UNIT_PRICE,POL.QUANTITY,POL.UNIT_MEAS_LOOKUP_CODE,POL.AMOUNT   FROM PO_LINES POL WHERE POL.PO_LINE_ID = :b1
enq: TX - row lock contention
JA_IN_PO_LINE_LOCATION_TAXES
+00 03:10:54.389000
572
168
9/4/2013 8:29:33.119 AM
9/4/2013 11:40:27.508 AM
1
554
173
select line_location_id into :b0 from po_line_locations_all where line_location_id=:b1 for update of line_location_id
enq: TX - row lock contention
PO_LINE_LOCATIONS_ALL
+00 03:10:54.389000
581
4,973
9/4/2013 10:49:38.157 AM
9/4/2013 10:50:39.259 AM
1
572
173
Update rcv_transactions_interface rti set rti.processing_mode_code ='BATCH' where rti.interface_transaction_id = 3671265
enq: TX - row lock contention
RCV_TRANSACTIONS_INTERFACE
+00 00:01:01.102000
my problem is in the above output among 4 which i have to delete so sove my issue.
its very urgent for me.
plz plz suggest me and how can i kill the session.
thanks & regards
pritesh ranjan
According to the above, your session_id is 581 which is blocked by session_id 572 so you need to kill the 3rd session in the list.
Thanks,
Hussein

How to kill particular Oracle Session from the multiple Session of User

Hi,
I am working on Web Application using ASP.NET , C# with Oracle. I am excuting queries from multiple connection of same user. I want to kill particular user session. I have tried to Kill session by using ALTER SYSTEM KILL SESSION 'sid,serial#' it is working fine but how can i identify which session is generated by particular connection so that i can kill that particular session.
Suppose there us user 'abc' there are multple instance of this user and all are active but same USERNAME. So Please tell me how can i identify that session through which i am executing the query.
Thanks,
Nitin

Some ideas for how to pick the right session:
-Look at the time the session was connected (logon_time)
-Look at the time the session last started it's most recent statement (last_call_et)
-Look at the sql that the session is running (join with sql_address and sql_hash_value over to v$sqltext_with_newlines or one of the other views that show you the sql they are running)
That usually gets me most of the way, if it's possible to distinguish them. ("Yeah I just started this query and I want you to kill it." is different than "I started five different queries at about the same time and I'm not sure which one I need killed.")

Killing a user session?

Running Essbase 11.1.2 ASO cube...occassionally, when I attempt to kill a user session in EAS, I get the status of "terminating". I try to kill the session using Maxl commands to no avail. I know as a last resort to use task manager to end the ESSSVR.exe process -but I have been burned by this in the past as the database gets corrupted. Does anyone know of a safe method to kill these "terminating" sessions? and why are some easy to kill through EAS and others are not?

Hi ,
You may find the following entries in the application log which means there were hung sessions.
+[Mon Jan 24 13:23:46 2011]Local/ESSBASE0///Error(1013290)+
Failed to logout user []: timeout while waiting for requests to die
+[Mon Jan 24 13:23:46 2011]Local/ESSBASE0///Info(1056092)+
Sessions logged out [0]
However, it is difficult to say why these errors occur exactly. Usually Errors like this occur because there are still processes running in the memory when the next transaction is called.
A vast majority of errors can be avoided by integrating pauses and by unloading the application and then reloading it after each calculation or member/data load.
When you kill a session from the EAS Console for a particular user, you need to wait for some time before the process gets compeltely killed, which perform a restructure or data load or data aggregation. You need to wait untill the process gets killed completely before performing any operations on the application.
Never allow any other user to modify outline or update data whenever the Calculation is running. This can cause the application to go into a hang state and whenever you try to kill and if it fails, then you need to kill the ESSSVR process manually. For instance, follow the below guide lines when running Calc scripts:
1) Never allow any other user to indulge any activity on the application. It is preferred to schedule the batch script as a nightly process, if it is a large operation to avoid user interruption.
2) In case of hangups, use the UNLOCKOBJECT command (ESSCMD) to first unlock all the objects that are accessed by the script (Check the technical reference guide for the command ).
3) Next log off the user using the LOGOUTUSER command, but here if you have multiple sessions of the same user logged in the application, all the sessions will be logged off. In this case use the EAS console and kill all the requests of the user first and then kill the session of the user.
Suggestion:
Try to execute the following MaxL commands as batch script and check if the execution of Calculation script is successful:
spool on to 'D:\output\backup.log';
login admin mypassword on localhost;
alter application <app_name> load database <db_name>;
alter system logout session on database <db_name>;
Shell Sleep 30;
alter system kill request on database <db_name>;
Shell Sleep 30;
alter application <app_name> disable commands;
Shell Sleep 30;
Execute Calculation <app_name>.<db_name>.<calc_name>;
Shell Sleep 30;
alter application <app_name> enable commands;
Shell Sleep 30;
logout;
exit;
You can also refer the doc: How to Kill the Essbase Processes/Sessions in 'Terminating' Status (Doc ID 839411.1)
Hope it helps...
KosuruS

Kill user's session via ABAP (like in SM04)

Does anybody knows is it possible to kill user's session via ABAP? Not all session like via TH_DELETE_USER, but selectively, session by session.
Maybe someone know how to trace which logic works when we press "Close session" button in SM04?

Hi Michael,
below a snippet to retrieve the sessions and a way to delete a TID.
Maybe it come in handy for your requirement.
Best,
Sander
INCLUDE tskhincl.
   DATA lt_userlist TYPE STANDARD TABLE OF uinfo.
   DATA ls_userlist TYPE uinfo.
CALL 'ThUsrInfo' ID 'OPCODE' FIELD opcode_list
         ID 'TABUSR' FIELD lt_userlist .
CALL 'ThUsrInfo' ID 'OPCODE' FIELD opcode_delete_usr
     ID 'TID' FIELD ls_userlist-tid.

TuxRacer kill my x session!!

I installed tuxracer:
pacman -Sy tuxracer
it worked fine.
when i ran it the first time, he could not find libstdc++.so.6
so:
pacman -S gcc
it installed it, and now when I run tux racer it kills my x session.

nvidia-installer log file '/var/log/nvidia-installer.log'
creation time: Mon May 10 14:53:08 2004
option status:
license pre-accepted : true
update : false
force update : false
expert : false
uninstall : false
driver info : false
no precompiled interface: true
no ncurses color : false
query latest driver ver : false
OpenGL header files : false
no questions : true
silent : false
XFree86 install prefix : /usr/X11R6
OpenGL install prefix : /usr
Installer install prefix: /usr
kernel source path : (not specified)
kernel install path : (not specified)
proc mount point : /proc
ui : none
tmpdir : /tmp
ftp site : ftp://download.nvidia.com
Using built-in stream user interface
-> License accepted by command line option.
-> There appears to already be a driver installed on your system (version: 1.0-
5336). As part of installing this driver (version: 1.0-5336), the existing
driver will be uninstalled. Are you sure you want to continue? ('no' will a
bort installation) (Answer: Yes)
-> Not probing for precompiled kernel interfaces.
-> Kernel source path: '/lib/modules/2.6.3/build'
-> Performing cc_version_check with CC="cc".
-> Cleaning kernel module build directory.
executing: 'cd ./usr/src/nv; make clean'...
rm -f -f nv.o os-agp.o os-interface.o os-registry.o nv.o os-agp.o os-interfa
ce.o os-registry.o nvidia.mod.o
rm -f -f build-in.o nv-linux.o *.d .*.{cmd,flags}
rm -f -f nvidia.{o,ko,mod.{o,c}} nv_compiler.h *~
-> Building kernel module:
executing: 'cd ./usr/src/nv; make module SYSSRC=/lib/modules/2.6.3/build'...
HOSTCC scripts/fixdep
HOSTCC scripts/split-include
HOSTCC scripts/conmakehash
HOSTCC scripts/docproc
HOSTCC scripts/kallsyms
CC scripts/empty.o
HOSTCC scripts/mk_elfconfig
MKELF scripts/elfconfig.h
HOSTCC scripts/file2alias.o
HOSTCC scripts/modpost.o
HOSTLD scripts/modpost
HOSTCC scripts/pnmtologo
HOSTCC scripts/bin2c
SPLIT include/linux/autoconf.h -> include/config/*
*** Warning: Overriding SUBDIRS on the command line can cause
*** inconsistencies
CC arch/i386/kernel/asm-offsets.s
CHK include/asm-i386/asm_offsets.h
echo #define NV_COMPILER "`cc -v 2>&1 | tail -n 1`" > /tmp/selfgz362/NVID
IA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv_compiler.h
CC [M] /tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.o
In file included from include/linux/sched.h:23,
from include/linux/module.h:10,
from /tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/
nv/nv-linux.h:52,
from /tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/
nv/nv.c:14:
include/linux/smp.h:33: error: conflicting types for 'smp_send_reschedule'
include/asm/smp.h:41: error: previous declaration of 'smp_send_reschedule' w
as here
include/linux/smp.h:33: error: conflicting types for 'smp_send_reschedule'
include/asm/smp.h:41: error: previous declaration of 'smp_send_reschedule' w
as here
/tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c: In function `
nvos_malloc_pages':
/tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c:385: warning:
use of cast expressions as lvalues is deprecated
/tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c: In function `
nvos_create_alloc':
/tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c:513: warning:
use of cast expressions as lvalues is deprecated
/tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c:523: warning:
use of cast expressions as lvalues is deprecated
/tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c: At top level:
/tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c:1185: warning:
initialization from incompatible pointer type
/tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c: In function `
nv_alloc_file_private':
/tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c:1193: warning:
use of cast expressions as lvalues is deprecated
/tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c:1204: warning:
use of cast expressions as lvalues is deprecated
/tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c: In function `
nv_kern_open':
/tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c:1265: warning:
use of cast expressions as lvalues is deprecated
/tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c: In function `
nv_kern_ctl_open':
/tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.c:1914: warning:
use of cast expressions as lvalues is deprecated
make[3]: *** [/tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv/nv.o]
Error 1
make[2]: *** [/tmp/selfgz362/NVIDIA-Linux-x86-1.0-5336-pkg0/usr/src/nv] Erro
r 2
nvidia.ko failed to build!
make[1]: *** [module] Error 1
make: *** [module] Error 2
-> Error.
ERROR: Unable to build the NVIDIA kernel module.
ERROR: Installation has failed. Please see the file
'/var/log/nvidia-installer.log' for details. You may find suggestions
on fixing installation problems in the README available on the Linux
driver download page at www.nvidia.com.

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.

MTS, Killing the user session?

My db is using MTS connection, while i kill the user session by using alter system kill session, the ever killed process goes to Pseudo status....even i can't kill from unix level because it uses dispatchers...
is there any way i kill the user processes in MTS, with out going to pseduo status

Hi,
AS ORACLE SAID,
If an active session cannot be interrupted (it is performing network I/O or rolling
back a transaction), the session cannot be terminated until the operation completes.
In this case, the session holds all resources until it is terminated. Additionally, the
session that issues the ALTER SYSTEM statement to terminate a session waits up to
60 seconds for the session to be terminated. If the operation that cannot be
interrupted continues past one minute, the issuer of the ALTER SYSTEM statement
receives a message indicating that the session has been "marked" to be terminated.
A session marked to be terminated is indicated in V$SESSION with a status of
KILLED and a server that is something other than PSEUDO.

Kill all oracle session

Situation:
Oracle Forms 9i application, with multiple oracle forms (MDI). When I call a new forms I use OPEN_FORM(v_cm_module, ACTIVATE, session, pl_id) so I create a new oracle session.
Problem:
The user open a lot of windows (oracle forms .fmx with diferent sessions each one) in the oracle forms application, when they close the browser window (X botom of the browser, mozilla, internet explorer), the session are still alive (only kill one session....the first I think).
I know that after 15 minutes oracle kill the rest of the sessions, but if the user was editing a block (locking a record), and close the browser, the table still lock 15 minutes!!!!.
Any sugestions:???
Thanks

Is it necessary to create a session for each form?
If so you could do the following:
in the formsweb.cfg set the seperateframe property on true; and place some JavaScript code into the htmlafterform property:
HTMLafterForm=<script type="text/javascript"> window.moveTo(-10000, -10000); </script>
now you have a seperate frame, the browser window gets moved to a position where you can't see it ;-). when clicking the X button in the seperate frame the current form will be closed; your MDI application is still running...if you wan't you can write a JavaBean, and get the windowlisteners of the seperate frame and replace them with your own...of course you can close the Browser by right clicking and closing it in the taskbar; but that's a thing you must live with...
besides that I have no clue how to get rid of those sessions, as I don't you have any event you can act with when closing the Browser. But if so you could save every sid in every when-new-form-instance trigger (you can get it from v$mystat), and when this event occurs you could kill all those sessions (alter system kill session ....) ;-). but as far as I know that's not possible...
regards
christian

Looking for a script to kill all inactive sessions

Does anyone have a script to kill all INACTIVE sessions (with EXECUTE IMMEDIATE)?

I suggest you to specify which OS you are talking about.
The inactive status on the V$SESSION doesn't mean the user is not doing any thing, it only means the oracle server process is not processing any thing by the time it was queried. On OLTP systems Oracle Server Processes remain INACTIVE for more than 95% of the time, so it is advisable to configure shared servers.
If you are really concerned about idle time, then I suggest you to configure profiles.
On the pool mechanism you should address the microsoft side, if this, as far as I understood and guessed, application server is IIS.
I suggest you further reading on the Killing sessions script and different session status (check the sniped status) here:
Re: session inactive ??
Re: make a job to delete the sniped sessions
Re: How do I put a timeout in my DataBase?
Re: Killing Session with Locks in Linux
~ Madrid

Killing Duplicate database session

Hi
We are running an Oracle 8i database. Remote users logon onto the database. The line drops and they lose connection. When the line is up again, they reconect successfully. However, there are now two sessions for this user. What can I do to identify the older session on the database for users and kill the older session.
Thanks

alter system kill session 'sid,serial#';
alter system kill session '243,14563'; -- USE THIS
-- find the session from V$session table and kill the session using SID and SERIAL
-- check the logon_time to find the older sessions
select sid,serial#,username,terminal,osuser,program,type,status,last_call_et,logon_time
from V$session
where type = 'USER'and username not like '%SYS%';
Hope this will help.
Regards
Asif Kabir

IEnterpriseSession.logoff does not kill the web session

Hi,
i can reproduce the following problem in my application also with the
BusinessObjects Enterprise Java SDK Sample JSP Application.
- start the application
- select Schedule And View Web Intelligence Documents
- Login with user A
- View a Webi Report
- Logoff
- select Schedule And View Web Intelligence Documents
- Login with user B
- View the same Webi Report
The second call of the Webi Report with openDocument.jsp will takeover the
web session of the first call
and create the report with user A.
Only closing the whole Internet Explorer helps.
So my assumption is that IEnterpriseSession.logoff kills only the enterprise
session and not the web session.
Any help?
regards
Gordon

Hi, Gordon,
You are correct in that IEnterpriseSession.logoff kills only the enterprise session and not the web session.
When using openDocument.jsp, the only thing in the URL that changes between calls are the parameters (everything after openDocument.jsp). Because of this, the browser sees it as a cache hit and re-uses the credentials it already has. The only way to get it to use different credentials is to exit the browser and reload it. Opening new windows from the current browser isn't good enough.
There's an SAP Knowledge Base Article about this:
[1384047 - OpenDoc Is Not Using the Correct Logon Token|https://service.sap.com/sap/support/notes/1384047]
It's a little involved, but basically it says that this is expected behavior and that the only way around it is to change your code to use the Enterprise SDK instead of openDocument and to manage the logon tokens yourself.
Hope this helps.
Bryan

Users to kill their own sessions queries?

Hello is it possible to allow users to kill just their own queries sessions within their own DB and not grant on higher server level? Thanks in advance.

As mentioned you Requires the ALTER ANY CONNECTION permission. ALTER ANY CONNECTION is included with membership in the sysadmin or processadmin
fixed server roles.
http://msdn.microsoft.com/en-us/library/ms173730.aspx
So you would do this:
use master
go
GRANT ALTER ANY CONNECTION TO TheUserName;
Raju Rasagounder Sr MSSQL DBA

Wine kills my X session

Similar Messages

Maybe you are looking for