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

Hemant K Chitale



Yes, that portion of the documentation, if read by itself, is incorrect.

At 11:55 PM Wednesday, Allen, Brandon wrote:
>Hemant, I'm not sure if you've been following the thread the whole time,
>but the issue we are currently addressing is the fact that the
>documentation clearly says that when an index is set to NOLOGGING
>(regardless of whether it was CREATEd or ALTERed NOLOGGING), that
>direct-path inserts will not be logged - see the logging_clause definition
>under the CREATE INDEX page at this link:
>Here is the relevant text:
>Specify whether the creation of the index will be logged (LOGGING) or not
>logged (NOLOGGING) in the redo log file. This setting also determines
>whether subsequent Direct Loader (SQL*Loader) and direct-path INSERT
>operations against the index are logged or not logged. LOGGING is the default."
>So, it appears that the documentation is incorrect - would you agree?

Hemant K Chitale