Quote Originally Posted by PAVB
Dear pareshjavkar --
When I'm not sure or I just "don't know" I usually restrain myself of doing any random-typing.
When facing a question the best thing you can do is to give a valid answer, clear and to the point.
The second best thing you can do is "nothing".
What you do... random-guessing-typing doesn't help much
You are not getting paid by the answer so... just let go the ones you have no clue about ;-)

PS: I'm in this thread just to keep you honest

Dear PAVB,

Try this out, Login from 10 to 15 sessions with the same username into the database.

Create a dynamic sql to kill the session, See below how to ...

SELECT 'ALTER SYSTEM KILL SESSION ' ||''''||SID||','||SERIAL#||'''' ||' ;' FROM v$session WHERE USERNAME NOT IN ('SYS') and username is not null and status='ACTIVE';

execute the sql generated.

QUICKLY do the following from the other SQL prompt: (and do it QUICKLY)

SQL> select username, sid, serial# from v$session where username='one of which you killed';

You might get two replies by SQL prompt:

"session marked for kill"

or the one which Aditya is facing above i.e. (i hope you know what error he got).

The above is technical aspect, now let me tell, if you look into the things very minutely, which i think you should start doing, showing the direction towards the solution MIGHT lead to some solution (maybe correct or incorrect), but typing NOTHING will surely lead you nowhere, will stand where you are.

P.S: Thanks for accepting HONESTLY you don't know anything about Aditya's problem. I appreciate