No, the key is different. I'm using the exact same listener.ora that I did
for the 10.1 instance with the exception of the different ORACLE_HOME. I
differentiate the keys by adding the instance name (e.g., KEY = EXTPROCAAA,
KEY = EXTPROCBBB, KEY = EXTPROCCCC).
I'll speak with the SAs about running netstat --listening tonight.
I didn't try turning off both other listeners and then restarting all three
but when I refreshed from my 10.1 backup the listener started up with no
Regarding the last question, see my response to Mladen.
One additional note on something I tried after sending the email to the
list. I tried adding the 10.2 instance to one of the 9.2 listeners
(figuring I could run that way on a temporary basis) and while the listener
came up I was unable to connect.
This was the entry:
(ADDRESS = (PROTOCOL = TCP)(HOST = usnjc01urp004)(PORT = 1526))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROCRTB))
(SID_NAME = rtbp)
(SID_NAME = mdsdb)
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /oracle/rtbp/product/9.2.0)
(PROGRAM = extproc)
This was the error I got when I tried to connect through the listener:ORA-12500
: TNS:listener failed to start a dedicated server process
I'm wondering now if the fact that I have PROGRAM = extproc but KEY =
EXTPROCRTB could possibly be an issue? Something else to try once the
developers release the box to me tonight.
From: Mark Bole [mailto:makbo@(protected)]
Sent: Tuesday, September 20, 2005 10:24 AM
Subject: Re: 10.2 listener won't start on same port as 9.2 listener
Have you tried the above step first? Note that ADDRESSes are not
limited to TCP protocol. Perhaps you have a conflicting IPC key? What
are the results of the "netstat --listening" command run as root?
Break the problem down through process of elimination. Double-check
your ORACLE_HOME settings when starting each listener. Eliminate all
but one ADDRESS for each listener, and then add them back in one at a time.
But, as Mladen stated, there is rarely a reason to run more than one
listener per machine. Why do you need to do this?
This message is confidential and sent by TD Waterhouse solely for use
by the intended recipient. If you are not the intended recipient, you
are hereby notified that any use, distribution or copying of this
communication is strictly prohibited. This should not be deemed as an
offer or solicitation, to buy or sell any product. Any 3rd party
information contained herein was prepared by sources deemed reliable,
but is not guaranteed. TD Waterhouse does not accept electronic
instructions that would require an original signature. Information
received by or sent from TD Waterhouse is stored, subject to review,
and may be produced to regulatory authorities or others with a legal
right to such.