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?

oracle l bounce


Hey Brandon,

Good point! I should have also stated that since this is a migration
database, there is only about 5-10% of the total number of expected
concurrent production users on it right now. I'm trying to head off
what could very well be a major showstopper come go-live.

Thanks for the feedback!

-----Original Message-----
From: Allen, Brandon [mailto:Brandon.Allen@(protected)]
Sent: Wednesday, December 20, 2006 11:08 AM
To: Jesse, Rich; oracle-l@(protected)
Subject: RE: How to reproduce an ORA-7445?

Probably not much point at all because they're always going to ask for
it to be reproduced with tracing on and as a DBA that provides tech
support myself, I usually find myself in the same position. It's often
very difficult if not impossible to troubleshoot a problem that can't be
reproduced and on top of that, there is the issue of triage - how much
time are you going to spend working on a problem that can't even be
reproduced when you've got 10 other fires to fight. If it can't be
reproduced, then chances are it won't be a problem again anyway so your
time would be better spent elsewhere. Of course, if it does end up
recurring, hopefully the next time you will have a better idea of what
to look for and compare with the first occurrence to see what the exact
conditions were that caused the problem - and each time you will
hopefully get closer to being able to reproduce it.


-----Original Message-----
From: oracle-l-bounce@(protected)

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