HP Serviceguard Extension for SAP (SGeSAP) Installation Step IS050, Filename localcopy checkexist

Installation Step: IS050

This step describes how to create a local copy of the SAP binaries. The step is mandatory for legacy packages. It is also required to do this, if a module-based package is used for a system with SAP kernel <7.0.

Check if the Central Instance host and all application servers have a directory named /usr/sap/<SID>/SYS/exe/ctrun. If the directory exists, this step can be skipped. The system is already using local executables through sapcpe.

To automatically synchronize local copies of the executables, SAP components deliver the sapcpe mechanism. With every startup of the instance, sapcpe matches new executables stored centrally with those stored locally. Figure 3-1 shows a SAP filesystem layout with sapcpe activated for two Application Servers.

Figure 3-1 sapcpe Mechanism for Executables

To create local executables, the SAP filesystem layout needs to be changed. The original link /usr/sap/<SID>/SYS/exe/run needs to be renamed to /usr/sap/<SID>/SYS/exe/ctrun. A new local directory /usr/sap/<SID>/SYS/exe/run will then be required to store the local copy. It needs to be initialized by copying the files sapstart and saposcol from the central executable directory /sapmnt/<SID>/exe. Make sure to match owner, group and permission settings.

Do not forget to set the s-bit of saposcol. To complete the process, a plain text configuration file is needed that tells sapcpe which files need to be included in the copying process.

A file of this type is usually called sapcpeft. If sapcpeft exists, sapcpe will automatically be executed as the first step of the next instance restart. It needs to be created in the central executable directory. For each additional file in the central executable directory it needs to contain a line with the following format:

<filename> local_copy check_exist

SAP also delivers template file lists within the central executable directory. These files have a filename of the format *.lst. The following files override sapcpeft: frontend.lst, instance.lst, instancedb.lst, tools.lst and inhouse.lst. Either the *.lst files should get removed, or they should be used instead of sapcpeft. In this case, they need to be changed to include all executables and libraries.

50 Step-by-Step Cluster Conversion