The table below describes the database sizes defined based on the system definition default values. If you use a number of resources that exceeds the number explained here, resources might become insufficient if the default values are specified for the operands. To avoid this, estimate and specify appropriate values for the operands including related operands.

Table 1-13 Database sizes that can be defined by default values

Major resource	Number	Related operand
Authorization identifier	100	pd_auth_cache_size
Base table	500	pd_table_def_cache_size pd_assurance_table_no
Index	2500	pd_assurance_index_no
Viewed table	500	pd_table_def_cache_size pd_view_def_cache_size
Routine	100	pd_routine_def_cache_size
RDAREA	1000 (per server)	pd_max_rdarea_no
HiRDB file	2000 (per server)	pd_max_file_no

Effects of the number of table partitions

For a HiRDB single server configuration, a non-partitioned table (in which the number of partitions is 1) is assumed. For a HiRDB parallel server configuration, the number of table partitions is assumed to be 6 under the following conditions:

• Number of units in the system: 3
• Number of back-end servers in the unit: 2
• Partitioning within a server is not applied.

If the number of table partitions exceeds the above values, you need to examine the following operand:

• pd_table_def_cache_size

Effects of using the table partitioning method

For the operands below, if there are tables or indexes that are partitioned within a server, you need to add the number of partitions. Therefore, if partitioning within a server is used, verify the specified value even if the number of resources is within the estimated size.

• pd_assurance_table_no
• pd_assurance_index_no

For guidelines on setting a value, see the description of each operand.