RE: Change index from nologging to logging

From: Kenneth Naim <kennaim_at_gmail.com>
Date: Sun, 22 Mar 2009 11:34:55 -0400
Message-ID: <717ED336BBAD4B30B0A9ECA5209361B5_at_KenPC>

I believe the poster is also using dataguard, and when they open the standby instance the indexes are market corrupt and need to be rebuilt.      

---

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Kumar Madduri
Sent: Sunday, March 22, 2009 8:15 AM
To: Hemant K Chitale
Cc: Oracle-L_at_freelists.org
Subject: Re: Change index from nologging to logging  

It matters because those indexes become unusable after clone.

On Sun, Mar 22, 2009 at 3:20 AM, Hemant K Chitale <hkchital_at_singnet.com.sg> wrote:

Why does it matter to you that some indexes have the NOLOGGING attribute set (which is the case if they are created with NOLOGGING) ?

NOLOGGING for an Index applies *only* at *CREATE* time . Redo for all subsequent DML is *always* LOGGING.

Hemant K Chitale
http://hemantoracledba.blogspot.com <http://hemantoracledba.blogspot.com/>

At 11:47 PM Saturday, Kumar Madduri wrote:

Hi
Some indexes were build using the nologging option. This creates corruption when the instance is refreshed. Now they need to be converted to logging option. I have two options to do this.

<snip>

Kumar  

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

Received on Sun Mar 22 2009 - 10:34:55 CDT