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: Streams

Remigiusz Sokołowski


Job Miller wrote:
> if you are trusting of the auto memory management stuff, the streams
> pool is now self adjusting in 10gR2, so that you shouldn't see these
> kind of errors. It *should* borrow memory from other pools to satisfy
> these moments of increased use during PQ operations.
> Job

Well, I suppose this may be a little controversial, but
we used auto memory management and came to conclusion it is a major
source of some of our problems.
The idea is fine and we suppose it works great for instances with less
turbulent memory structure changes
However since we started with ASMM, we experienced several major server
failures, while working with static settings it was not the case.
Of course now we have to bounce server to change settings, but still it
is better to have a control over shutdown process.


Remigiusz Sokolowski <rems@(protected)>
WP/PTI/DIP/ZAB (+04858) 52 15 770
MySQL v. 4.x
Oracle v. 10.x