On your Linux, SAP binaries do not start properly. One of the following error messages displayed on the screen or in the logs or in the trace files:
1. GLIBC library related messages such as
/lib64/libc.so.6: version `GLIBC_2. 11' not found (required by disp+work)
/lib64/libc.so.6: version `GLIBC_2.10' not found (...)
/lib64/libc.so.6: version `GLIBC_2.9' not found (...)
/lib64/libc.so.6: version `GLIBC_2.8' not found (...)
/lib64/libc.so.6: version `GLIBC_2.7' not found (...)
/lib64/libc.so.6: version `GLIBC_2.6' not found (...)
/lib64/libc.so.6: version `GLIBC_2.5' not found (...)
/lib64/tls/libc.so.6: version `GLIBC_2.4' not found (... )
2. ICU library related messages such as
Could not open the ICU common library.
The following files must be in the path described by the environment variable "LD_LIBRARY_PATH":
libicuuc.so.40, libicudata.so.40, libicui18n.so.40 [nlsui0_mt. c 1544]
Linux, GLIBC_2.7, libc.so.6, 7.20 EXT, 720_EXT, 721_EXT, 7.38, 738, 7.40, 740, 640_EX2, 46D_EX2
1. The Linux error message "libc.so.6: version `GLIBC_<version>' not found" generally appears if you run binaries that are not compiled for your Linux operating system release, for example
- The 7.20 EXT kernel and other 7.20 EXT components such as SAP IGS or brtools require SuSE Linux Enterprise Server (SLES) 11 SP1 or RedHat Enterprise Linux (RHEL) 6 (note 1563102), because they are compiled against glibc-2.11.
- The 7.21 EXT kernel as well as the 7.38 and 7.40 kernel also require SLES 11 SP1 or RHEL 6 (note 1563102), because they are compiled against glibc-2.11.
- The 46D_EX2 and 640_EX2 kernels and other components require SLES 10 or RHEL 5 (note 1271224), because they are compiled against glibc-2.4.
2. The libicu*.so.40 libraries are delivered starting with the 7.20 EXT kernel (7.21 EXT, 7.38 and 7.40 kernels include the libicu*.so.40 libraries as well). If you install EXT kernel components (such as IGS) without having the EXT kernel installed you get the error message about missing libicu*.so.40 libraries.
3. The libicu*.so.50 libraries are delivered starting with SAP kernel 7.40.
It is known that current SAP upgrade processes lack some precision and easiness, especially regarding operating system and database alternatives, so that it is likely possible to make mistakes. This could have various reasons in different components: incomplete PPMS (SAP Product and Production Management System) information, deficiencies in Solution Manager Maintenance Optimizer (MOpz) or upgrade tools including EHPI or SUM, incomplete or bad documentation, and last but not least human mistakes such as selecting the wrong alternative (e.g. the 7.20 EXT variant) during the upgrade process.
The current upgrade tools do not consider all database or operating system prerequisites such as those for the EXT kernel and thus both kernels could be displayed for human selection even if operating system prerequisites for 7.20 EXT are not met. If you then select both non-EXT and EXT kernels, the upgrade process will not complain, and the latter one (i.e. the EXT kernel) will be installed without any further check. This installation will fail if the operating system prerequisites for 7.20 EXT are not met.
1. If you want or must use the 7.20 EXT, 7.21 EXT, 7.38, 7.40, 640_EX2, or 46D_EX2 kernel:
- Install or upgrade your Linux operating system so that you meet the minimal requirements (7.20 EXT: note 1563102, 640_EX2, 46D_EX2: note 1271224).
If you have accidently selected an EXT or EX2 kernel on an older Linux system:
- Make sure that you do not use an EXT or EX2 kernel! Please install the non-EXT or non-EX2 kernel/component instead. Be careful when upgrade tools let you choose the 7.20 or the 7.20 EXT kernel. Maybe it is needed to manually extract/copy the files from a non-EXT or non-EX2 SAR archive into the corresponding directory.
2. Consider the operating system requirements for all components and follow the instructions above for all components.