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?

Andrey Kriushin


Sorry for late joining and with a little bias to the NLS conversions

Are you using NCHAR/NVARCHAR2/NCLOB types in your binds?
We had some issues with NCLOB in or 6 (don't remember exact
version). The diagnostics was ORA-00600 with no arguments.

What was discovered while working on SR is that when converting from
NCLOB (or probably NVARCHAR) to main characterset of database, the
server process had simply (i.e. without any latching/locking)
overwritten some areas in the SGA, where NLS structures were stored,
with the values pertinent to national characterset. Of course, these
structures were restored to their original values when the conversion
was completed. But in the middle of the conversion the other sessions
sometimes got that ORA-600 without arguments.

Thanks to Kyle Hailey for his ksuse.c. This approach allowed us to catch
those memory overwrites and construct the "reproducible test case".


Jesse, Rich wrote:
> Hey all,
> In our migration of a new ERP system in 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.