Thanks everybody for your input/thoughts. Currently I login to the specific instance by having appropriate entries in my TNSNAMES and use it only when I need to do such instance specific task. Otherwise, I use the service name. Another such requirement was for OWB runtime service, which needed to be running only on the given instance and not use any available instance - don't ask me why. (I am not an expert on OWB) On 4/13/07, Tanel Poder <tanel.poder.003@xxxxxxx> wrote:
Hi, Write a pl/sql daemon which runs in every instance, wakes up once per minute and scans for a shared table for insance, sid and serial# combination to kill. If it finds anything matching local instance ID, it kills that session(s). So if you need to kill something, you insert the instance_id, sid and serial# to the shared table, commit and wait for a minute :) Tanel. ------------------------------ *From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto: oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *rjamya *Sent:* Friday, April 13, 2007 20:25 *To:* WLJohnson@xxxxxxxxxxxxxxxxxxx *Cc:* kaygopal@xxxxxxxxx; shivaswamykr@xxxxxxxxx; Oracle-L Freelists *Subject:* Re: KIll Session in - RAC DB That you can do simply by selecting from gv$session. Killing session on _other_ instance is a different story, and is not possible until 11g. rjamya On 4/13/07, Johnson, William L (TEIS) <WLJohnson@xxxxxxxxxxxxxxxxxxx> wrote: > > I do know that Quest's TOAD software shows you all sessions > in a RAC environment while using their session browser utility... >