Table D-1 shows the maximum number of utilities that can be executed concurrently. The table assumes that appropriate values are set in the system definition. For settings, see the HiRDB Version 8 System Definition.
Table D-1 Maximum number of utilities that can be executed concurrently
Utility | Maximum number of concurrently executable copies | Number of connections required for execution of 1 utility | |
---|---|---|---|
pd_utl_exec_mode=0 | pd_utl_exec_mode=1 | ||
Database initialization utility | 1 | 1 | |
Database structure modification utility | 1 | 1 | |
Database load utility | 32 | Value specified in pd_max_users operand | 1 |
Database reorganization utility2 | 32 | Value specified in pd_max_users operand | 1 |
Rebalancing utility | 32 | Value specified in pd_max_users operand | 1 |
Database definition utility3 | Value specified in pd_max_users operand | 1 | |
Integrity check utility | Value specified in pd_max_users operand ![]() | 2 | |
Database condition analysis utility | 16 | Value specified in pd_max_users operand | 1 |
Optimizing information collection utility | 16 | Value specified in pd_max_users operand ![]() | 2 |
Dictionary import/export utility | 1 | 1 | |
Database copy utility | ![]() gi: Number of backup files specified in pdcopy e: Maximum number of copies of pdcopy that can be executed concurrently1 | ![]() gi: Number of backup files specified in pdcopy e: Maximum number of copies of pdcopy that can be executed concurrently1 | 0 |
Database recovery utility | 32 | Value specified in pd_max_users operand | 0 |
1 The maximum number of copies of a utility that can be executed concurrently also depends on the number of backup files specified in pdcopy. This can be determined as follows:
2 When the free page release utility or the global buffer residence utility is used, the database reorganization utility is executed internally.