Ansicht
Dokumentation
Tip-No.: 589 ( INFO589 )
R/3 instance cannot be started
Tip-No.: 589
( INFO589 )
ROGBILLS - Synchronize billing plans
RFUMSV00 - Advance Return for Tax on Sales/Purchases
This documentation is copyright by SAP AG.
Short text
R/3 instance cannot be started
Tip-No.: 589
Symptom
An R/3 instance cannot be started. A consequence of this is that all
SAPTEMU users receive an error message (e.g. connect to disp failed).
Cause
These problems can normally be explained by the fact that the down
loading of the R/3 instance was not done correctly, and operating
system resources are still occupied.
Solution
. log on with the user that normally starts the R/3 instance.
. delete the contents of the work directory (/usr/sap/C11/D.../work/*).
this, of course, should only be done if the instance does not run|
. start again
If you still cannot start the instance correctly, selectively:
. boot the computer (all processes and IPC resources are released)
or:
. kill all the SAP processes in this instance manually (the process
names contain "sap
(processes release the tracks themselves), then, if without
success, use "kill -9
. with command "
occupied by which instance (Sapsysnr). If IPC resources from
instances still exist, but do not run, these can be deleted with
"
BAL Application Log Documentation ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 1417 Date: 20240329 Time: 100853 sap01-206 ( 14 ms )