RE: 10.2 listener won't start on same port as 9.2 listener

From: "Goulet, Dick" <DGoulet@xxxxxxxx>
To: <MGogala@xxxxxxxxxxxxxxxxxxxx>, <JayMiller@xxxxxxxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
Date: Wed, 21 Sep 2005 11:28:37 -0400

The advice I got from OTS some years ago, like with the release of 8.0,
was to use one listener for all databases on a single server, just use
the latest listener installed as they were backwards compatible.  That
advice has been working extremely well ever since.  So my question would
be why do you want a separate listener, unless you've got two or more IP
addresses, and consequently NIC's, for one server?

  _____  

From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Gogala, Mladen
Sent: Wednesday, September 21, 2005 11:20 AM
To: 'JayMiller@xxxxxxxxxxxxxxxx'; oracle-l@xxxxxxxxxxxxx
Subject: RE: 10.2 listener won't start on same port as 9.2 listener



Oracle is, quite obviously, listening to my advice, even if some listers
are not.

 

--

Mladen Gogala

Ext. 121

  _____  

From: JayMiller@xxxxxxxxxxxxxxxx [mailto:JayMiller@xxxxxxxxxxxxxxxx] 
Sent: Tuesday, September 20, 2005 6:07 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: 10.2 listener won't start on same port as 9.2 listener

 

Well, I just got the answer from Oracle and apparently 10.2 is purposely
not allowing you to do this any more.  It was done as a fix for another
bug and this behavior will be backported to earlier versions in future
releases.

 

Looks like we're going to have to go with a single listener, like it or
not.

 

Sigh.

Follow-Ups:

Re: 10.2 listener won't start on same port as 9.2 listener
From: Richard Ji

RE: 10.2 listener won't start on same port as 9.2 listener

Other related posts: