RE: MTS v$session

[Wiegand, Kurt]

Title: MTS v$session

Yes; at least on the server side.

 

 

# SQLNET.ORA Network Configuration File: /u01/app/oracle/product/817/network/admin/sqlnet.ora
# Generated by Oracle configuration tools.
 
#NAMES.DIRECTORY_PATH= (TNSNAMES)
SQLNET.EXPIRE_TIME= 10

-----Original Message-----
From: Nuala Cullen [mailto:[EMAIL PROTECTED]
Sent: Friday, August 01, 2003 12:34 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: MTS v$session

Hi Kurt,

 

Have you set the sqlnet.expire_time in the sqlnet.ora file?

 

N.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Wiegand, Kurt
Sent: 01 August 2003 16:19
To: Multiple recipients of list ORACLE-L
Subject: MTS v$session

I've got an 8.1.7.4.0 instance running under Solaris 2.8.

I've never worked with MTS before, but got a call from a user telling me that there
were about 700 rows in v$session but they only had about 130 sessions open.
The user believes that  when the session is ended, v$session doesn't (or doesn't always)
get cleaned up.  Does anyone have any insight into this?  Thanks.

I checked v$process and had about 89 rows, which matched exactly to the 89 unix processes that I had on the box.

I looked at paddr in v$session and saw that there were just over 100 rows pointing to each of the 6 dispatchers.
The other rows each had their own dedicated process.

I checked v$dispatcher and saw the 100+ values in the OWNED column, but also saw values between 300 - 450 in
the CREATED column.
               
I really don't know whether the application ends it's connections gracefully or nongracefully.

Kurt Wiegand      Cable & Wireless Communications      703 292-2115