12.22.3 Rules for choosing an RDAREA for storage

When there are multiple temporary table RDAREAs, or when PDTMPTBLRDAREA is omitted from the client environment definition, HiRDB chooses a temporary table RDAREA for storing data. This subsection explains how HiRDB chooses the target RDAREA to use for storage.

Organization of this subsection
(1) Choosing a target back-end server for storage (applicable to HiRDB/Parallel Servers only)
(2) Choosing storage candidate RDAREAs
(3) Choosing the RDAREAs that satisfy the conditions
(4) Choosing the temporary table RDAREA in which to store data

(1) Choosing a target back-end server for storage (applicable to HiRDB/Parallel Servers only)

For a HiRDB/Parallel Server, HiRDB first chooses a back-end server for storing data. HiRDB narrows down the candidate back-end servers based on the rules described below and then chooses a back-end server that accesses a base table that is not a temporary table among all the base tables specified in the INSERT statement.

(2) Choosing storage candidate RDAREAs

HiRDB chooses the storage candidate RDAREAs based on the specification of PDTMPTBLRDAREA in the client environment definition. For details about the specification of PDTMPTBLRDAREA, see 12.22.2(3) How to specify a temporary table RDAREA for storing data.

(3) Choosing the RDAREAs that satisfy the conditions

From the storage candidate RDAREAs, HiRDB chooses RDAREAs that satisfy all the following conditions:

(4) Choosing the temporary table RDAREA in which to store data

Among the RDAREAs satisfying the conditions, HiRDB preferentially uses the following temporary table RDAREAs: