Appendix D.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)

(a) For a HiRDB single server configuration

209 + [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] 64,000[Figure])

(b) For a HiRDB parallel server configuration (front-end server and dictionary server)

3

(c) For a HiRDB parallel server configuration (dictionary server)

206 + [Figure]

(d) For a HiRDB parallel server configuration (back-end server)

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] 64,000[Figure])

[Figure]: MAX(number of table columns, number of table indexes, number of RDAREAs for table)

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)

(a) For a HiRDB single server configuration

209 + [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] 64,000[Figure])

(b) For a HiRDB parallel server configuration (front-end server and dictionary server)

3

(c) For a HiRDB parallel server configuration (dictionary server)

206 + [Figure]

(d) For a HiRDB parallel server configuration (back-end server)

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] 64,000[Figure])

[Figure]: MAX(number of table columns, number of table indexes, number of RDAREAs for table)

(3) Rebalancing utility (pdrbal)

(a) For a HiRDB single server configuration
Shared mode (-k share)
starting/finishing#1 + preprocessing#2 + rebalancing#3 + 2
Exclusive mode (-k exclusive)
starting/finishing#1 + preprocessing2 + rebalancing#3
(b) For a HiRDB parallel server configuration
Shared mode (-k share)
  • Front-end server: starting/finishing#1 + preprocessing#2 + 1
  • Dictionary server: starting/finishing#1 + preprocessing#2
  • Back-end server: starting/finishing#1 + rebalancing#3
Exclusive mode (-k exclusive)
  • Front-end server: starting/finishing#1 + preprocessing#2
  • Dictionary server: starting/finishing#1 + preprocessing#2
  • Back-end server: starting/finishing#1 + rebalancing#3
#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 D.1(10) CREATE [PUBLIC] FUNCTION.
Bi: Number of lock requests per procedure
For the number of lock requests of a procedure, see in D.1(13) CREATE [PUBLIC] PROCEDURE.
#2: The number of lock requests for preprocessing is as follows:
  • HiRDB single server configuration: 225
  • HiRDB parallel server configuration (front-end server): 5
  • HiRDB parallel server configuration (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] 64,000[Figure])

(4) pdacunlck command

(a) For a HiRDB single server configuration

0

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
(b) For a HiRDB parallel server configuration (dictionary server)

0

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