This section describes the procedures for estimating the HP-UX OS parameter values (or kernel parameter values). If OS parameter values are too small, HiRDB may not function correctly. Table 21-1 shows the guidelines for the HP-UX OS parameter values.
If you are using HP-UX 11i, do not change the OS parameter values while HiRDB is running. Even an OS parameter that can be adjusted automatically, if changed may affect HiRDB operations.
Table 21-1 Guidelines for the HP-UX OS parameter values
OS parameter | Guideline for value |
---|---|
maxdsiz (32-bit-mode) maxdsiz_64bit (64-bit mode) | ![]() The target value should satisfy the following two conditions; however, if the value is less than (process private area used by the Single Server process#1) ![]() 32-bit mode
![]() The target value should satisfy the following two conditions; however, if the value is less than (process private area using by each server process#3) ![]() 32-bit mode
|
maxssiz | Specify 80 MB or greater. Note that the unit for this value is MB. If this value is less than the value required by another program that is run on the server machine, specify the latter, which is greater. |
maxfiles | HiRDB calculates and sets this value, so you do not need to specify it. |
maxfiles_lim | Specify at least MAX(1344,value of pd_max_open_fds, n). |
nfile | Specify at least MAX{1600,320![]() ![]() ![]() ![]() ![]() ![]() If the value determined from this formula exceeds the system maximum, use the system maximum value. |
nflocks | Specify at least a + (b![]() ![]() |
maxuprc | Specify at least MAX(value of pd_max_server_process + e, 512). However, if this value is less than the value required by another program that runs on the server machine, specify the higher value. |
maxusers | Recommended value is 128 or greater. |
nproc | Specify at least the value of MAX (pd_max_server_process + 20, 576). |
msgmni | Specify the number of message queue identifiers required by all programs that are run on the server machine. For details about the number of message queue identifiers required by HiRDB, see 21.5 Estimating the sizes of message queues and semaphores. Add the values obtained. |
msgtql | Specify at least MAX(k![]() |
semmni | Specify the number of semaphore identifiers required by all programs that are run on the server machine. For details about the number of semaphore identifiers required by HiRDB, see 21.5 Estimating the sizes of message queues and semaphores. Add the values obtained. The recommended value is 1024 or greater. |
semmns | Specify the number of semaphores required by all programs that are run on the server machine. For details about the number of semaphores required by HiRDB, see 21.5 Estimating the sizes of message queues and semaphores. Add the values obtained. The recommended value is 7200 or greater. |
semmnu | Specify a value of 512 or greater. |
semume | Specify a value of 512 or greater. |
shmmax | Specify at least MAX(p + q, r, s, t), and at least 200000000. If the global buffer dynamic update facility is used, consider the size of the global buffers to be added; if there is a possibility that the size of the added part will become greater than the specified value, specify the anticipated size of the added part. However, if the inter-process memory communication facility is used (PDIPC=MEMORY is specified in the client environment definition), specify a size of at least MAX(p + q, r, s, value of PDSENDMEMSIZE, value of PDRECVMEMSIZE). Specify in the HiRDB system definition's SHMMAX operand a value no greater than the value for shmmax determined here. |
shmmni | Specify a value of 1000 or greater. If the global buffer dynamic update facility is used, add the following value. Add 1 when the security audit facility is used.
A ![]() ![]() A indicates the maximum number of concurrently executable clients that use the inter-process memory communication facility. If the value of A is unknown, use the total number of clients that use the inter-process memory communication facility or the value of k. |
shmseg | Specify a value of 120 or greater. To dynamically change the global buffer, add the maximum value of the pd_max_add_dbbuff_shm_no operand value defined in each server. Also add 1 when the security audit facility is used. |