Re: ORA-12535 TNS:Operation Timed Out

In article <40466s$etv_at_newsbf02.news.aol.com>, sjelle_at_aol.com (SJelle) writes:
> 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)

I'd say that your listener configuration is not relevant here.

The error (ORA-12535) is being realized and declared completely within the client. In particular what it has meant when we've had this error is that the server was not reachable from the client machine.

--
Mark Pizzolato - INFO COMM Computer Consulting, Danville, Ca
PHONE:	(510)837-5600	UUCP:  decwrl!infopiz!mark
DOMAIN:	mark_at_infocomm.com