13.12.3 Prerequisites

Organization of this subsection
(1) Table partitioning method
(2) Applicability by table type
(3) Required products
(4) Other applicability issues

(1) Table partitioning method

Key range partitioning is the prerequisite. Table 13-3 shows for each table partitioning method whether or not the partitioning storage conditions can be changed.

Table 13-3 Table partitioning methods for which partitioning storage conditions can be changed

Table partitioning methodApplicability
Key range partitioningStorage condition specificationOnly = is used as the comparison operator for storage conditionsY
A condition other than = is used as the comparison operator for storage conditionsN
Boundary values specificationOther than belowY
Matrix partitioningN
Hash partitioning (including rebalancing)FIX hash not specifiedN#
FIX hash specified
Legend:
Y: Can be changed.
N: Cannot be changed.
#
Only RDAREA addition is supported by the ALTER TABLE definition SQL statement with ADD RDAREA specified.

(2) Applicability by table type

Partitioning storage conditions cannot be changed for the following types of tables:

(3) Required products

To change partitioning storage conditions, HiRDB Advanced Partitioning Option must be installed. If you attempt to change the partitioning storage conditions (CHANGE RDAREA of ALTER TABLE) and this product has not been set up, the KFPA11948-E message will be displayed and ALTER TABLE will terminate with an error.

(4) Other applicability issues

(a) Indexes

If an index has been defined for a table whose partitioning storage conditions are to be changed, it may not be possible to change the partitioning storage conditions depending on the index definition conditions. Table 13-4 shows for each type of index whether or not the partitioning storage conditions can be changed.

Table 13-4 Index types for which partitioning storage conditions can be changed

Index typePartitioned/Non-partitioned indexApplicability
Cluster key indexPartitioned key indexY#1
Primary key index
(including an index for which a primary key and cluster key are defined)
B-tree indexPartitioned key indexY#1
Non-partitioned key indexY#1, #2
Plug-in indexNot applicableN
Legend:
Y: Can be changed.
N: Cannot be changed.
#1
Depending on the partitioning conditions for the index storage RDAREAs, it may not be possible to change the partitioning storage conditions. Table 13-5 Whether or not the partitioning storage conditions can be changed depending on the partitioning conditions for the index storage RDAREAs shows whether or not the partitioning storage conditions can be changed depending on the partitioning conditions for the index storage RDAREAs.
#2
If the index storage RDAREAs have a 1-to-1 partition correspondence with the table storage RDAREAs, the partitioning storage conditions can be changed. Table 13-6 Applicability of changing partitioning storage conditions for a non-partitioning key index shows whether or not change to the partitioning storage conditions is applicable for a non-partitioning key index.

Table 13-5 Whether or not the partitioning storage conditions can be changed depending on the partitioning conditions for the index storage RDAREAs

Partitioning conditions for the index storage RDAREAsWhether or not the partitioning storage conditions can be changed
SplitCombine
Partitioning key indexIndex storage RDAREAs are partitioned.YY#1
Index storage RDAREAs are not partitioned.N#2N#3
Non-partitioning key indexPartitioning is performed in such a manner that the table storage RDAREAs and index storage RDAREAs have a 1-to-1 correspondence.Index storage RDAREAs are partitioned.YY#1
Index storage RDAREAs are not partitioned.N#2N#3
OtherNN
Legend:
Y: Partitioning storage conditions can be changed.
N: Partitioning storage conditions cannot be changed.
#1
If the total number of index storage RDAREAs is reduced after combining to a single index storage RDAREA, the partitioning storage conditions can no longer be changed because the row-partitioned index has been converted to a non-row-partitioned index.
#2
The partitioning storage conditions cannot be changed because the non-row-partitioned index is converted to a row-partitioned index.
#3
A row-partitioned index can be changed to a non-row-partitioned index only when the target table is stored in a single RDAREA. Therefore, the partitioning storage conditions cannot be changed.

If the partitioning storage conditions cannot be changed due to the relationship between index storage RDAREAs and table storage RDAREAs, delete the applicable index first, execute ALTER TABLE, and then re-define the index.

Figures 13-18 and 13-19 show cases in which a table storage RDAREA cannot be split.

Figure 13-18 Case in which a table storage RDAREA cannot be split (part 1)

[Figure]

Figure 13-19 Case in which a table storage RDAREA cannot be split (part 2)

[Figure]

Table 13-6 Applicability of changing partitioning storage conditions for a non-partitioning key index

Table RDAREAsIndex RDAREAs
Row partitioning between serversRow partitioning within serversRow partitioning between serversNo row partitioning between servers
YesYesYN
No[Figure]Y#
NoYesYN
No[Figure][Figure]
Legend:
Y: Can be changed.
N: Cannot be changed.
[Figure]: Not applicable.
#: Cannot be changed if multiple partitioning storage conditions are stored in the same RDAREA.
(b) RDAREAs storing LOB and indexes

If RDAREAs storing LOB and indexes are defined for a table whose partitioning storage conditions are to be changed, these RDAREAs must also be partitioned or combined along with the table in the same manner.

(c) RDAREAs after change

RDAREAs after the change cannot be used for the following purposes: