My Oracle Support Banner

START_REDEF_TABLE Builds Wrong Primary Key Index Attributes (Doc ID 1914635.1)

Last updated on FEBRUARY 26, 2019

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 10.2 to 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.


While using a PK based online redefinition, start_redef_table() always builds the PK Index NoParallel which causes bad execution performance. i.e,  DBMS_REDEFINITION builds the target table with wrong Primary Key index attributes.

If there is table with a primary key index and this primary key is compressed or has a parallel clause the:
If you use the DBMS_REDEFINITION package to rebuild the table then the index on the target table has no  parallel clause.
If you have a compressed key index the redefinition operation fails with ORA-28665

Steps to reproduce:

 - create MV metadata wrapper and add pk constraint
 - alter table <interim_table> disable primary key
   (internal statement to drop the pk index)
 - <complete refresh>
 - alter table <interim_table> enable primary key


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.