-
NONE instead of SHARED in field SERVER in V$SESSIONS in dd view
why is it that the SERVER field in v$sessions for client connections still NONE instead of SHARED in MTS environment?
my DB is ORACLE 9.2.0.1 under sun v880 solaris 9
the background processes are DEDICATED
sqlplus connections are SHARED
but the rest are NONE
I did used once ONAMES and I was thinking maybe it is
because of ONAMES that the MTS cannot identify the connection.
But the when I remove the ONAMES and used purely the TNSNAMES
still the value of SERVER field is NONE.
and my mts setup is:
mts_dispatchers=(protocol=TCP)(DIS=5)(SERVICE=myservname)
mts_max_servers=20
mts_max_dispatchers=5
mts_service=myservname
-
When the session is idle, it will be "NONE". When its active, it will be "SHARED".
Jeff Hunter
-
Hey Marist,
Do you mean when there are no users connections or user sessions?
-
Originally posted by cruser3
Hey Marist,
Do you mean when there are no users connections or user sessions?
Neither. When a user is connected via an MTS connection, but is not acively doing something.
Jeff Hunter
-
thanks Jeff and cruser3,
But I don't think this is the case of my database.
I have queried sql stmnt below for so many times, and yet
it produces the same result and to think that I have more
than 25 application tester + about 30 concurrent connections from development team, it's just to impossible to have the same output.
sql stmnt:
select sid, serial#, server, machine, program
from v$session;
I will try later using another attribute of MTS_DISPATCHERS like
DESCRIPTION instead of PROTOCOL and see what happen.
again, thanksalot.
-
Originally posted by reydp
thanks Jeff and cruser3,
But I don't think this is the case of my database.
I have queried sql stmnt below for so many times, and yet
it produces the same result and to think that I have more
than 25 application tester + about 30 concurrent connections from development team, it's just to impossible to have the same output.
sql stmnt:
select sid, serial#, server, machine, program
from v$session;
I will try later using another attribute of MTS_DISPATCHERS like
DESCRIPTION instead of PROTOCOL and see what happen.
again, thanksalot.
Then you must have a unique compilation of the oracle code because that's the way it works for everybody else.
Jeff Hunter
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|