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: ORA-1578...block corrupted...error is normal...a block...had a NOLOGGING...operation performed against

Joel Garry


Chris Marquez wrote:

>I can NOT believe the if I used NOLOGGING to create and INDEX "long
ago" *and*
>many, many subsequent FULL BACKUPS that it could/did effect or error on
future recovery?

>Again, we are getting this error after full db recovery on indexes
>(NOLOGGING), well before the FULL backup and thus no "NOLOGGING"
objects in any
>of the arch logs applied...what gives?

Believe it. Time bomb sat there since long ago. Nologging operations
bypass the redo logs. So they bypass the archived logs. So when you
restore the datafile by rolling forward, you invalidate those blocks.
So you have to fix them with some other mechanism than recovery. Maybe
use force logging if you don't want to run into this again. And all
that advice about taking a backup after nologging operations seems
pretty misleading, huh?

In the end, surely you realize that you, the DBA, are taking
responsibility for _any_ previous nologging operations in the case of

Joel Garry