Re: Using DBMS_METADATA/DBMS_REDFINITION to move all objects to another TS
From: Andrew Kerber <andrew.kerber_at_gmail.com>
Date: Thu, 20 Jun 2013 11:58:51 -0500
Message-ID: <CAJvnOJb+d7eaKo5XXsafr=0v4Pj2=D5=-ijh8VDT-7M_WvXpaQ_at_mail.gmail.com>
Is the index naming convention critical? My method was to do it in a couple of steps, whereby I first add a string to the front of the index name by looking for the index creation piece (INDEX indexname), then trimming from the end of the index name if it is too long.
Date: Thu, 20 Jun 2013 11:58:51 -0500
Message-ID: <CAJvnOJb+d7eaKo5XXsafr=0v4Pj2=D5=-ijh8VDT-7M_WvXpaQ_at_mail.gmail.com>
Is the index naming convention critical? My method was to do it in a couple of steps, whereby I first add a string to the front of the index name by looking for the index creation piece (INDEX indexname), then trimming from the end of the index name if it is too long.
On Thu, Jun 20, 2013 at 11:53 AM, Rich Jesse < rjoralist2_at_society.servebeer.com> wrote:
> Andrew replies:
> <SNIP again>
>
> Yeah, I'm already doing that to have the new tables SEGMENT CREATION
> DEFERRED in order to save space on the ~2700 tables that are empty (they
> were originally created when the DB was 10g). But where that is a clearly
> defined string to replace, the semi-random index names are a wee bit
> trickier.
>
> Thanks anyway!
>
> Rich
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>
-- Andrew W. Kerber 'If at first you dont succeed, dont take up skydiving.' -- http://www.freelists.org/webpage/oracle-lReceived on Thu Jun 20 2013 - 18:58:51 CEST