This section describes how to store executables locally for an SAP instance and automatically keep them up-to-date with the central copies.
Prerequisites
Required Disk Space
Ensure that each host server that will use local SAP executables has several hundred megabytes (depending on the SAP release) of free disk space for the executables.
Procedure
Carry out the following actions using the user
<sid>adm:In an SAP system with the system ID C11:
mv /usr/sap/C11/SYS/exe/run sr/sap/C11/SYS/exe/ctrun
A standard installation usually contains a symbolic link or soft link from
/usr/sap/<SID>/SYS/exe/ctrun to the local directory /usr/sap/<SID>/SYS/exe/dbg. The directory /usr/sap/<SID>/SYS/exe/dbg, in turn, has a symbolic link to the central directory /sapmnt/<SID>/exe (see graphic under Functionality of Automatic Adjustment).Command for displaying soft link assignments:
ls -l /usr/sap/C11/SYS/exe
mkdir /usr/sap/C11/SYS/exe/run
The directory must be local to each host system. That is, it must be located on a disk that is physically connected to the host system.
Alternative: create a local executables directory using any name that you wish and define a softlink from
/usr/sap/C11/SYS/exe/run to this directory.mkdir <executables directory>
ln -s <executables directory> /usr/sap/C11/SYS/exe/run
cp /usr/sap/C11/SYS/exe/ctrun/startsap
/usr/sap/C11/SYS/exe/run/startsap
See also:
sapcpe Program.Note that the specified path names and commands are intended for the UNIX environment. If you are using a different platform, you must adapt these specifications to your operating system. The objective here is to build the constellation shown in the graphic under
Functionality of Automatic Adjustment.