Re: NOLOGGING recovery errors
- From: Adric Norris <landstander668@xxxxxxxxx>
- To: lyallbarbour@xxxxxxxxxxxxxxx, oracle-l <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 6 Dec 2010 11:47:30 -0600
Have you tried rebuilding with the ONLINE keyword? It seems
counterintuitive, but I seem to recall this variation working in the past...
alter index da.ST_PRODTXWIPSRC_ON_FK_I rebuild ONLINE logging;
On Mon, Dec 6, 2010 at 11:12 AM, <lyallbarbour@xxxxxxxxxxxxxxx> wrote:
> I did this for one of the indexes
>
> alter index da.ST_PRODTXWIPSRC_ON_FK_I rebuild logging
> *
> ERROR at line 1:
> ORA-01578: ORACLE data block corrupted (file # 6, block # 5341)
> ORA-01110: data file 6: '/oradata/semst01/idx01.dbf'
> ORA-26040: Data block was loaded using the NOLOGGING option
>
> It's a non unique index. I think it's complaining about the primary key
> index on that table... which is weird...
> Anyhow, i'm trying to recreate those primary key/ unique key indexes and i
> can't cause they have constraints on them:
>
> Here's a primary key:
> semst01:SQL> alter index da.ST_WI_PROP_VALS_PK rebuild logging;
> alter index da.ST_WI_PROP_VALS_PK rebuild logging
> *
> ERROR at line 1:
> ORA-01578: ORACLE data block corrupted (file # 6, block # 19549)
> ORA-01110: data file 6: '/oradata/semst01/idx01.dbf'
> ORA-26040: Data block was loaded using the NOLOGGING option
>
> Was hoping someone had a quick script to disable a constraint then drop the
> index...
>
> Lyall
>
>
--
"I'm too sexy for my code." -Awk Sed Fred
Other related posts: