8.3.9 Operands related to global buffers

23) pd_max_add_dbbuff_no = maximum-global-buffers-count-for-dynamic-addition
[Figure]<unsigned integer>((1-32752))
In order to change global buffers dynamically, this operand specifies the maximum number of global buffers (per server) that can be added dynamically by the pdbufmod command.
Condition
Y must be specified in the pd_dbbuff_modify operand.
Specification guidelines
  • Estimate the number of global buffers to be added dynamically by the pdbufmod command and then specify a sufficient value based on that value.
  • Determine the operand's value in such a manner that the following condition is satisfied:
    Value of pd_max_add_dbbuff_no[Figure] 2000000 - number of global buffers allocated per server during HiRDB startup
Notes
Do not specify an unnecessarily large value in this operand. If this operand's value is too large, the shared memory used by HiRDB increases, which may result in a shortage of shared memory and an inability of HiRDB to start.
Relationship to other operands
This operand is related to the following operands:
  • SHMMAX
  • pdbuffer
  • pd_max_add_dbbuff_shm_no
24) pd_max_add_dbbuff_shm_no = maximum-shared-memory-segments-count-for-dynamic-addition
[Figure]<unsigned integer>((1-32752))
In order to change global buffers dynamically, this operand specifies the maximum number of shared memory segments (per server) that can be allocated when dynamic addition is performed by the pdbufmod command.
Condition
Y must be specified in the pd_dbbuff_modify operand.
Specification guidelines
Estimate the number of global buffers to be added dynamically by the pdbufmod command and then specify an appropriate value.
Notes
  • If the following condition is satisfied, the value of the pd_max_add_dbbuff_no operand is assumed in this operand:
    Value of pd_max_add_dbbuff_shm_no < value of pd_max_add_dbbuff_no
    The value of the pd_max_add_dbbuff_no operand is also assumed when the default value satisfies the above condition.
  • Do not specify an unnecessarily large value in this operand. If this operand's value is too large, the shared memory used by HiRDB increases, which may result in a shortage of shared memory and an inability of HiRDB to start.
  • If the size of a shared memory segment to be added exceeds the SHMMAX operand value, shared memory is divided into multiple segments based on the SHMMAX operand value as the maximum value. Either increase the SHMMAX operand value based on the size of the shared memory segment to be added or increase the pd_max_add_dbbuff_no operand value so that no shortage occurs when the shared memory is segmented.
Relationship to other operands
This operand is related to the following operands:
  • SHMMAX
  • pdbuffer
  • pd_max_add_dbbuff_no