Re: MTS problems with NT 8.1.7.4 Standard Edition

Thanks very much for both your replies - both really helpful and it did seem to be dynamic registration that was stopping it working.

I removed all the SID_LIST entries from the listener.ora and nothing would dynamically register until I added the local_listener parameter to the init.ora and added the listener address to tnsnames.ora (I also removed the multiple references to port 1521 in listener.ora) - not sure why this was needed as it does say in the documentation that it isn't required if the default listener name was used, which it was - maybe the fact that I also have an Oracle 7 home on the machine (no services running though, 8i set as the default home) was coming into play here, or the fact its referenced by IP address.

After I had done this and restarted the databases all worked fine - lsnrctl status showed ORA2 as having 5 service handlers and shared server connections, which I intentionally forced for testing purposes, worked!

Howard mentioned that I may have needed the mts_servers parameter but as I was using a very similar init.ora from a machine that already had MTS running I thought it unlikely that this was stopping it (and there was a large_pool parameter, set to 250000000, I just clipped it), but I will look into the benefits of adding it.

Thanks again for your help and very informative replies,

Dom

drak0nian_at_yahoo.com (Paul Drake) wrote in message news:<1ac7c7b3.0305131527.143dbb63_at_posting.google.com>...
> form999v_at_hotmail.com (Dom) wrote in message news:<52400398.0305130302.31dda160_at_posting.google.com>...
> > After installing Oracle on a new machine I can't seem to get MTS
> > working - I've added the relevant lines to init.ora and although
> > querying several v$views would suggest it's working, I can't connect
> > when server=shared is specified in tnsnames.ora (I get ORA-12510:
> > TNS:listener could not find available handler for requested type of
> > server), no problems if its commented out. Any suggestions would be
> > appreciated (more details below, sorry if the output of the sql is
> > hard to read) and I know its unusual to use the ip address but this is
> > a cluster environment with fail over (a second machine picks up the
> > same ip address in the event of failure).
> >
> > Thanks in advance
> >
> > Dom
>
> Dom,
>
> You were using static registration - by using a verbose list in the
> listener.ora. If you were to use dynamic registration, each instance
> registers with the listener at startup, in which case the dispatchers
> would be registered with the listener.
>
> I'd recommend the following - but this is only off of a hunch:
>
> 1. use the parameter local_listener to describe where the listener(s)
> can be contacted. If you are only using 1 listener on port 1521, this
> parameter does not have to be explicitly set.
>
> 2. remove all of the SID_LIST entries from the listener.ora - which
> will enable dynamic registration (keep around your EXTPROC entires if
> they are in use)
>
> 3. stop and restart the listener service via:
>
> C:\> net stop oracleorahome81tnslistener
> C:\> net start oracleorahome81tnslistener
>
> use lsnrctl , SET DISPLAYMODE VERBOSE and examine the listener logs to
> verify that each instance registers with the listener(s) at startup.
>
> If this doesn't get it - email me backchannel.
>
> hth,
>
> Paul
Received on Wed May 14 2003 - 04:13:53 CDT