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

Mercadante, Thomas F





I was thinking about this whole topic over the weekend.  It just affirms my feeling that using the NOLOGGING option needs to be used judiciously.  And I question how much time we are saving here.


I have now come up with a “NEW RULE” (to borrow from Bill Mahar).


If the total time to reload using NOLOGGING and a total backup is less than a reload with LOGGING and no backup, then don’t use it.


I personally have never liked turning logging off.  I would just as soon deal with the extra archive logs and extra time involved with the restore than what Chris has been dealing with.  There are far too many things happening in a database for me to remember or even know about.  So if *everything* is covered by archive logs, then a recovery will always work.




From: oracle-l-bounce@freelists.org [mailto:oracle-l-bounce@freelists.org] On Behalf Of Jared Still
Sent: Saturday, August 20, 2005 4:18 PM
To: rjsearle@gmail.com
Cc: Brandon.Allen@oneneck.com; cmarquez@collegeboard.org; oracle-l@freelists.org
Subject: Re: ORA-1578...block corrupted...error is normal...a block...had a NOLOGGING...operation performed against



On 8/20/05, rjsearle@gmail.com <rjsearle@gmail.com> wrote:

Forgive me for jumping in here in the middle of a conversation but I can't push  these thoughts from my mind...  Are all of these observations supported by the simple fact the modifications to the data dictionary ARE logged (recursive SQL)  So the entries into the obj$ tables as a result of the new objects would be logged as well as the extent allocation actions.

Yes, the changes to the data dictionary are all logged.


You can see this by the small amount of redo generated even when inserting with append hint that results in a new extent (DMT obviously).  So the block operations on the index may not be logged but the changes to the schema are logged.

Yup.  There's some other stuff in there as well.  A session
with logminer would reveal what is being logged.


Also I consider it unwise to create *persistent* segments use nologging option for exactly this reason.  But indexes can always be rebuilt, but at what cost? (how many days processing?) 

Unless you do direct path loads or use the APPEND hit, all DML will be logged.
If you can save a lot of time and resources by doing so, then why not do it,
unless you have a very good reason not to?

Back it up afterwards and you will be able to recover.


Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist