Академический Документы
Профессиональный Документы
Культура Документы
Two places you need to check: EventViewer (Application and System logs) and the SAP
Management Console (MMC).
Event Viewer can provide useful information and it may help you pinpoint where the problem
resides. The SAP MMC gives you the
ability to visually see the system status (green, yellow or red lights), view the work processes
status and view the developer traces,
which are stored in the "work" directory. Example: /usr/sap/TST/DVEBMGS00/work.
For a central SAP instance to start successfully, both the message server and the dispatcher
need to start. If one of them or both fail
to start, users cannot log in to the system. The following scenarios will illustrate possible causes
of why an SAP instance might not
start and the reason of the message:
"DISPATCHER EMERGENCY SHUTDOWN ".
Developer Traces:
dev_disp Dispatcher developer trace
dev_ms Message Server developer trace
dev_wp0 Work process 0 developer trace
The "services" file, which contains TCP and UDP services and their respective port numbers.
This plain-text configuration file is
Solution
Edit the instance system profile at the OS level under /usr/sap//sys/profile and lower the value
assigned to "abap/buffersize". Then,
restart the instance. Also, it's important to find out if any other memory parameter were
changed. If not, the system should start once
the adequate memory allocation has been set to the the "abap/buffersize" parameter.
Output