Ansicht
Dokumentation

Startup fails, sapstart.sem, startsap, sapstart
Tip-No.: 2033 ( INFO2033 )

Short text

Startup fails, sapstart.sem, startsap, sapstart
Tip-No.: 2033

Symptom

The start of the System fails, as the file sapstart.sem still exists
or if files with owner "root" exist ("permission denied").

Cause

List of possible causes:

1) Error in Startup-Script "startsap" (remedied in the meantime).
A file "sapstart.sem" in the work directory of a unit
( UNIX: "/usr/sap///work") contains a
process ID and a Shared-Memory ID.
An SAP System unit is deemed operational, if
- this file exists and
- a process with this process ID eixsts and
- a Shared-Memory segment with this ID exists.
In the above script, the startup was terminated if the file existed.

2) The unit was not closed in orderly manner.
There are still objects, which still causes problems at startup.

3) Authorization problems
From a previous startup under a privilged user ID ( -> not permitted),
objects still exist (files, shared memories, semaphores, etc.)
to which the current startup under correct, non-privileged ID has no
access authorization, and which therefore cannot be removed.

Solution

Ensure that all of the systems processes have stopped.
If necessary, run the files kill.sap and shutdown.sap in the SAP System
Working-Directory.
( /usr/sap///work ).
Ensure that all IPC objects (shared mem, semaphores, ...) have been
deleted. ( showipc )

Delete file sapstart.sem.
Make sure that no files with foreign owners exist. In correct install-
ation and parameterization, no files exist in this directory that
cannot be deleted, therfore, delete the entire directly if needed.

Attempt a restart.

If problems still occur, search for error notes in the following files:
sapstart.log, sapstart.trc, strerr, stdout, dev_disp,
dev_w, dev_ms.

For problems with the syslog and spool error files search in the log
directory (Unix: '/usr/sap///log")