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

Allen, Brandon


Where in the documentation do you see a description of this different treatment of the NOLOGGING clause for CREATE vs. ALTER statements?
My understanding from the documentation, including that which you have included in your email below, is that when specifying NOLOGGING during either the CREATE or ALTER of an object, the creation/alteration of the object as well as any future direct loads/inserts are minimally logged.  If you see something contrary to this in the documentation, please provide a link.
P.S.  in case anyone else tries to look it up - the correct Metalink note # is 147474.1
-----Original Message-----
From: Hemant K Chitale [mailto:hkchital@singnet.com.sg]
Sent: Tuesday, August 23, 2005 8:56 AM
To: jkstill@gmail.com; Allen, Brandon
Cc: cmarquez@collegeboard.org; oracle-l@freelists.org
Subject: Re: ORA-1578...block corrupted...error is normal...a block...had a NOLOGGING...operation performed against


You ARE right.  You really don't need to retest it. 
When an object is NOLOGGING is used in the CREATE statement, it is the actual first load that the create does
that is NOLOGGING.  All subsequent DML is logged.
When an object is ALTERed to NOLOGGING,  only certain statements (eg APPEND) that support NOLOGGING
are NOLOGGed.
Read the extract that Allen has quoted "Direct Loader .. and direct path insert".  It specifically talks of Direct
operations  NOT regular DML.  Regular DML is always always LOGged.

Again, quoting from the 9i SQL Reference  on the logging clause :  This also says " .. subseqent direct .. direct ..."
NOT regular DML.




The logging_clause lets you specify whether creation of a database object will be logged in the redo log file (LOGGING) or not (NOLOGGING).

This clause also specifies whether subsequent Direct Loader (SQL*Loader) and direct-path INSERT operations against the object are logged (LOGGING) or not logged (NOLOGGING).

You can specify the logging_clause in the following statements:
You can also specify LOGGING or NOLOGGING for the following operations:
  • Rebuilding an index (using CREATE INDEX ... REBUILD)
  • Moving a table (using ALTER TABLE ... MOVE)

Data Dictionary Updates are always logged.  Regular DML is always logged.

Note 17474.1 , from Oracle7 and Oracle8  days is still the best reference.

   The following operations can make use of no-logging mode:

        direct load (SQL*Loader)
        direct-load INSERT
        INSERT, UPDATE, and DELETE on LOBs in NOCACHE NOLOGGING mode stored out of line

At 11:40 PM Tuesday, Jared Still wrote:
I will rerun my tests and post the results to the list.

If there is a flaw in my testing procedure someone here
is sure to spot it.

Won't be able to do so until this afternoon however.


Hemant K Chitale

Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it.