Case

When starting saposcol you may see the error in logs “saposcol is not running”

In order to be able to start saposcol successfully, you have to adapt its owner and file permissions properly

Solution

OS level, for example on unix/linux, change saposcol owner and file permissions after stopping and clearing shared memory segment by

# /usr/sap/SID/SYS/exe/run/saposcol -k

# /usr/sap/SID/SYS/exe/run/saposcol -c

# chown root:sapsys /usr/sap/SID/SYS/exe/run/saposcol

# chmod 4755 /usr/sap/SID/SYS/exe/run/saposcol