Kbase P23592: What is the limit for Memory for Progress 9.0B and higher?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/7/2008 |
|
Status: Verified
GOAL:
What is the Maximum Shared Memory Segment Size (SHMMAX) for Progress?
GOAL:
SHMMAX and SHMSEG Changes in Progress 9.0B
GOAL:
What is the Maximum number of Shared Memory Segments (SHMSEG) for Progress?
GOAL:
What is the limit of Shared Memory Segments for Progress 64-Bit ports?
GOAL:
What is the limit of Shared Memory Segments for Progress 32-Bit ports?
GOAL:
Why do we get error 1175 ?
GOAL:
Maximum number of shared-memory segments per process exceeded. (1175)
FACT(s) (Environment):
Progress 9.0B
Progress 9.1x
OpenEdge 10.0x
OpenEdge 10.1A
FIX:
Prior to 9.0B the maximum shared memory segment size (SHMMAX) we used in the Progress RDBMS was 16,777,216 (16MB) for most UNIX Operating Systems, and the maximum number of shared memory segments (SHMSEG) you could have was 116. This equated to approximately 1.8Gb of memory. There were exceptions to the SHMMAX limit of 16MB on NT, AIX, Sequent PTX and DG-UX where SHMMAX was 134,217,728 (128MB). When these values are exceeded, the 1175 error is returned. AIX 32-bit Progress by default had a limitation of SHMSEG 10 unless the EXTSHM=ON parameter was globally defined.
In 9.0B and later, these values have changed to the following:
Progress Total Shared
Port: SHMMAX SHMSEG Memory Accessed:
-------- ------------ ------ ----------------
32-bit 134,217,728 21 2,147,483,648
(128Mb) (2Gb, due to 32-bit pointers limitation)
64-bit 1,073,741,824 116 124,554,051,584
(1Gb) (116Gb)