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

To set events or not set events, that is the question

Jesse, Rich


Replies: on HP/UX 11.11, newly created from an export. After a week of uptime, we get an ORA-1555 today. The alert.log says:

ORA-01555 caused by SQL statement below (Query Duration=8581 sec, SCN:0x0000.0090c189):

...followed by what I'm hoping is a partial statement (because it's a nasty FTS):


(schema/table/column names changed to protect the innocent). Now any query that takes 2+ hours to complete during the day on our nice new fast server *deserves* to die a horrible ORA-1555 death, IMHO, but I'd still like to be able to track these down in the future. And without a trace file generated, that's just not gonna happen.

So, I'll set event 1555 as an errorstack. But the last time I did this, then had a Support call a year later, I was told that setting events permanently like this is not a good idea, although I was not able to find out *why* it's not.

I've got a TAR open to get the Official Word, but does anyone have a good reason why this or other "error" event (like 1652 to determine who the hell used up 2GB of TEMP) should NOT be in an init.ora for any version of Oracle???


Rich Jesse                  System/Database Administrator
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