Re: Should one include partitioning key column as first column of non-unique local index
From: Robert Klemme <shortcutter_at_googlemail.com>
Date: Wed, 17 Aug 2011 11:00:02 +0200
Message-ID: <9b1e8nF73gU1_at_mid.individual.net>
On 17.08.2011 09:35, vsevolod afanassiev wrote:
> OK, found Metalink Note 312843.1. The only way to compress partitioned
> index is to drop and rebuild. Great.
Date: Wed, 17 Aug 2011 11:00:02 +0200
Message-ID: <9b1e8nF73gU1_at_mid.individual.net>
On 17.08.2011 09:35, vsevolod afanassiev wrote:
> OK, found Metalink Note 312843.1. The only way to compress partitioned
> index is to drop and rebuild. Great.
Maybe DBMS_REDEFINITION can help. It's certainly not an easy operation
though.
http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14258/d_redefi.htm#CBBJJAIF
One way could be to copy the table (with partitions), create the compressed index on the copy and swap both tables with DBMS_REDEFINITION.
Kind regards
robert
-- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/Received on Wed Aug 17 2011 - 04:00:02 CDT