All Oracle Error Codes
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

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



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,

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:

listener_rtb =
    (ADDRESS = (PROTOCOL = TCP)(HOST = usnjc01urp004)(PORT = 1526))

SID_LIST_listener_rtb =
   (ORACLE_HOME= /oracle/rtbp/product/9.2.0)
   (SID_NAME = rtbp)
   (ORACLE_HOME= /oracle/mds/product/10.2.0)
   (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.

Jay Miller

-----Original Message-----
From: Mark Bole [mailto:makbo@(protected)]
Sent: Tuesday, September 20, 2005 10:24 AM
Cc: oracle-l@(protected)
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?

Mark Bole


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.