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: A VLDB contest

oracle l bounce


>>>If you enable 10046 trace while doing the scan, you should
>>>see your server process occasionally waiting on SQL*Net
>>>message to/from client events against the ASM instance,
>>>while it's scanning through the table. These are the ASM
>>>metadata fetches.

right. I was looking at some stats from one of our buddies over
on the Oak Table and he showed the extant array values from all 4
instances on a 4 node cluster. Instance 4 had 10x more ASM extent
array size than the largest of the other 3 instances. I'm sure
we've all measured the failover impact of being
cache-cold on over 1GB of extent array cache that has to be
fetched over 1Gb right in the event of a RAC failover? What if that
forces a shared pool extention? What if that causes other shrinkage?

I started testing this very aspect yesterday so the questions are
rhetorical :-)