RE: db corruption

Definitely second Mladen's recommendation. A quick & dirty way to find possible suspect tables (assuming Oracle knows what it wants to do with logging/nologging in its' own tables) is something like this. You may want to add/change excluded schemas based on the options you have installed.  

hth,

-joe  

select owner||'.'||table_name from dba_tables

where logging <> 'YES' (*** or logging = 'NO' ***)

and owner not in ('SYS', 'SYSTEM', 'DBSNMP', 'WKSYS', 'OLAPSYS', 'WMSYS', 'MDSYS', 'BIBCAT') order by owner, table_name;  

> -----Original Message-----

> From: oracle-l-bounce_at_freelists.org

[mailto:oracle-l-bounce_at_freelists.org]

> On Behalf Of Mladen Gogala

> Sent: Tuesday, August 15, 2006 8:17 AM

> To: joseph.armstrong-champ_at_tufts.edu

> Cc: ORACLE-L

> Subject: Re: db corruption

>

>

> On 08/15/2006 09:57:31 AM, Joe Armstrong-Champ wrote:

>

> >

> > We were wondering what other shops do to detect corruption. Also
does

> > anyone have any recommended reading for how to fix it once it's been

> > detected? This is probably the hardest part depending on the extent
of

> > the damage.

>

> There might have been a logical corruption, usually a result of
restoring

> tablespaces

> with indexes created as "NOLOGGING". First thing to do is to verify
that

> you can actually

> restore the backup with "restore database verify".

>

>

> --

> Mladen Gogala

> http://www.mgogala.com

>

> --

> http://www.freelists.org/webpage/oracle-l

>
 

--
http://www.freelists.org/webpage/oracle-l