The exec sapstart or sapstartsrv are not working after a filesystem crash

Solution Verified - Updated -

Issue

After a filesystem crash sapstart or sapstartsrv are not working as expected anymore. If you try to execute the sapstart or sapstartsrv command by hand with the user sidadm you get an abnormal ouput.

  • Simulated corrupted sapstartsrv
$:/usr/sap/RH2/HDB02/exe> ./sapstartsrv.corrupted -h
Segmentation fault (core dumped)
  • Normal behavior of sapstartsrv
$:/usr/sap/RH2/HDB02/exe> ./sapstartsrv -h
Usage:

Run as Service:
  sapstartsrv pf=<Startprofile> [-D] [-u <User>] [-setup_env]
  -D:       Run as daemon
  -u <User>:    Run as user <User>
  -setup_env:   Setup user environment

Installation options:
  -h|-?:    Print usage
  -pf=<Instanceprofile> [-nosystemd] -reg   Register in /usr/sap/sapservices
  -pf=<Instanceprofile> -unreg          Unregister in /usr/sap/sapservices

Internal use only options:
  -pf=<Instanceprofile> -sapparam:  Echo all profile parameters to stdout
  -pf=<Instanceprofile> -defparam:  Echo all default profile parameters to stdout
  -pf=<Instanceprofile> -detailparam [<default profile> [<profile> [<format>]]]:    Echo profile parameter details to stdout

  • Normal behavior of sapstart
$:/usr/sap/RH2/HDB02/exe> ./sapstart
./sapstart=>sapparam(1c): No Profile used.
./sapstart=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
*** ERROR => CTrcOpen: fopen dev_sapstart

---------------------------------------------------
trc file: "dev_sapstart", trc level: 1, release: "753"
---------------------------------------------------
**** unknown SAPSYSTEMNAME.
(160113) Exiting with Return-Code -101. (Unknown Sap-System-Name)

Environment

  • Red Hat Enterprise Linux for SAP Solutions

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content