Home
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: ORA-4031

Mogens Nørgaard

2006-05-09

Replies:

Have you all noticed how certain errors come and go throughout the ages
and versions? The memory leak, which can be fixed with an event, the
4031, which has been permanently fixed in every single release of Oracle
since 7.0, and others.

The root causes stay the same, though. Go back to the docs from when the
problems were thoroughly detected, diagnosed and repaired and you will
find ever-green advise for 4031-handling...

I'm not saying there couldn't be some new and exciting reason for 4031,
but mostly it's the same old, same old.

Mogens


Joe Armstrong-Champ wrote:

> Tracy,
>
> We upgraded a database from 9i to 10gr2 on aix 5.2 last weeek and got
> a 4031 which killed an etl process that runs daily. I'm not the dba
> working on the problem but I know that 1 of the fixes is to increase
> the data limit (ulimit -d). That seemed to help somewhat but not
> entirely. The dba who is working on it is also playing with some sga
> parms. I'll pass your info to her to see if it helps.
>
> Joe


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