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: Why does a job loose its context?

Mercadante, Thomas F



According to the docs,


Specify SERVERERROR to fire the trigger whenever a server error message
is logged.

The following errors do not cause a SERVERERROR trigger to fire:

  * ORA-01403: data not found
  * ORA-01422: exact fetch returns more than requested number of rows
  * ORA-01423: error encountered while checking for extra rows in
exact fetch
  * ORA-01034: ORACLE not available
  * ORA-04030: out of process memory

So in your case, sql errors would not fire the trigger. I always
thought that this trigger would only fire for things that appear in the
alert log. But sql processing errors would not show up.

Hope this helps.


-----Original Message-----
From: oracle-l-bounce@(protected)
Sent: Thursday, March 02, 2006 11:14 AM
To: oracle-l@(protected)
Cc: mcdonald.connor@(protected)
Subject: Re: Why does a job loose its context?

Speaking of triggers not firing, anyone seen an example of where a
SERVERERROR trigger does not fire?

I was looking an an issue this week where a log file in an app is
reporting a ORA- error (no data found), so we added some logging to
the code and turned on SERVERERROR trigger. I was hoping to get
something like this in my log file.

..entering proc foo...
..ORA- error

However, I never got the ORA- error in my log (the application log
still reports it, but it is possible some developer has hard coded
this particular error string someplace where the error is not really
occurring, strange but possible).

The only other option is that the trigger is not firing, I see errors
for plenty of other sessions in the database. At first I thought it
was because I had the EVENT level elevated for this error and the dump
of a trace file was causing this, but we removed that and still
getting nothing.