My Oracle Support Banner

DBMS_REDEFINITION: Case Study for a Large Non-Partition Table to a Partition Table with Online Transactions Occuring (Doc ID 1481558.1)

Last updated on SEPTEMBER 20, 2022

Applies to:

Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version and later
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.


NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product.  Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

This Note has been written to provide some volume details and timings for the process
to convert a normal table to a partition table using the DBMS_REDEFINITION package.

The note will also include details of objects used by the process (Fast Refresh) and how
these become populated during the procedure.

The procedure is broken down into the following sections:

1.  Create the Partition Table structure required, known as the Interim table.
2.  Execute DBMS_REDEFINITION.can_redef_table
3.  Execute DBMS_REDEFINITION.start_redef_table
4.  Execute DBMS_REDEFINITION.sync_interim_table
5.  Execute DBMS_REDEFINITION.finish_redef_table
6.  Drop the interim table.




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.