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

Marquez, Chris

2005-08-19

Replies:
RE: ORA-1578...block corrupted...error is normal...a block...had a NOLOGGING...operation performed against

All,

After talking to a co-DBA we believe we *did* have [create] nologging operations within the redo logs applied to the recovered database.

Also, I just tested out our database in constant recovery mode (poor man's standby).
We have 33 indexes created *and* defined with nologging, *before* the database was restored and recovered (applying logs) to our standby server.  It seems that we can select from indexes that were "CREATED" with NOLOGGING and *still* are "DEFINED as LOGGING='NO".  When we select using the index on the database (in read only mode) we find the index and data are fine...no errors.
We have applied two weeks worth of arch log (transactions) against these indexes "DEFINED as LOGGING='NO".

So now that statement or questions is that;
"CREATED" with NOLOGGING, must be entirely different than "DEFINED [ALTER?] as LOGGING='NO" (dba_indexes).
Or rather NOLOGGING only has negative recovery impact on CREATED DDL?

Chris Marquez
Oracle DBA


-----Original Message-----
From: oracle-l-bounce@freelists.org on behalf of Jared Still
Sent: Fri 8/19/2005 3:31 PM
To: joelgarry@anabolicinc.com
Cc: oracle-l@freelists.org
Subject: Re: ORA-1578...block corrupted...error is normal...a block...had a NOLOGGING...operation performed against

On 8/19/05, Joel Garry <joelgarry@anabolicinc.com> wrote:
>
>
> Believe it. Time bomb sat there since long ago. Nologging operations
> bypass the redo logs. So they bypass the archived logs. So when you
> restore the datafile by rolling forward, you invalidate those blocks.


Roll forward from when?

If you restore from a backup prior to the nologging operation, and roll
forward, the index created with 'nologging' will not be restored.

If you restore a backup taken after the creation of the nologging operation,
the nologging object will be restored.


So you have to fix them with some other mechanism than recovery. Maybe
> use force logging if you don't want to run into this again. And all
> that advice about taking a backup after nologging operations seems
> pretty misleading, huh?


Either you need to test it further, or I don't understand your premise.

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