When you partition a table, you also need to partition its plug-in index and store it in multiple user LOB RDAREAs.
For details about how to define plug-in index row partitioning, see 7.4 Creating a table containing a plug-in-provided abstract data type.
The forms of plug-in index row partitioning are described below for a HiRDB/Single Server and for a HiRDB/Parallel 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 14-6 shows a form of plug-in index row partitioning. Figure 14-7 shows an example of plug-in index row partitioning based on the form shown in Figure 14-6.
Figure 14-6 Form of plug-in index row partitioning (HiRDB/Single Server)
Figure 14-7 Example of plug-in index row partitioning (key range partitioning) (HiRDB/Single 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 14-8 shows a form of plug-in index row partitioning. Figure 14-9 shows an example of plug-in index row partitioning based on the form shown in Figure 14-8.
Figure 14-8 Form of plug-in index row partitioning (HiRDB/Parallel Server)
Figure 14-9 Example of plug-in index row partitioning (key range partitioning) (HiRDB/Parallel Server)
Separate user LOB RDAREAs should be used for a row-partitioned table and for its plug-in index.
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.