Physical memory on this machine may be too fragmented
This error may be caused by a hardware problem.
At startup, Adaptive Server allocates and initializes the memory needed for its structures and cache. This error occurs when Adaptive Server is not able to initialize the memory needed for its structures and static cache.
The most common cause of this error is that the total memory required for the configurable parameters is greater than the memory configured for Adaptive Server.
At the operating system level, check memory use.
On UNIX machines, there are several commands for checking memory use. Following are examples of two of these commands:
% /etc/pstat -s
44076k allocated + 8920k reserved =52996k used, 40960k available
% vmstat
procs memory page disk faults cpu r b w avm fre re at pi po fr de sr s0 d1 d2 d3 in sy cs us sy id 4 0 0 0 336 0 1 0 0 0 16 0 1 0 0 0 181 260 399 84 2 14
If processes other than Adaptive Server are leaving memory fragmented, rebooting the operating system may resolve this error.
Start Adaptive Server.
If you still cannot start Adaptive Server, refer to “Adaptive Server does not start after altering configuration” in the chapter “Adaptive Server System Recovery” in the most recent version of Troubleshooting and Disaster Recovery.
Once Adaptive Server is running, use sp_configure either to reduce the value of the configurable parameters (such as number of user connections and number of locks) or to increase the value of the total memory configuration parameter. The total memory parameter controls the size of memory, in 2K units, that Adaptive Server allocates from the operating system.
Refer to the Adaptive Server Enterprise performance and tuning guides and “Configuring Memory” in the System Administration Guide: Volume 2 for information about memory-related configuration parameters.
When you call Sybase Technical Support, have the information on hand that is listed in “Reporting errors”, including the text of your configuration file or sp_configure output.
