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: is it possible in pl/sql?

Singer, Phillip (P.W.)



>Mark Bole wrote:

>Hmmm.. from "Oracle Performance Tuning 2nd edition" (Gurry and=20
>O'Reilly Press, 1996) -- so were talking version 7 RBO here:
>"Contrary to popular belief, COUNT(*) is faster than COUNT(1). If the=20
>rows are being returned via an index, counting the index column--for=20
>example, COUNT(EMP_NO) is faster still. [followed with actual=20
>test runs=20
>including timings to prove this]"
>So, for the sake of historical accuracy (and not much else), there is=20
>some evidence that a long time ago the count(*) performance=20
>issue existed.
>-Mark Bole

What is interesting is that it is contrasted with a select count()
against a column on which a unique index exists - which is shown to be
quicker still. Which suggests that (at that time at least) the
optimizer was not smart enough to find and use a unique index without
lots of help.

I also remember about that time finding advice on Metalink to do a
count(*) on a table if one was getting ORA-01555's due to delayed block
cleanout - this was supposed to be the 'best' way to force every block
to be read.