13.5 Plug-in index row partitioning

When you partition a table, you also need to partition its plug-in index and store it in multiple user LOB RDAREAs.

Organization of this section
(1) Effects of plug-in row partitioning
(2) Definition procedure
(3) Forms of plug-in index row partitioning
(4) Design considerations
(5) Notes

(1) Effects of plug-in row partitioning

Improved operability
When a plug-in index is created in the batch mode, the portion of the plug-in index in each user LOB RDAREA is processed independently.

(2) Definition procedure

For details about how to define plug-in index row partitioning, see 6.4 Creating a table containing a plug-in-provided abstract data type.

(3) Forms of plug-in index row partitioning

The forms of plug-in index row partitioning are described below for a HiRDB/Single Server and for a HiRDB/Parallel Server.

(a) HiRDB/Single Server

For a HiRDB/Single Server, a plug-in index can be partitioned and stored in multiple user LOB RDAREAs on multiple disks on the same basis as the row-partitioned table.

Figure 13-6 shows a form of plug-in index row partitioning. Figure 13-7 shows an example of plug-in index row partitioning based on the form shown in Figure 13-6.

Figure 13-6 Form of plug-in index row partitioning (HiRDB/Single Server)

[Figure]

Figure 13-7 Example of plug-in index row partitioning (key range partitioning) (HiRDB/Single Server)

[Figure]

Explanation:
The example assumes that a plug-in index is defined for the INSTRUCTIONS_FOR_USE column.
The MEDICAL_MANAGEMENT_TABLE is partitioned and stored in user LOB RDAREAs LOBSGML1 and LOBSGML2 using the MEDICINE_ID column as the condition. The plug-in index is stored in LOBNGRAM1 and LOGNGRAM2.
(b) HiRDB/Parallel Server

For a HiRDB/Parallel Server, a plug-in index can be partitioned and stored in multiple user LOB RDAREAs located in multiple server machines or back-end servers, on the same basis as its row-partitioned table.

Figure 13-8 shows a form of plug-in index row partitioning. Figure 13-9 shows an example of plug-in index row partitioning based on the form shown in Figure 13-8.

Figure 13-8 Form of plug-in index row partitioning (HiRDB/Parallel Server)

[Figure]

Figure 13-9 Example of plug-in index row partitioning (key range partitioning) (HiRDB/Parallel Server)

[Figure]

[Figure]

Explanation:
The example assumes that a plug-in index is defined for the OPERATION_MANUAL column.
MEDICAL_MANAGEMENT_TABLE is partitioned and stored in user LOB RDAREAs LOBSGML1-LOBSGML3 using the MEDICINE_ID column as the condition. The plug-in index is stored in LOBNGRAM1, LOBNGRAM2, and LOBSGML3.

(4) Design considerations

Separate user LOB RDAREAs should be used for a row-partitioned table and for its plug-in index.

(5) Notes

Row partitioning results in an increase in the number of RDAREAs; therefore, when the database is backed up with RDAREA specified, the table and its index will have a one-to-one correspondence.