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
rman failure ORA-04030 indicates memory issue

rman failure ORA-04030 indicates memory issue

2004-10-06       - By Joel Garry

Reply:     <<     11     12     13     14  


> ORA-12540 (See ORA-12540.ora-code.com): TNS:internal limit restriction exceeded

You can also get TNS 12540 as a result of too many processes. I would
guess what may be happening is all those aborted RMAN jobs are hanging
onto processes, hence everything is better after bouncing db. Perhaps
you should try upping both the unix and init.ora processes settings to
push the problem back. No reason not to if you aren 't even close to
actual swapping. And take a close look at your listeners. I can 't
recall if Solaris has swapinfo -a. netstat -a |grep WAIT might be
interesting, too, there might be a very long timeout on the extraneous
connections.

Joel =
Garry=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0
http://www.garry.to=20
=A0


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