Re: Server refuses to start MTS/Shared connection

andreyNSPAM_at_bookexchange.net (NetComrade) wrote in message news:<40e1d8d2.696633415_at_localhost>...
> I have 2 non-production databases than run on the same server. Both
> are 8.1.7.4. Both configured very similarly. All parameters are very
> similar, except for some memory variables and SID specific variables.
> Each has a corresponding listener listening on a different port
> (1521/1524); listener is always started first (although, this might be
> necessary anymore). The sid's are DEV1 and PROD.
>
> The machine connecting to them has entries that are identical in
> tnsnames.ora file, except for SID/port (tried service_name too).
> However, DEV1 accepts shared/MTS connections, but PROD doesn't. The
> listener shows that dispatchers are registered with it. When I try to
> 'foce' MTS connection by setting SERVER=MTS, connection goes through,
> but goes through as DEDICATED (checked through v$session). In fact, a
> quick query of mts views shows that no mts connection has ever been
> made (listener services confirms that as well).
>
> I am lost.. what to do? I tried to do TNS tracing, but can't make much
> of it.
>
> Thanks for any help
> .......
> We use Oracle 8.1.7.4 on Solaris 2.7 boxes
> remove NSPAM to email

Andrey,

gotcha covered. (8.1.7.4 at the time)
I never really needed 2 listeners on a server except for one particular time.
as a benchmark, a site was going to have 100 users login at the same time, 2 sessions each via a fat client, 2 tiered app. actually, I didn't know that they were going to perform this test, I heard about it after they attempted it. (this was not my call) It was analogous to benchmarking the onramp to a 4 lane freeway, not the interstate itself.

we were using dedicated server connections on a platform that did not support pre-spawning of sessions.
4 cpu server, 1 listener, unsuccessful test. 4 listeners, sucessful test.

the key thing here is to use dynamic registration, but have the instance (pmon) register with all the listeners. this is what the parameter local_listener is for. prepare a tns alias for all of your listeners, fully qualified, e.g. "all_listeners.mydomain.com" in your tnsnames.ora file for the oracle home for both your instance and your listener home (in case they are different).

in the init.ora set:

local_listener=all_listeners.mydomain.com

the instance will dynamically register with all the listeners. the listeners will know about the dispatchers.

it worked for me - can provide more detail tomorrow (wed) if you like.

Pd Received on Wed Jun 30 2004 - 00:10:16 CDT