Appendix E.4 Utilities and commands

Organization of this subsection
(1) Database load utility (pdload)
(2) Database reorganization utility (pdrorg)
(3) Rebalancing utility (pdrbal)
(4) pdacunlck command

(1) Database load utility (pdload)

ConditionNumber of lock requests
HiRDB/Single Server209 + [Figure] + number of segments used by RDAREAs for table + number of segments used by RDAREAs for index + ([Figure] number of segments used by LOB RDAREAs[Figure] 64000 [Figure]) + [Figure]
HiRDB/Parallel ServerFront-end server3
Dictionary server206 + [Figure]
Back-end serverNumber of segments used by RDAREAs for table + number of segments used by RDAREAs for index + ([Figure] number of segments used by LOB RDAREAs[Figure] 64000 [Figure]) + [Figure]
[Figure]: MAX(number of table columns, number of table indexes, number of RDAREAs for table)
[Figure]: To estimate a value, see the section on Resources to be used in locking across transactions (specified using the pd_lck_until_disconnect_cnt operand) in Locked resources per server that are required for executing the database reorganization utility in the manual HiRDB Version 8 Command Reference.
Determine the number of segments used from the number of segments scheduled to store data. When the -d option is specified and if the number of segments already storing data (the number of segments being used) is greater than the number of segments scheduled to store data, use for computation the number of segments being used.

(2) Database reorganization utility (pdrorg)

ConditionNumber of lock requests
HiRDB/Single Server209 + [Figure] + number of segments used by RDAREAs for table + number of segments used by RDAREAs for index ([Figure] number of segments used by LOB RDAREAs[Figure] 64000 [Figure]) + [Figure]
HiRDB/Parallel ServerFront-end server3
Dictionary server206 + [Figure]
Back-end serverNumber of segments used by RDAREAs for table + number of segments used by RDAREAs for index + ([Figure] number of segments used by LOB RDAREAs[Figure] 64000 [Figure]) + [Figure]
[Figure]: MAX(number of table columns, number of table indexes, number of RDAREAs for table)
[Figure]: To estimate a value, see the section on Resources to be used in locking across transactions (specified using the pd_lck_until_disconnect_cnt operand) in Locked resources per server that are required for executing the database reorganization utility in the manual HiRDB Version 8 Command Reference.

(3) Rebalancing utility (pdrbal)

ConditionNumber of lock requests
HiRDB/
Single Server
Shared mode (-k share)starting/finishing1 + preprocessing2 + rebalancing3 + 2
Exclusive mode (-k exclusive)starting/finishing1 + preprocessing2 + rebalancing3
HiRDB/
Parallel Server
Shared mode
(-k share)
Front-end serverstarting/finishing1 + preprocessing2 + 1
Dictionary serverstarting/finishing1 + preprocessing2
Back-end serverstarting/finishing1 + rebalancing3
Exclusive mode (-k exclusive)Front-end serverstarting/finishing1 + preprocessing2
Dictionary serverstarting/finishing1 + preprocessing2
Back-end serverstarting/finishing1 + rebalancing3
1 Number of lock requests for starting/finishing = [Figure]Ai + [Figure]Bi
Ai: Number of lock requests per function
For the number of lock requests of a function, see in E.1(4) CREATE FUNCTION.
Bi: Number of lock requests per procedure
For the number of lock requests of a procedure, see in E.1(7) CREATE PROCEDURE.
2 The number of lock requests for preprocessing is as follows:
  • HiRDB/Single Server: 225
  • HiRDB/Parallel Server (front-end server): 5
  • HiRDB/Parallel Server (dictionary server): 220
3 The number of lock requests for rebalancing = number of segments used by RDAREAs for table + number of segments used by RDAREAs for index + ([Figure] number of segments used by LOB RDAREAs[Figure] 64000 [Figure])

(4) pdacunlck command

ConditionNumber of lock requests
HiRDB/Single Server0
HiRDB/Parallel Server (dictionary server)Add the following if an authorization identifier is specified:
+ 128
Add the following if ALL is specified:
+ number-of-users-registered-in-dictionary-table-SQL_USERS