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

Hemant K Chitale


At 08:11 AM Wednesday, Allen, Brandon wrote:
>Here is another test indicating that a direct-path insert to a nologging
>index is actually logged (like Jared has also shown), which is contrary to
>the documentation.
>Notice that both the table and the index are created as NOLOGGING, but the
>tablespace containing the index (TOOLS) only gets marked as unrecoverable
>at the time of the index creation (16:42) and the unrecoverable time is
>not updated after the direct-path insert, whereas the tablespace
>containing the table (SYSTEM) *does* have its unrecoverable time updated
>at the time of the direct-path insert (16:48). So, it appears the table
>changes are not logged, and therefore are unrecoverable as would be
>expected, but the index changes *are* still logged and therefore the index
>is recoverable, contrary to the documentation:

Yes, of course. Even if you marked the Index NOLOGGING the Index Updates
were NOT bulk updates -- to the
Index they are regular DML. They will be LOGged. {The Index Create was a
NOLOGging operation, correctly}

Hemant K Chitale