Re: Creating unique index on huge table.

From: Franck Pachot <franck_at_pachot.net>
Date: Thu, 22 Sep 2016 23:35:44 +0000
Message-ID: <CAK6ito0mUCuYRL0MwXgafA_jsNeDSHr40uwbVBqaRgpreujVVg_at_mail.gmail.com>



Ok so redo from index will be ignored by Dbvisit mine. No pb. If additional redo volume is a problem then you can consider nologging. Note that creating an index online generates more redo. Le jeu. 22 sept. 2016 à 16:32, Vadim Keylis <vkeylis2009_at_gmail.com> a écrit :

> Hello Franck.
> We are testing Dbvisit replicate application. The unique index that I
> need to create would be on source database.
>
> Vadim
>
> On Thu, Sep 22, 2016 at 4:08 PM, Franck Pachot <franck_at_pachot.net> wrote:
>
>> Hi,
>> Are you referring to Dbvisit standby or replicate? If replicate, do you
>> create index on source or target?
>>
>> Le jeu. 22 sept. 2016 à 14:44, Vadim Keylis <vkeylis2009_at_gmail.com> a
>> écrit :
>>
>>> I am working on adding replication using third party tool(dbvisit) to
>>> our databases.
>>>
>>> I have couple 5T highly transactional partition tables. I need to add a
>>> partition unique index to these tables without causing any outage or
>>> incurring performance hit. Will greatly appreciate suggestions on the best
>>> approach to do it.
>>>
>>> Thanks so much,
>>> Vadim
>>>
>>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Fri Sep 23 2016 - 01:35:44 CEST

Original text of this message