Re: Question: ONE corrupted tablespace in standby db???

On 16 Jun 2006 15:00:09 -0700, "BD" <bobby_dread_at_hotmail.com> wrote:

>> Does that mean you haven't tried to bring it up in read-only mode? I
>> think you must have since you say "is being used," but I have to ask.
>> Have you read from the affected datafiles?
>
>I can bring the db up in read-only mode.
>
>The affected files only contain a few specific, large, indexes.
>
>> When you created the standby, did you use RMAN or a manual procedure?
>> Did you follow a particular cookbook?
>
>Not RMAN. I used a manual process, after reviewing Oracle's
>documentation.
>

This is *exactly* why you know have a bootload of problems, while you are trying to be 'smart'

[snipped]

>INTERESTING: I just ran a select with an index hint, and got this::
>
>ORA-01578: ORACLE data block corrupted (file # 90, block # 2571)
>ORA-01110: data file 90: '/disk1/oradata/db1/arch_idx_db1_03.dbf'
>ORA-26040: Data block was loaded using the NOLOGGING option
>
>I do recall now, that I had to relocate this index from one tablespace
>to another not long ago, and elected to use NOLOGGING because at this
>point I need to be VERY aware of how much redo I was spitting out (disk
>space issues). This would appear to be the culprit.

Yet another smart measure in a standby database.

>
>I'm still not entirely clear on the implications of the NOLOGGING, but
>I'll obviously be digging into it... regardless, I see an index rebuild
>in my future. Or perhaps a recreation of that whole tablespace.
>
>Thanks!!

The index rebuild is fully self-inflicted. Doh!

--
Sybrand Bakker, Senior Oracle DBA