Kbase P68107: Unable to start SQL servers.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/12/2008 |
|
Status: Verified
SYMPTOM(s):
Unable to start SQL servers.
Unable to attach shared memory <shmname>, error <n>. (1720)
Unable to attach shared memory <db-extent>, error 0. (1720)
Failure during dsmUserConnect (-1)
Could not spawn a SQL server. (8842)
Number of Database Buffers (-B): 238000. (4239)
Database Blocksize (-blocksize): 8192. (6573)
FACT(s) (Environment):
Windows NT 32 Intel/Windows 2000
Progress/OpenEdge Product Family
CAUSE:
The Windows shared memory limit for a process is 2 GB.
There are many Progress parameters that contribute to the size of the shared memory structure when a session is started.
The SQL engine in 9.1D and upwards requires a shared memory segment because it is now multithreaded. In the symptom above the parameters for the -B alone were over 1.9 GB. When an SQL server opens an additional memory segment, the request for an additional shared memory space is exceeding the MS Windows 2 GB limit for a process.
FIX:
Reduce the -B to an acceptable limit, so the process does not exceed 2 GB of shared memory.
i.e. 200000.
Reference Solution P5698: 2 gigabyte memory limitation per process on Windows Platform