Home
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

rjsearle

2005-08-22

Replies:
Hi Jared,
 
I understand and agree with all you have said.
 
I have begun departing from this recently after a recent nasty restore and recover that took us 3 weeks.  Some of this delay was caused by successive failures of backup tapes.  We had to go back 3 days as one tape each from the more recent backup sets failed.  fortunately, the archivelogs were recovered.  UNfortunately ALL online redos were lost, but that's another matter.  One of these tapes failed on the second use.  We completely restored from a backup set, then 24 hours later had to get some more files from the same backup set and one of the tapes had failed.  rotten luck!  This is an environment where all backups are verified and tapes are regularly.
 
This reminded me not to place too many eggs in the backup basket.  If the most recent backup contained the first backup of the new segments created nologging and that tapeset fails then you are left in the same precarious situation.
 
The benefits to nologging are clear and inviting.  i think we should remember the additional risks associated.
 
Russell

 
On 8/23/05, Jared Still <jkstill@gmail.com> wrote:

On 8/22/05, Mercadante, Thomas F (LABOR) < Thomas.Mercadante@labor.state.ny.us> wrote:

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.


Quite a bit of time actually.  Try timing a bulk load operation with and without logging.
 

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.


You don't need a complete database backup, just the datafiles containing the  nologging objects.
 

 
--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist