Scalable Database Server, HiRDB Version 8 Installation and Design Guide
Figure 15-1 shows the memory allocation for a HiRDB/Single Server.
Figure 15-1 Memory allocation for a HiRDB/Single Server
Table 15-1 provides the details of the shared memories for a HiRDB/Single Server.
Table 15-1 HiRDB/Single Server shared memory details
| Item | Type of shared memory | ||||
|---|---|---|---|---|---|
| Unit controller shared memory | Global buffer shared memory | Utility shared memory | Security monitoring information buffer shared memory | Inter-process memory communication shared memory | |
| Purpose | System control | Global buffers | Communication between the unit controller and utilities | Security monitoring information buffer | Client-server inter-process memory communication |
| Processes | All HiRDB processes | Single Server | Utility processes | Single server | Single Server, client processes |
| Number of segments | 1 |
|
1 | 1 | Number of clients connected using the PDIPC=MEMORY environment variable (0-2000) |
| Maximum value per segment | See Table 15-2 Size of memory required for a HiRDB/Single Server. It may not be possible to allocate this size depending on the OS environment. | Divide the segment by the SHMMAX operand value. It may not be possible to allocate this size depending on the OS environment. | See Table 15-2 Size of memory required for a HiRDB/Single Server. | See Table 15-2 Size of memory required for a HiRDB/Single Server. It may not be possible to allocate this size depending on the OS environment. | See Table 15-2 Size of memory required for a HiRDB/Single Server. It may not be possible to allocate this size depending on the OS environment. |
| Allocation conditions | None | There must be a global buffer definition | Specify pd_utl_exec_mode=1 | Specify the pd_aud_file_name operand as the HiRDB file system area name for the audit trail file. | There are clients connected using the PDIPC=MEMORY environment variable |
| Creation timing | At unit activation (including standby unit activation when the rapid system switchover facility is used) |
|
When utilities are executed | When a HiRDB/Single Server starts up | When client and server are connected |
| Deletion timing | At next unit activation (including standby unit activation when the rapid system switchover facility is used) |
|
10 minutes after the utility terminates | When a HiRDB Single Server quits | When client and server are disconnected |
| Indication by pdls -d mem | Indicated | Indicated | Indicated | Indicated | Not indicated |
| SHM-OWNER of pdls -d mem | MANAGER | Server name | UTILITY | AUDDEF | Not indicated |
| Related operands |
|
|
|
|
|
| Remarks | Can be created only when pd_utl_exec_mode=1 (when pd_utl_exec_mode=0, the relevant space is allocated in the unit controller shared memory). | ||||
All Rights Reserved. Copyright (C) 2007, Hitachi, Ltd.