Links
Home
Oracle DBA Forum
Frequent Oracle Errors
TNS:could not resolve the connect identifier specified
Backtrace message unwound by exceptions
invalid identifier
PL/SQL compilation error
internal error
missing expression
table or view does not exist
end-of-file on communication channel
TNS:listener unknown in connect descriptor
insufficient privileges
PL/SQL: numeric or value error string
TNS:protocol adapter error
ORACLE not available
target host or object does not exist
invalid number
unable to allocate string bytes of shared memory
resource busy and acquire with NOWAIT specified
error occurred at recursive SQL level string
ORACLE initialization or shutdown in progress
archiver error. Connect internal only, until freed
snapshot too old
unable to extend temp segment by string in tablespace
Credential retrieval failed
missing or invalid option
invalid username/password; logon denied
unable to create INITIAL extent for segment
out of process memory when trying to allocate string bytes
shared memory realm does not exist
cannot insert NULL
TNS:unable to connect to destination
remote database not found'>ora-02019
exception encountered: core dump
inconsistent datatypes
no data found
TNS:operation timed out
PL/SQL: could not find program
existing state of packages has been discarded
maximum number of processes exceeded
error signaled in parallel query server
ORACLE instance terminated. Disconnection forced
TNS:packet writer failure
see ORA-12699
missing right parenthesis
name is already used by an existing object
cannot identify/lock data file
invalid file operation
quoted string not properly terminated
10.2 listener won 't start on same port as 9.2 listener

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

2005-09-20       - By Mark Bole

Reply:     1     2     3     4     5     6     7     8     9     10     >>  

JayMiller@(protected) wrote:

> Is anyone else out there running both a 10.2 and a 9.2 listener on the
> same port?  Now that I've successfully upgraded my dev database from
> 10.1 to 10.2 I'm having listener issues (Solaris 2.9).
>
>  
>
> Previously I was running 3 listeners on the same port with no problems
> (2 of them 9.2 one of them 10.1).  When I try to start the listener for
> the 10.2 database it complains that there is already a listener running
> on that port:
>
>  
>
> $ lsnrctl start listener_mds
>
> LSNRCTL for Solaris: Version 10.2.0.1.0 - Production on 19-SEP-2005 20:37:49
>
> Copyright (c) 1991, 2005, Oracle.  All rights reserved.
>
> TNS-01106: Listener using listener name listener_rtb has already been
> started
>
[...]

TNS-01106: Listener using listener name string has already been started
    Cause: Another listener is already listening on one of the
ADDRESSes specified.
    Action: Shutdown the previous listener specified by the listener
name before starting this one.

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?

--
Mark Bole
http://www.bincomputing.com



--
http://www.freelists.org/webpage/oracle-l