ORA-12535 TNS:Operation Timed Out

From: SJelle <sjelle_at_aol.com>
Date: 1995/08/07
Message-ID: <40466s$etv_at_newsbf02.news.aol.com>#1/1


We have a project which is trying to setup an emulation of 400 sessions to a database. When about 200 session have connected of the oracle database, sessions start receiving the ORA-12535 error.

We are using MTS.

The queue times for dispatchers and shared servers are not long enough (< sec.) for the 120 second timeout set in the listener.ora.

What is happening?
Can a listener handle over 200 concurrent active sessions to a database? Do I have enough dispatchers configured? Would I get this error is the problem is really network saturation? Here is some of the parameter settings from the last run:
LISTENER_CONNECT_TIMEOUT= 120 (listener.ora)

init.ora stuff:

mts_servers=30
mts_max_servers=100
mts_dispatchers=tcp,50

Other info:
I have about a 1.3 Gig sga with 1Gig shared_pool_size. I am using 7.1.4 Oracle, V2 sqlnet on a sequent with 12 processors and 768Meg of Mem.

Thanks for the help,
Steve

Work: jelles_at_ihub.ea.unisys.com
Home: sjelle_at_aol.com Received on Mon Aug 07 1995 - 00:00:00 CEST

Original text of this message