RE: v$session with same serial#
From: Saibabu Devabhaktuni <saibabu_d_at_yahoo.com>
Date: Wed, 23 Jan 2013 18:52:34 -0800 (PST)
Message-ID: <1358995954.20052.YahooMailNeo_at_web161304.mail.bf1.yahoo.com>
I believe serial# is incremented every time same session id is established again on the database. All sessions come from the fixed session state array as defined by sessions init parameter. All sessions start with serial# being 1 and they get incremented each time the same slot is reused. This is the reason why core background processes have serial# 1.
Date: Wed, 23 Jan 2013 18:52:34 -0800 (PST)
Message-ID: <1358995954.20052.YahooMailNeo_at_web161304.mail.bf1.yahoo.com>
I believe serial# is incremented every time same session id is established again on the database. All sessions come from the fixed session state array as defined by sessions init parameter. All sessions start with serial# being 1 and they get incremented each time the same slot is reused. This is the reason why core background processes have serial# 1.
18:30:38 SQL> select sid, serial# from v$session where sid=sys_context('USERENV','SID');
SID SERIAL#
----- ----------
1419 11995
18:30:42 SQL> exit
oracle_at_testdb > sqlplus /
18:30:47 SQL> select sid, serial# from v$session where sid=sys_context('USERENV','SID');
SID SERIAL#
----- ----------
1419 11997
Thanks,
Sai
http://sai-oracle.blogspot.com
-- http://www.freelists.org/webpage/oracle-lReceived on Thu Jan 24 2013 - 03:52:34 CET