sapservices-move(8)

📦 version 0.9.6+git.1791548114.2a86b96, in opensuse-leap 16.0

💅 sapservices-move — a little intro, bestie

okay so this is the manual page for sapservices-move(8), from the SAPStartSrv corner of the universe, and it's genuinely so specific that it's iconic. it's a tiny helper script with a very dramatic job: it hides a file at boot. that's it. that's the whole vibe. ✨

🌸 NAME

sapservices-move — hiding the sapservices file from the sapinit service at system boot.

🎀 SYNOPSYS

sapservices-move [ --help | --version | --hide | --unhide ]

🦋 DESCRIPTION

so sapservices-move is called by the systemd services sapping and sappong for the express purpose of temporarily hiding the sapservices file from the sapinit service at system boot. that's the whole glow-up. 🔥

  • sapping is hiding the sapservices file from the sapinit service at system boot.
  • sappong is unhiding the sapservices file after the sapinit service has been started.

why would anyone need to hide a file, you ask? because hiding the sapservices file from sapinit is necessary in certain HA cluster setups, no cap. the affected ones are HA clusters for SAP enqueue replication where cluster nodes have concurrent access to all instance working directories — like, say, through a simplified NFS mount structure. in those environments sapstartsrv needs to be started specific for each SAP instance (e.g. ASCS/ERS), so you don't get side effects with other instances. it's giving very careful, very intentional. 💅

meanwhile the sapinit service does not take such environments into account — it just starts sapstartsrv for all the instances listed in the sapservices profile definition file. and that could damage the working directory content of already running instances, even on remote cluster nodes. 😭 so yeah, this matters.

the script is intended to be called at boot time. administrative use during regular operations is not intended. consequently, calling the sapinit script during regular operation will cause trouble in an above-mentioned HA cluster — even on remote nodes. fr fr, be careful.

for details on concept and requirements, see ocf_suse_SAPStartSrv(7). 🧚

✨ OPTIONS ✨

  • --help — show help 🫶
  • --version — show version
  • --hide — hide the sapervices file from sapinit
  • --unhide — unhide the previously hidden sapservices file 🙈

🌈 EXAMPLES

  • enable both services at boot time 👑
# systemctl enable sapping sappong
  • show status of service sapping, including content of the moved sapservices file 💖
# systemctl status sapping
  • show journal log entries for service sapping since 2020-02-02 20:20:20 ⭐
# journalctl --unit=sapping --since="2020-02-02 20:20:20"

💀 EXIT STATUS

  • 0 — successful program execution. slay. ✨
  • >0 — usage, syntax or execution errors. not slay. 😭

🍓 FILES

  • /usr/sbin/sapservices-move — systemd service executable
  • /usr/lib/systemd/system/sapping.service , /usr/lib/systemd/system/sappong.service — systemd service definitions
  • /usr/sap/sapservices — SAP profiles definition file, used by sapstartsrv et al.
  • /usr/sap/$SID/SYS/profile/$SID_ASCS$nr_$virhost , /usr/sap/$SID/SYS/profile/$SID_ERS$nr_$virhost — SAP instance profiles
  • /etc/init.d/sapinit — System V SAP init script to enable the SAP start framework, including the sapstartsrv service for all entries in the sapservices file

🙈 BUGS

in case of any problem, please use your favourite SAP support process to open a request for the component BC-OP-LNX-SUSE. (yes, the favourite one. pick a good one. 🫶)

👑 SEE ALSO

ocf_heartbeat_SAPStartSrv(7) , sapping(7) , systemctl(1)

💜 AUTHORS

F.Herschel, L.Pinne

(c) 2020-2026 SUSE LLC

sapservices-move comes with ABSOLUTELY NO WARRANTY. For details see the GNU General Public License at http://www.gnu.org/licenses/gpl.html

and that's the whole page, bestie 🎀 — brought to you by sapservices-move(8), dated 15 Aug 2025, with the manual name living right up at the top where it belongs. mwah. 💋

📦 where this page comes from