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: How to reproduce an ORA-7445?

Mladen Gogala

2006-12-20

Replies:
How about sennding signal 4 (illegal instruction), 8
(floating point exception) or 11 (segmentation violation) to
an oracle process of your choice? The ORA-7445 error is
generated from within a signal handler. If oracle process
receives an external signal that it cannot handle, it will
generate ORA-7445. That way of generating signals will keep
Oracle developers occupied for a while, as they will
frantically trie to reproduce the phantom menace causing the
signal.

-----Original Message-----
From: oracle-l-bounce@(protected)
[mailto:oracle-l-bounce@(protected),
Rich
Sent: Wednesday, December 20, 2006 11:51 AM
To: oracle-l@(protected)
Subject: How to reproduce an ORA-7445?

Hey all,

In our migration of a new ERP system in 10.2.0.2.0 on AIX, a
user hit an
ORA-7445 (with no parameters!). I file an SR, upload the
resulting
trace file, troubleshooting happens, and it's determined
we've hit a BUG
due to issues with NLS translation of dates in binds. I'm
then told
that unless we can reproduce the problem, there will be no
patch.

Setting aside my knee jerk of steam shooting out my ears, I
started
thinking about this situation. Applying the logic that it's
only a bug
if it can be reproduced, I believe the only way I can
attempt to
accomplish that is to trace every session, either at the
client or the
server, just in case it errors out in the future. And even
then, that's
hardly guaranteed, as the issue could depend on factors only
existing at
the time of the original error (e.g. SGA status, OS memory,
etc).

So what's the point of filing an SR unless the problem is
100%
reproducible? I'm not trying to be sarcastic, just
pragmatic.

TIA,
Rich

"It's a Christmas Miracle!" -- Jenny Meyer, Better Off Dead
--
http://www.freelists.org/webpage/oracle-l


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