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: relation shared pool elements phys mem

Tanel Poder


> I have found ?Diagnosing and Resolving ORA-4030 errors? (Note 233869.1).
> There is reference to the EVENT: 10261. It is seems that this event can be
> useful for the purpose that we are discussing.

I've not used 10261 myself, but there's also a _pga_max_size parameter,
which might help you in your case.

> .
> Are you aware, dose heapdump and 10261 works well in MTS env.?

Heapdump should work ok in MTS if you use the following:
event = "4030 trace name heapdump level 1" (or level 4 to get UGA

That way the MTS server process hitting ORA-4030 will write the heapdump to
trace. Of course if you don't get 4030's at all, this won't be of any help..

Otherwise, when taking heapdumps from other processes with oradebug, you
might dump a process too late (or too early), when it already has serviced
your problematic session, thus you might see wrong information...


Please see the official ORACLE-L FAQ: http://www.orafaq.com
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe' in the subject line.
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html