When you partition an existing table, the data is not automatically moved to the new partitions. PARTITIONMANAGE SPLIT is used to redistribute the records in one table partition into different partitions.
Use PARTITIONMANAGE SPLIT when a partition is too big, a partition needs to be partitioned into finer granularities, or for data migration when initially partitioning a table. When a table partition is split, the records, LOB fields, and local index partitions of the table partition instance are moved to the appropriate target partitions, and global indexes are updated.
The following diagram depicts the splitting a large table into smaller partitions.
Figure 50. Splitting partition example
PARTITIONMANAGE SPLIT relies on the target partitions being previously defined and designated as a split target. Designating a partition as a split target can be done through an OpenEdge SQL or ABL program, or the easiest way is through the OpenEdge Management/OpenEdge Explorer interface. (See Management and OpenEdge Explorer: Managing Table Partitioning in Databases, or the online help for these tools.) Once designated as a split target, existing data destined for the target is not accessible. For this reason, do not designate partitions as a split target until ready to execute the split.
PARTITIONMANAGE SPLIT allocates target partitions that are not allocated at the beginning of the split.
The syntax for PARTITIONMANAGE SPLIT is as follows:
If you are splitting a table for the first time, source partition is specified as composite initial; for all other splits, the source partition is specified with partition table-partition-name. For complete details on PARTITIONMANAGE SPLIT, see the section, PROUTIL PARTITIONMANAGE SPLIT qualifier.
