sap note

SAP Note: 941735. Linux kernels

Summary

Symptom

Recommendation for parameterization of 64-bit Linux systems.

Other terms

Linux memory management, es/implementation, STD, MAP, TMPFS, /dev/shm, 64-bit, em/initial_size_MB

Reason and Prerequisites

For SAP on Linux, two different memory management systems are available. You can switch between the two systems using the SAP instance profile parameter es/implementation:

MAP implementation (es/implementation=map)

This variant is mainly used for 32-bit systems, and is described in detail in Note 386605.

As of SAP kernel 6.20, an SAP system on Linux uses the MAP implementation by default, in which only the currently active user context is displayed in the address space of the work process.

STD implementation (es/implementation=std)

With this variant, the memory management of an SAP system on Linux is the same as on standard UNIX systems. This means that all user contexts are displayed in the address space at the same time, which means that this variant is only available for 64 bit systems.

While the MAP implementation should be used exclusively on 32-bit Linux in more cases, both variants can be used on 64-bit systems. However, since there are no longer any 32-bit restrictions, there is no longer any need to use the special MAP implementation on 64-bit Linux systems .

For this reason, the STD implementation for SAP systems on 64-bit Linux is activated by default as of SAP Kernel 7.10.

Solution

If you want to use the STD implementation with older SAP kernels, you can activate it using the profile parameter es/implementation=std.

Relevant parameters for the STD implementation

A) SAP profile parameters em/initial_size_MB

This parameter specifies how much Extended Memory is available to the SAP system.

In the SAP Extended Memory, there are additional SAP internal memory areas, which cannot be directly accessed by the user contexts. These include the areas that are configured using the parameters em/global_area_MB and abap/shared_objects_size_MB. Note: For the user contexts in the system, only the difference of

em/initial_size_MB - (em/global_area_MB + abap/shared_objects_size_MB)

can be used as Extended Memory.

ztta/roll_extension

This parameter specifies how much SAP Extended Memory is available to an individual user context.

This quota can be set differently for dialog and background work processes if necessary. To do this, use the parameters ztta/roll_extension_dia for dialog work processes or ztta/roll_extension_nondia for background work processes.

The three profile parameters used with the MAP implementation (em/address_space_MB, em/max_size_MB and PHYS_MEMSIZE) are not relevant if you use the STD implementation.

B) Linux operating system parameters

The following Linux kernel parameters can be configured using the sysctl interface. To do this, you must edit the file /etc/sysctl.conf accordingly:

kernel.shmmax

This kernel parameter specifies how large an individual SysV Shared Memory Segment is allowed to be. In the case of an STD implementation, the parameter must be set sufficiently large in order to allow em/initial_size_MB. The value is specified in the unit Bytes so that "21474836480", for example, permits segments of 20 GB.

kernel.shmall

This kernel parameter specifies how much SysV Shared Memory is available in the Linux system as a whole. As an estimate for the requirements of the SAP system, you can use the total of the SAP Extended Memory (em/initial_size_MB) + SAP buffer (transaction ST02 -> Detail analysis menu -> Storage, row with the entry "Total").

If several SAP systems are running on a Linux server, the requirements increase accordingly. The same applies for databases that may be operating on the same Linux server.

As a configuration recommendation, kernel. shmall can be configured as the amount of virtual memory in the Linux system (RAM + Swap).

The value is specified in the unit "4 KB blocks", so that "5242880", for example, permits 20 GB SysV Shared Memory in the Linux system as a whole.

TMPFS

With the STD implementation, the SAP Extended Memory is no longer stored in the TMPFS (under /dev/shm). However, the TMPFS is required by the Virtual Machine Container (VMC). For this reason, we still recommend the same configuration of the TMPFS:

75% (RAM + Swap) is still recommended as the size.Points to remember when using the STD implementation

Background work processes now use memory close to the process (heap) as the first large memory type. The allocation sequence for "NonDia" work processes is as follows:

1. Roll memory (ztta/roll_first),

2. Heap memory (abap/heap_area_nondia),

3. Roll memory (ztta/roll_area - ztta/roll_first),

4. Extended Memory (ztta/roll_extension(_nondia)).

In the case of dialog work processes, the allocation sequence remains unchanged from that used in the MAP implementation:

1. Roll memory (ztta/roll_first),

2. Extended Memory (ztta/roll_extension(_dia)),

3. Roll memory (ztta/roll_area - ztta/roll_first),

4. Heap memory (abap/heap_area_dia).

The allocation sequence can be changed using the RSMEMORY report.

In transaction ST02, the "In Memory" display for the "Extended Memory" entry shows the SAP Extended Memory available for the SAP instance. The value of the parameter em/initial_size_MB is used as a basic value. However, the Extended Memory is not automatically increased to the value of em/max_size_MB with the STD implementation.

Frequent problems in connection with the STD implementation

The following problems or error messages may occur when you carry out the STD implementation:

ERROR shmget() (28: No space left on device)

Example from dev_w0:

...M SHM_ROLL_ADM (addr: 0x2a99dc7000, size: 2672386)M SHM_PAGING_ADM (addr: 0x2bb1ae6000, size: 656416)I *** ERROR => shmget(13040,112000000,2016) (28: No space left on device) [shmux.c 1407]I *** ERROR => shmget(13040,112000000,992) (28: No space left on device) [shmux.c 1407]I *** ERROR => Shm Pool Create Error. PoolKey=40, Key=48. [shmux.c 1892]... Example from dev_disp:

...EmInit: MmSetImplementation( 2 ).MM global diagnostic options set: 0client 0 initializing ....InitFreeListblock size is 4096 kByte.Using implementation stdEsStdUnamFileMapInit: shmget() of 10737418240 bytes failed.errno = 28(No space left on device)EsStdInit: unable to allocate 10240 MBEsStdInit: try to allocate 8192 MBEsStdUnamFileMapInit: shmget() of 8589934592 bytes failed.errno = 28(No space left on device)EsStdInit: unable to allocate 8192 MB...EsStdInit: try to allocate 8 MB

EsStdUnamFileMapInit: shmget() of 8388608 bytes failed.errno = 28(No space left on device)EsStdInit: unable to allocate 8 MBEsStdInit: try to allocate 4 MB*** ERROR => EsStdInit: unable to allocate 10240 MB [esuxi.c 401]*** Error 11 while initializing OS dependent part.*** ERROR => DpEmInit: EmInit (1) [dpxxdisp.c 9559]*** ERROR => DpMemInit: DpEmInit (-1) [dpxxdisp.c 9486]*** DP_FATAL_ERROR => DpSapEnvInit: DpMemInit*** DISPATCHER EMERGENCY SHUTDOWN ***... According to 'man 2 shmget' , the error "No space left on device" (ENOSPC) signifies that the requested memory exceeds the system limit for Shared Memory (SHMALL).

Therefore, check the value of the sysctl parameter kernel. shmall (/proc/sys/kernel/shmall).

ERROR shmget() (22: Invalid argument)

Example from dev_w0:

...A Fri Oct 22 16:18:47 2005AA ---PXA-------------------------------------------A PXA INITIALIZATIONA System page size: 4kb, admin_size: 31788kb.I *** ERROR => shmget(11906,1126400000,2016) (22: Invalid argument) [shmux.c 1904]A RABAX in run level 1 A RABAX in unkown environment: task_type=0, run level=1, rabax state=80000000... According to 'man 2 shmget', the error "Invalid argument" (EINVAL) signifies that you try to create a Shared Memory Segment (in this case the ABAP program buffer (abap/buffersize) that is larger than permitted by SHMMAX.

Therefore, check the value of the sysctl parameter kernel. shmmax (/proc/sys/kernel/shmmax).

Profile parameter "ES/TABLE = SHM_SEGS"

In particular, after an operating system change to Linux, ensure that the profile parameter "ES/TABLE" is not set using the SAP profiles (in other words, make sure that the SAP kernel default value "ES/TABLE = UNIX_STD" is reported).

For example, if the instance profiles are copied from Advanced Interactive eXecutive (AIX), "ES/TABLE = SHM_SEGS" may be set. As a result, the SAP system on Linux still uses the AIX memory management, even if "es/implementation = std" is set. On Linux, this may result in a poor performance and increased paging.

In the SAP logs (dev_w*), setting "ES/TABLE = SHM_SEGS" results in the following:

...X EmInit: MmSetImplementation( 2 ).X MM global diagnostic options set: 0X EM/TOTAL_SIZE_MB = 262144... Remove parameters such as ES/TABLE, ES/SHM_SEG_SIZE, and EM/TOTAL_SIZE_MB from the profiles and restart the instance.

Correct log entries are as follows:

...X EmInit: MmSetImplementation( 2 ).X MM global diagnostic options set: 0X client 0 initializing ....X Using implementation std...

Header Data

Release Status: Released for CustomerReleased on: 12.11.2009 08:20:42Master Language: GermanPriority: Recommendations/additional infoCategory: ConsultingPrimary Component:BC-OP-LNX Linux

Affected Releases

SoftwareComponent

ReleaseFrom

ReleaseTo

ReleaseAnd

subsequentKRNL64NUC 6.40 6.40 6.40 XKRNL64NUC 7.00 7.00 7.00 XKRNL64UC 6.40 6.40 6.40 XKRNL64UC 7.00 7.00 7.00 XKRNL64UC 7.10 7.10 7.10 X

Subscribe | Add to Favorites

Note 171356 - SAP software on Linux: Essential information

Summary

Symptom

You want to install SAP software on Linux.

Other terms

Redhat, redhat, RH, SuSE, Suse, suse, Swapspace, swapspace, swap-space, ServicePack, IA-64, IA64, x86_64, AMD, Opteron, EM64T, POWER, zSeries, System z


You want to install SAP software on Linux. You require the appropriate Linux distribution and permitted hardware to do this.After you successfully install Linux and before you carry out the actual SAP installation, you must also take some other matters into consideration that are not mentioned in the installation guide and are therefore addressed in this note.

Solution

******************************************** This note is updated on a regular basis ********************************************

Contents

I/.... Released Linux Distributions:II/... Supported hardwareIII/.. Other Linux environments that are supported.IV/... Special notes about installing the operating systemV/ .... General notes about installing the operating systemVI/ ... SAP software: saplocalesVII/ .. SAP software: NPTLVIII/ . SAP software: Additional comments:IX/ .., Notes that are specific to the databaseX/ .... Notes about IBM PowerXI/ ... Mounting installation CDs and installation DVDsXII/ .. Adding Linux application servers to existing SAP systems

https://service.sap.com/sap/support/notes/171356

XIII/ . Using virtualization technologiesXIV/ .. Use of Raw Devices, "Journaling File system" and LVM

I/ Released Linux Distributions

One of the following Linux distributions is required for installing SAP software on Linux:

1. 64-bit systems: SUSE Linux Enterprise Server 11

o SUSE Linux Enterprise Server 11 for AMD64 & Intel EM64T (SLES11-x86_64)

o SUSE Linux Enterprise Server 11 for IBM Power (SLES11-PPC)

o SUSE Linux Enterprise Server 11 for IBM System z(SLES11-ZS, see Note 81737 for information about supported Linux kernels, glibc versions and required packages)

o SUSE Linux Enterprise Server 11 for Intel Itanium2 Proc. Family (SLES11-IPF)

SUSE Linux Enterprise Server 10

o SUSE Linux Enterprise Server 10 for AMD64 & Intel EM64T (SLES10-x86_64)

o SUSE Linux Enterprise Server 10 for IBM Power (SLES10-PPC)

o SUSE Linux Enterprise Server 10 for IBM System z(SLES10-ZS, see Note 81737 for information about supported Linux kernels, glibc versions and required packages)



o SUSE Linux Enterprise Server 9 for AMD64 & Intel EM64T(SLES9-x86_64, for release information, see Note 816097)

o SUSE Linux Enterprise Server 9 for IBM POWER (SLES9-PPC)

o SUSE Linux Enterprise Server 9 for zSeries(SLES9-ZS, see Note 81737 for information about supported Linux kernels, glibc versions and required packages)



o SUSE Linux Enterprise Server 8 for zSeries(SLES8-ZS, see Note 81737 for information about supported Linux kernels, glibc versions and required packages)

o SUSE Linux Enterprise Server 8 for Intel Itanium2 Proc. Family(SLES8-IPF, for release information, see Note 623653)

Red Hat Enterprise Linux 5

o Red Hat Enterprise Linux 5 for AMD64 & Intel EM64T (RHEL5-x86_64)

o Red Hat Enterprise Linux 5 for IBM Power (RHEL5-PPC)

o Red Hat Enterprise Linux 5 for Intel Itanium (RHEL5-IA64)

o Red Hat Enterprise Linux 5 for IBM System z (RHEL5-ZS, see Note 81737 for information about supported Linux kernels, glibc versions and required packages)


o Red Hat Enterprise Linux 4 for AMD64 & Intel EM64T(RHEL4-x86_64, for release information, see Note 816097)

o Red Hat Enterprise Linux 4 for IBM POWER (RHEL4-PPC)




2. 32-bit systems:o SUSE Linux Enterprise Server 10 for x86 (SLES10-X86)

o SUSE Linux Enterprise Server 9 for x86 (SLES9-X86)

o SUSE Linux Enterprise Server 8 (SLES8)

o SUSE Linux Standard Server 8(Note: As a result, all statements used for the 32-bit version of SUSE Linux Enterprise Server 8 also apply for the 32-bit version of the SUSE Linux Standard Server 8.)

o Red Hat Enterprise Linux 5 for x86 (RHEL5-X86)

o Red Hat Enterprise Linux 4 for x86 (RHEL4-X86)

o Red Hat Enterprise Linux 3 (RHEL3)

The following Linux distribution was also released for 32-bit systems and R/3 Releases 4.x, but not for the recommended SAP kernel in the EXT version (4.0B_EXT, 4.5B_EXT, 4.6D_EXT):

o Red Hat Enterprise Linux 2.1 (RHEL2.1)

If you want to change over to the EXT kernel and already use an earlier Linux distribution, you need to upgrade to one of the Linux distributions mentioned above.

Up to and including SAP Release 4.6x, the following technically obsolete Linux distributions are also available for 32-bit systems:

o SUSE Linux Enterprise Server 7 (SLES7)(Note: see Note 750884 for information about the end of maintenance for SUSE SLES7)

o SUSE Linux Enterprise Server (SLES)

o Red Hat 7.1 (limited release, see Note 513277)

o Red Hat 6.2

o Red Hat 6.1 Enterprise Version 1.0 (special version of Red Hat 6.1)

For further information about this, see Note 171356 (up to and including Version 173).

As soon as you use SAP software on one of the specified Linux distributions, we strongly recommend that you take out a service contract. You can do this via the manufacturer of the Linux distribution or via an OEM provider, who will offer an equal level of support for one of the distributions certified by SAP. Otherwise, support may be denied if errors occur in connection with the operating system.

II/ Supported hardware

Note that only the host types released by the hardware partners are suitable for using SAP software productively on Linux.For current information about this, see the following SAP Notes: 606107 (Bull) 1403020 (Cisco) 300900 (Dell) 171383 (Fujitsu Siemens) 171371 (HP) 171380 (IBM) 765424 (IBM POWER) 411970 (IBM zSeries) 1379130 (NEC) 907727 (SGI) 597470 (SUN) 832402 (Unisys)

Furthermore, you can find information on the Internet: http://www.sap.com/linux (Link: "Supported Platforms")

If you are unsure about what to do, you can contact the hardware partners that are represented in SAP LinuxLab, for example by email: [email protected]

Other Linux environments that are supported.

Using SAP software is also permitted in certain Linux environments.For current information about this, see the following SAP Notes: 1278782 (Egenera) 1266874 (Symantec)

If you are unsure about what to do, contact the SAP LinuxLab, for example by email: [email protected]

IV/ Special notes about installing the operating system

Red Hat Linux: InstallationPrior to the installation, refer to the notes corresponding to your Red Hat version from the following list: 1048303 (Red Hat Enterprise Linux 5) 722273 (Red Hat Enterprise Linux 3 and 4) 625674 (RHEL 2.1: Notes on installation) 618173 (RHEL 2.1: on Red Hat Enterprise Linux 2.1)

SUSE Linux: InstallationPrior to the installation, refer to the note corresponding to your SUSE version from the following list: 1310037 (SUSE Linux Enterprise Server 11: Installation notes) 958253 (SUSE Linux Enterprise Server 10: Installation notes)

797084 (SUSE Linux Enterprise Server 9: Installation notes) 767814 (SUSE Linux Enterprise Server 8: Installation notes)

o Among other things, this note describes the "sapinit" RPM (or up to and including SLES 9 Service Package 2: "SUSE-sapinit" RPM). This should be installed in order for the parameters of the Linux kernel to be set correctly.

o If you use the BRTOOLS (for example brbackup) delivered by SAP, problems may arise when the system compresses data files. As of SLES 8, Novell SUSE does not deliver the "compress" program that is otherwise used on UNIX for licensing reasons. The problem can be avoided if you set the following parameters in the file init<SID>.sap:

compress_cmd = "gzip -c $ > $" uncompress_cmd = "gunzip -c $ > $"

V/ General notes about installing the operating system System language

You must select English as the operating system language on all Linux hosts that are running SAP software.

Swap spaceWhile the Linux distribution is being installed, create partitions of the type "swap" when you organize the hard disk(s).Recommended total size: Twice the main memory structure (2 x RAM). According to Note 153641, a swap space of 20 GB is generally sufficient on 64-bit Linux for operating an SAP system (including the database).For earlier 32-bit Linux versions, the maximum size of a swap partition is 2 GB, but if you require more space, distribute the swap space over multiple swap partitions.The Linux kernel does not usually require much swap space, since other limits have already been reached before the swap space has reached full capacity ("late swap allocation").However, if you discover that more swap space is required when using SAP software, you can use the distribution-specific tools to increase your swap space at any time.

HostnameThe "hostname" command must only return the host name and not the "Fully Qualified Domain Name" (for example: Fully Qualified Domain Name: ls3001.wdf.sap-ag.de; required output from "hostname": ls3001). Distribution-specific tools are available to change the host name.

Updating RPM packagesThe distributors (Novell SUSE and Red Hat) regularly provide updates for your

software. The distributors test these updates with regard to compatibility with the SAP software before releasing them. From an SAP point of view, these updates can be imported in the productive environment immediately after they are available. This compatibility is guaranteed only if the original packages of the distributors are used, to which a customer is entitled within the framework of a valid support contract with the distributor or an authorized OEM.The same also applies for the "Collections of updates", that is "Service Packs" (Novell SUSE) or "Updates" (Red Hat).We recommend that you import the latest available "Service Pack" (Novell SUSE) or the latest "Update" (Red Hat). You should use the latest available installation media when you are installing this.If an update to an imported package (for example, kernel or glibc) unexpectedly does not work, return to the last Service Pack or update level that worked.

Note for all "Service Packs" and "Updates": If you are using a non-Unicode version of the SAP software, you must install the "saplocales" again after every update of the "glibc" RPM (see below or Note 516716).

Also note: For information about assessing customer modifications to a Linux kernel, see Note 784391.

VI/ SAP software: saplocales

For non-Unicode versions of the SAP software, you may have to install another RPM package that adjusts the locales of the Linux system to the SAP standard.

If you set up Unicode systems only, you can ignore the next section of this note.

Note 187864 contains further important information about locales on Linux. It is therefore essential that you refer to this note.

If you have to import a "saplocales" RPM, use the one that matches your operating system version.

These are the available "saplocales" packages:

1) Red Hat Enterprise Linux 2.1

saplocales-2.20.4-1 # adjusted SAP code pages (see saplocales_rhel21_i386_version-1.zip, attached to this note)

2) Red Hat Enterprise Linux 3 (32-bit systems)


3) Red Hat Enterprise Linux 3 (64-bit systems)

saplocales-2.3.2-5 # adjusted SAP code pages saplocales-32bit-2.3.2-5 # adjusted SAP code pages (see saplocales_rhel30_ia64_version-5.zip, attached to this note)

4) Red Hat Enterprise Linux 4 for x86


5) Red Hat Enterprise Linux 4 for AMD64 & Intel EM64T

saplocales-2.3.4-4 # adjusted SAP code pages (see saplocales_rhel40_x8664_version-4.zip, attached to this note)

6) Red Hat Enterprise Linux 4 for IBM POWER

saplocales-2.3.4-4 # adjusted SAP code pages (see saplocales_rhel40_ppc64_version-4.zip, attached to this note)

7) Red Hat Enterprise Linux 4 for Intel Itanium

saplocales-2.3.4-4 # adjusted SAP code pages (see saplocales_rhel40_ia64_version-4.zip, attached to this note)

8) Red Hat Enterprise Linux 5 for x86

saplocales-2.5-2 # adjusted SAP codepages (see saplocales_rhel5_i386_version-2.zip, attached to this note)

9) Red Hat Enterprise Linux 5 for AMD64 & Intel EM64T

saplocales-2.5-2 # adjusted SAP codepages (see saplocales_rhel5_x86_64_version-2.zip, attached to this note)

10) Red Hat Enterprise Linux 5 for IBM POWER

saplocales-2.5-2 # adjusted SAP codepages (see saplocales_rhel5_ppc64_version-2.zip, attached to this note)

11) Red Hat Enterprise Linux 5 for IBM System z

saplocales-2.5-2 # adjusted SAP codepages (see saplocales_rhel5_s390x_version-2.zip, attached to this note)

12) Red Hat Enterprise Linux 5 for Intel Itanium

saplocales-2.5-2 # adjusted SAP codepages (see saplocales_rhel5_ia64_version-2.zip, attached to this note)

13) SUSE Linux Enterprise Server 8 (32-bit systems)

saplocales-2.2.5-4 # adjusted SAP code pages (see saplocales_sles8_i386_version-4.zip, attached to this note)

14) SUSE Linux Enterprise Server 8 for IBM zSeries

saplocales-2.2.5-2 # adjusted SAP code pages saplocales-32bit-2.2.5-2 # adjusted SAP code pages (see saplocales_sles8_s390x_version-2.zip, attached to this note)

15) SUSE Linux Enterprise Server 8 for Intel Itanium2 Proc. Family

saplocales-2.2.5-3 # adjusted SAP code pages saplocales-32bit-2.2.5-3 # adjusted SAP code pages (see saplocales_sles8_ia64_version-3.zip, attached to this note)

16) SUSE Linux Enterprise Server 9 for x86

saplocales-2.3.3-11 # adjusted SAP code pages (see saplocales_sles9_i386_version-11.zip, attached to this note)

17) SUSE Linux Enterprise Server 9 for AMD64 & Intel EM64T

saplocales-2.3.3-11 # adjusted SAP code pages (see saplocales_sles9_x86_64_version-11.zip, attached to this note)

18) SUSE Linux Enterprise Server 9 for IBM POWER

saplocales-2.3.3-11 # adjusted SAP code pages (see saplocales_sles9_ppc64_version-11.zip, attached to this note)

19) SUSE Linux Enterprise Server 9 for IBM zSeries

saplocales-2.3.3-11 # adjusted SAP code pages saplocales-32bit-2.3.3-11 # adjusted SAP code pages (see saplocales_sles9_s390x_version-11.zip, attached to this note)


saplocales-2.3.3-11 # adjusted SAP code pages saplocales-32bit-2.3.3-11 # adjusted SAP code pages (see saplocales_sles9_ia64_version-11.zip, attached to this note)

21) SUSE Linux Enterprise Server 10 for x86

Up to SLES 10 Service Pack 1: saplocales-2.4-2 # modified SAP codepages (see saplocales_sles10_i386_version-2.zip, attached to this note)

As of SLES 10 Service Pack 2: saplocales-2.4-3 # adjusted SAP codepages (see saplocales_sles10_i386_version-3.zip, attached to this note)

22) SUSE Linux Enterprise Server 10 for AMD64 & Intel EM64T

Up to SLES 10 Service Pack 1: saplocales-2.4-2 # modified SAP codepages (see saplocales_sles10_x8664_version-2.zip, attached to this note)

As of SLES 10 Service Pack 2: saplocales-2.4-4 # modified SAP codepages (see saplocales_sles10_x8664_version-4.zip, attached to this note)

23) SUSE Linux Enterprise Server 10 for IBM POWER

Up to SLES 10 Service Pack 1: saplocales-2.4-2 # modified SAP codepages (see saplocales_sles10_ppc64_version-2.zip, attached to this note)

As of SLES 10 Service Pack 2: saplocales-2.4-3 # modified SAP codepages (see saplocales_sles10_ppc64_version-3.zip, attached to this note)

24) SUSE Linux Enterprise Server 10 for IBM System z

Up to SLES 10 Service Pack 1: saplocales-2.4-2 # modified SAP codepages saplocales-32bit-2.4-2 # adjusted SAP code pages (see saplocales_sles10_s390x_version-2.zip, attached to this note)

As of SLES 10 Service Pack 2: saplocales-2.4-3 # modified SAP codepages saplocales-32bit-2.4-3 # adjusted SAP code pages (see saplocales_sles10_s390x_version-3.zip, attached to this note)


Up to SLES 10 Service Pack 1: saplocales-2.4-2 # modified SAP codepages saplocales-32bit-2.4-2 # adjusted SAP code pages (see saplocales_sles10_ia64_version-2.zip, attached to this note)

As of SLES 10 Service Pack 2: saplocales-2.4-3 # modified SAP codepages saplocales-32bit-2.4-3 # adjusted SAP code pages (see saplocales_sles10_ia64_version-3.zip, attached to this note)

26) SUSE Linux Enterprise Server 11:

Use the "sap-locale" RPM package that is provided by Novell via the default update channels (see Notes 187864 and 1310037).

The "saplocales" RPM packages are attached to this note. If this contains a more recent version of the "saplocales" RPM package than mentioned in the note text, use the more recent version. Exception to this rule: SLES 10 up to Service Pack 1:

The attachments to this note are zip archives that you can unpack as shown in the following example:

unzip saplocales_sles10_x8664_version-4.zip

You can import the resulting RPM packages as follows:

rpm -ivh saplocales-2.4-4.x86_64.rpm

Caution: After each "glibc" RPM update, you must import "saplocales" again (see Note 516716).

VII/ SAP software: NPTL

Current Linux distributions (as of Red Hat Enterprise Linux 3 andSUSE Linux Enterprise Server 9) are based on "Native Posix Threading Library" (NPTL). This is an improved implementation of the threading mechanism. It adheres more closely to the POSIX requirements than the previous implementation on Linux ("LinuxThreads").

As regards NPTL, note that some software must first be adjusted to NPTL so that it can continue to work correctly. When you use RHEL 3/4 and SLES 9, you can rely on a compatibility mode, so that problem software can also be used on NPTL. To do this, set the environment variable LD_ASSUME_KERNEL to 2.4.1: Bash Shell: export LD_ASSUME_KERNEL=2.4.1

C shell: setenv LD_ASSUME_KERNEL 2.4. 1

The following SAP software requires you to set the environment variable LD_ASSUME_KERNEL to 2.4.1 before you execute this software.

1) SAP kernels up to and including Version 6.20 (Exception: the current patch level of the SAP kernel 4.6D_EXT and 6.20 are compatible with NPTL.) (Note: Your SAP kernel is not compatible with NPTL if, for example, the call of "disk+work" ends with a "Floating Point Exception".)2) SAPINST3) SAP DB database or MaxDB database, see Note 788272 (Exception: versions for AMD64/EM64T)4) Oracle database: runInstaller,

However, there is also the opposite case that LD_ASSUME_KERNEL cannot be set, or at least not to a value lower than 2.4.21. This applies to the following SAP software:

SAP kernel as of Version 7.00As of Version 7.0, the SAP kernel generates the following error message: "SAP Web Application Server requires NPTL on Linux." "Please refer to section NPTL of SAP note 171356." "Running in LinuxThreads-compatibility mode only allowed while running a SAP upgrade."If the error message occurs during an SAP upgrade, you can ignore it. Otherwise, deactivate the environment variable LD_ASSUME_KERNEL, to avoid getting the error message.

VIII/ SAP software: Additional comments:

SAP kernel 7.10 on RHEL 4 or SLES 9If you want to use the SAP-Kernel 7.10 together with Red Hat Enterprise Linux 4 or SUSE Linux Enterprise Server 9, you must also refer to Note 1021236.

IX/ Notes that are specific to the database

Informix database: Additional installation notes (R/3 4.0B and 4.5B)If you want to install R/3 Release 4.0B or 4.5B together with the Informix database, you must take into account important additional information. In this regard, the subdirectory UNIX/LINUX_32 on the kernel CD contains the file README. Its contents are particularly important if you are trying to avoid problems that are associated with "password encryption" (/etc/pam.d/passwd contains the entry "crypt" instead of "md5").

DB2 UDB database: Additional RPM packages requiredIf you want to use DB2 UDB as a database, you must install the support for the Korn

shell before installing the DB2 database software. The RPM package that you require is called "ksh" (as of SLES 10 and RHEL 5) or "pdksh" (up to SLES 9 and RHEL 4), and it is available on one of the Linux installation CDs.

Additional considerations for DB2 on IBM POWER:

DB2 UDB V8 (as of FixPak 9)

o SLES 9 or higher - IBM XL C/C++ Advanced Editions V7.0/V8.0 for the Linux runtime environment component

o RHEL 4 or higher - IBM XL C/C++ Advanced Editions V7.0/V8.0 for the Linux runtime environment component

DB2 UDB V9

o SLES 9 Service Package 2 or higher - IBM XL C/C++ Advanced Editions V8.0 for the Linux runtime environment component

o RHEL 4 U2 or higher - IBM XL C/C++ Advanced Editions V8.0 for the Linux runtime environment component

You can find further information below in the section "Notes about IBM Power".

Oracle database: Additional RPM packages requiredAdditional considerations for Oracle on IBM POWER:

Oracle 10g:

o SLES 9 or higher - IBM XL C/C++ Advanced Editions V7.0/8.0 for the Linux runtime environment component

o RHEL 4 or higher - IBM XL C/C++ Advanced Editions V7.0/8.0 for the Linux runtime environment component

You can find further information below in the section "Notes about IBM Power".Important: You must meet certain requirements to install Oracle 10g with the "IBM XL C/C++ Advanced Editions V8.0 for the Linux runtime environment component". For more detailed information about this workaround, see Note 975196.

X/ Notes about IBM Power

For DB2 UDB Version V9, V8 (as of FixPak 9) and Oracle 10g, the IBM XL C/C++ runtime environment component ("Runtime") is not delivered with the database. The runtime component must be downloaded separately from IBM. More information is

available at: http://www.ibm.com/software/awdtools/xlcpp/support

Here, search for "Linux Runtime". The runtime component is specific to the Linux kernel version.

Additional prerequisites:The v7.0 runtime component is compatible with the following operating systems supported by SAP.

o Red Hat Enterprise Linux 4 (RHEL4, RHEL4 U1) for IBM POWER

o SUSE LINUX Enterprise Server 9.0 (SLES 9) for IBM POWER

Install the RPM packages of the v7. 0 runtime component in this order:

a) xlsmp.msg.rte-1.5.0b) xlsmp.rte-1.5.0c) vacpp.rte-7.0.0

The v7.0.1 runtime component is compatible with the following operating systems supported by SAP.

o Red Hat Enterprise Linux 4 Update 2 (RHEL4 U2) or higher for IBM POWER

o SUSE LINUX Enterprise Server 9.0 (SLES 9) for IBM POWER

Install the RPM packages of the v7.0. 1 runtime component in this order:

a) vacpp.rte-7.0.1-1 (or a more recent version)b) xlsmp.msg.rte-1.5.1-1 (or a more recent version)c) xlsmp.rte-1.5.1-1 (or a more recent version)

The v8.0. runtime component is compatible with the following operating systems supported by SAP.

o Red Hat Enterprise Linux 4.0 Update 2 (RHEL4 U2) or higher for IBM POWER

o SUSE Linux Enterprise Server 9 Service Pack 2 (SLES 9 Service Package 2) for IBM POWER

Install the RPM packages of the v8.0. runtime component in this order:

a) xlsmp.msg.rte-1.6.0-0.ppc64.rpm (or a more recent version)

b) xlsmp.rte-1.6.0-0.ppc64.rpm (or a more recent version)c) vacpp.rte-8.0.0-0.ppc64.rpm (or a more recent version)

XI/ Mounting installation CDs and installation DVDs

All installation CDs and installation DVDs created without a Rock Ridge Extension must be included in the file system with the option -o map=off, so that file names appear with upper case spelling. You can use the following command accordingly:

mount -r -t iso9660 -o map=off /dev/cdrom /mnt/cdrom

XII/ Adding Linux application servers to existing SAP systems

As an SAP customer, you can add one or more Linux application servers to your existing SAP system (at least Release 4.0B). See also Notes 156548 and 531069. This measure alone does not involve any additional license costs.

The "Windows central instance with Linux application server" combination is also an option, as long as an SQL server is not used as a database. For questions regarding the link between the Windows and the Linux file systems, contact the hardware manufacturer of your SAP server.

To install the application server, you require both the Linux distribution (see above) and the kernel CD provided for Linux from the set of installation or upgrade CDs for your SAP release. You can obtain this kernel CD free of charge from your SAP sales partner.

We are aware of one (possible) problem regarding heterogeneous SAP systems: For non-Unicode systems, the sort sequence depends on the operating system used. There are no specific requirements defined by SAP in this regard. For this reason, different results are possible when outputting lists on different application servers.A similar problem may occur if you migrate the existing SAP system from another operating system to Linux. After the migration, the sort sequence may have changed.For all problems concerning the sort sequence, the Linux distributors offer the option of adjusting the Linux sort sequence to customer-specific requirements as part of the support. For more information, see Note 1069443.

XIII/ Using virtualization technologies

For more information about which SAP virtualization technologies are supported by Linux, see Note 1122387.

XIV/ Use of Raw Devices, "Journaling File system", and LVM

For information about using Raw Devices or a 'journaling file system', see Note 405827.For more information about the "Logical Volume Manager" (LVM), see Note 597415.

Header Data

Release Status: Released for CustomerReleased on: 25.03.2010 17:19:49Master Language: GermanPriority: Correction with high priorityCategory: Installation informationPrimary Component:BC-OP-LNX Linux

Affected Releases

SoftwareComponent

ReleaseFrom

ReleaseTo

ReleaseAnd

subsequentSAP_APPL 40 40B 40B SAP_APPL 45 45B 45B SAP_APPL 46C 46C 46C SAP_APPL 470 470 470 SAP_APPL 500 500 500 SAP_APPL 600 600 600 SAP_APPL 602 602 602 SAP_APPL 603 603 603 SAP_APPL 604 604 604 SAP_APPL 605 605 605 SAP_BASIS 46 46B 46D SAP_BASIS 60 610 640 SAP_BASIS 70 700 702 SAP_BASIS 71 710 720 SAP_ABA 50A 50A 50A SAP_ABA 620 620 620 SAP_ABA 640 640 640 SAP_ABA 700 700 700 SAP_ABA 710 710 710 SAP_ABA 711 711 711 SAP_ABA 701 701 701 SAP_ABA 702 702 702 SAP_ABA 720 720 720

Note 1244576 - 10.2.0.4 glibc and RAC

Summary

Symptom

Glibc released in RHEL4.6 and RHEL5.1 have a known bug by which the memory returned by calls to calloc() made while the memory is locked, for instance with


mlockall(), do not return zeroed memory.Various symptoms including segmentation faults.

Other terms

CALLOC ; CLEARED ; GLIBC ; ZEROED ; Linux; SUSE; RED HAT


Components responsible for the problem:

RHEL-4.6 and OEL-4.6: glibc-2.3.4-2.39, all architectures.RHEL-5.1 and OEL-5.1: glibc-2.5-18, all achitecturesSLES10-SP2: glibc-2.4-31.54 , all architectures

RHEL3 and earlier versions of glibc in RHEL4 and RHEL5 seriesare not affected by this problem.

Solution

For OEL4.6 and RHEL4.6 users, upgrade to glibc-2.3.4-2.41 or later.For OEL5.1 and RHEL5.1 users, upgrade to glibc-2.7-54 or later.For SLES10-SP2 users, Novell/SUSE is in the process of testing a new glibc, I will post an update to this note as soon as possible.

Note 1048303 - Red Hat Enterprise Linux 5.x: Installation and upgrade

Summary

Symptom

You want to use SAP server software on Red Hat Enterprise Linux 5.x

Other terms

Red Hat, Redhat, RH, Enterprise Linux, RHEL5, virtualization, XEN, x86_64, ppc64, ia64


You want to use SAP server software on Red Hat Enterprise Linux 5.x

SolutionEnvironment


This document deals with the installation and configuration of SAP server software on Red Hat Enterprise Linux 5 and upgrading an existing SAP system from Red Hat Enterprise Linux 2.1, 3 or 4 to Red Hat Enterprise Linux 5.x. In the following, "Red Hat Enterprise Linux" means version 5.x unless specified otherwise.

The installation or configuration of Red Hat Enterprise Linux as the base of a database server is not the primary purpose of this document although some notes listed here are specific to DBMS. If you want to install a database server, consult the operating system and database system documentation as well.

Certification of specific SAP products on specific versions of Red Hat Enterprise Linux notwithstanding, the following hardware platforms are certified for use of SAP software on Red Hat Enterprise Linux:

x86/ia32 (Intel compatible 32bit)

x86_64

ia64 (Intel Itanium 2)

PowerPC

IBM System z

Supportability prerequisites

In order for your SAP system to be fully supported on Red Hat Enterprise Linux, the following prerequisites must be fulfilled (this list is not exclusive, other notes may apply):

You need to use the Server variant of Red Hat Enterprise Linux.

You need to have valid support and update entitlements for Red Hat Enterprise Linux and any additional layered components (e.g. Virtualization, Clustering, Cluster Storage) on your machine. Please go to http://www.redhat.com/rhel/ for more information, or contact your local Red Hat sales representative.

Your machine must be able to retrieve additional software and updates, either directly, via an HTTP or RHN proxy or through an RHN satellite server. If you access additional software or updates by other, not officially supported avenues, some information in this note might not be applicable in your environment.

You need to use hardware that is certified for SAP use on Linux by your hardware vendor. See the respective notes on certified hardware which are listed in note 171356.

You are allowed to run any version or variant of the Linux kernel issued by Red Hat for your specific OS version as long as you use the same (sub-) architecture as tested in the SAP LinuxLab:

o i686 on Intel 32bit and compatible or AMD64 or Intel EM64T when used in 32bit mode

o x86_64 on AMD64 or Intel EM64T

o ppc64 on IBM PowerPC

o ia64 on Intel Itanium 2

o s390x on IBM System z

To get a fully supported Java stack, you need to purchase separate support for the certified JVM from the vendor or manufacturer. For x86_64 Systems you can get a Red Hat supported version of the required IBM 1.4.2 JDK by purchasing a subscription for "Red Hat Advanced Platform for SAP".

Installing Red Hat Enterprise Linux

Install the operating system as described in its documentation ("Red Hat Installation Guide", either the handbook or from installation media). Install the minimum operating system components mentioned below. Use English as the installation and system language. Note that some things that were configured during the installation in former versions of Red Hat Enterprise Linux are now configured during the first boot after the installation.

Additional notes:

Manually partitioning the disks is strongly recommended to reserve space for the application.

When asked about the desired timezone, choose "System clock uses UTC" in order to automatically switch between normal and daylight savings time.

Set a short, not fully qualified hostname. Mapping the short to the fully qualified hostname is described below under "Hostname".

When offered to customize the software selection, choose "Customize now". It is recommended to select the software groups listed in the following at a minimum for an SAP server machine. When customizing the list of optional packages for a software group, keep the packages selected by default and add packages eventually listed with the group. This is the list of categories/groups used in the installataion program:

o Servers/Printing Support

o Base System/Base

o Base System/X Window System

o Development/Legacy Software Development

o Development/Development Libraries (for Oracle databases)

o Development/Development Tools (for Oracle databases)

The following packages can't be chosen in these groups and have to be installed afterwards:

o compat-openldap

o libXp

o libunwind (only on ia64)

You can also install or reinstall a package or a package group at a later point (after registering your system in Red Hat Network) with the following commands, provided that your system can access Red Hat Network via the officially supported ways (directly or via RHN Proxy or RHN Satellite):

o For installing individual packages: yum install <package1> [<package2> [<package3> [...]]]

where <package*> are the names of the packages to be installed, e.g.:yum install libXp

o For installing package groups: yum groupinstall '<group1>' ['<group2>' ['<group3' [...]]]

where <group*> are the names of the groups you want to install.

The following yum groups correspond to the groups used in the installation program above:

o Printing Support

o Legacy Software Development

o X Window System

o Development Libraries (for Oracle databases)

o Development Tools (for Oracle databases)

If your system can't use the officially supported ways to access Red Hat, it often means it cannot determine the individual packages contained in a package group. In this case, you need to install the individual packages as described above.

To find out which packages fulfil a certain requirement or are part of a certain package group, please contact your operating system support.

When you first boot your system you will be presented with "firstboot", a post installation configuration tool:

If you leave the firewall enabled, you need to open up the ports for your SAP product either in firstboot if you already know them or by e.g. using the system-config-securitylevel tool at a later point. These ports are listed during the installation of the SAP software but can also be found in /etc/services after it is installed.

Red Hat Enterprise Linux uses SELinux technology for additional security which is enabled by default. Because several components of an SAP server system (like the installation tools or some underlying RDBMS) are not aware of SELinux, we recommend setting it to "Permissive" for the time being so that these components won't break. We don't recommend setting it to "Disabled" as this would require relabeling the whole filesystem if you want to enable it again at a later point for additional security when these components are made compatible or suitable procedures exist to make them function properly with SELinux. You can change SELinux settings by editing /etc/selinux/config for future boot processes. On a running system, you can switch between "Enforcing" and "Permissive" modes using the command "setenforce".

If you can access an NTP time server from the machine, we strongly recommend choosing "Enable Network Time Protocol" in the "Date and Time" dialog to keep all SAP applications servers' time and date synchronized.

You should register the system in the Red Hat Network to retrieve update packages for your machine. In all cases it is recommended that you update all program packages (including kernel and glibc) to the latest version available in the Red Hat Network.

Hostname

Ensure that the system hostname is set to the short name as described above, i.e. both commands "hostname" and "hostname -s" must return the hostname without domain, "hostname -f" must return the fully qualified hostname and domain. To do that, check

that HOSTNAME is set to the short name without domain in /etc/sysconfig/network and set up /etc/hosts so that it is configured like this (besides any additional configured hosts):127.0.0.1 localhost.localdomain localhost192.168.0.1 server.example.com serverIt is important that the fully qualified domain name is in the second column, followed by any alias names and that the hostname of the machine is not associated with the IP address 127.0.0.1. Afterwards run 'hostname <shorthostname>' to set the hostname without rebooting.

Linux kernel

You may use any Linux kernel as long as the conditions described above in "Supportability prerequisites" are met.

Updating the Glibc package

You may use any glibc package for your OS version provided by Red Hat. After updating the glibc package you need to (re-) install the saplocales package:rpm -e saplocalesrpm -ivh <saplocales.rpm>See note 171356 for details on the saplocales package.

Linux kernel parameters

Some Linux kernel parameters have to be adjusted to meet the requirements of SAP software. To do this append the following lines to /etc/sysctl.conf (or change them accordingly -- these are minimum values, higher values are okay as well):# SAP settingskernel.msgmni=1024kernel.sem=1250 256000 100 1024vm.max_map_count=1000000kernel.shmmax=23136829430kernel.shmall=5242880 (adapt according to SAP note 941735)Activate these settings with the command "sysctl -p".

Process resource limits

Some components (e.g. the SAP J2EE engine, Oracle RDBMS software, ...) need to keep a large number of file handles opened simultaneously. You need to increase the limit of files one process can open at a time by extending /etc/security/limits.conf with lines similar to these:@sapsys hard nofile 32800@sapsys soft nofile 32800@dba hard nofile 32800@dba soft nofile 32800These lines grant the users in the sapsys group (J2EE engine) and the dba group (Oracle)

to open up to 32800 files simultaneously, you need to logout and login again for the setting to take effect. If needed, adjust these lines to match your setup. Please refer to the comments in said file for information about its format.

Minimum patchlevels

Some installation media contain old patchlevels of the SAP software. For proper functioning of your SAP system, ensure that you have installed at minimum the patchlevels listed here:

SAP kernel 4.6D_EXT: patchlevel >= 1811

SAP kernel 6.40: patchlevel >= 12

Memory Management

The Intel-compatible 32bit Linux kernels contained in RHEL 5 allow to allocate more than 2GB of memory in a single chunk. You can adjust your SAP profile parameters accordingly to use more SAP buffers and extended memory at the expense of heap size. For more information refer to SAP note 386605.

Patching SAPINST

In some cases SAPINST will fail during start or terminate abnormally and needs to be patched. Please refer to and proceed according to note 722890 for information about where to download SAPINST patches and how to apply them.

Threading on Red Hat Enterprise Linux 5.x

Red Hat Enterprise Linux 5.x uses the Native Posix Threading Library, a POSIX-compatible threading implementation, for threading. Unlike former versions of RHEL, using LinuxThreads for older applications by way of setting the environment variable LD_ASSUME_KERNEL to 2.4.1 doesn't work anymore and will probably prevent most programs from being run at all if it is set.

Red Hat supported IBM 1.4.2 JDK for x86_64

To install the Red Hat supported IBM 1.4.2 JDK, please make sure that the system is subscribed to the "RHEL AP for SAP" channel on RHN or your local RHN Satellite. You can then install the required IBM 1.4.2 JDK packages via the following commands:yum install java-1.4.2-ibm-1.4.2.13.sap-1jpp.3.el5_3yum install java-1.4.2-ibm-devel-1.4.2.13.sap-1jpp.3.el5_3To avoid that the IBM 1.4.2 JDK packages get overwritten during a update please add the following line to /etc/yum.conf:exclude=java-1.4.2-ibm*

Additional notes for installing SAP systems

You may get a warning from the Prerequisite Checker that Red Hat Enterprise Linux 5.x is not supported. Ignore this warning.

For information about the current supported SUN JDK 1.4.2 release on Intel-compatible 32bit and ia64 platforms and known issues with older releases of the SUN JDK please see note 716604.

When installing an SAP system based on kernel 640, you need to update the SAP kernel to a current patchlevel, then continue with the installation of the DB instance, see note #19466 for details. In the DB installation, when asked whether you want to extract the SAP kernel SAPEXE and SAPEXEDB archives, uncheck these options so that the updated kernel files don't get overwritten with old versions.

When using SAP software in an LDAP environment on RHEL 5/x86_64, you need to install a symbolic link for two libraries because the binaries used to access LDAP where built against versions of these libraries with a non-standard SONAME:

ln -s libldap-2.2.so.7 /usr/lib64/libldap.so.199

ln -s liblber-2.2.so.7 /usr/lib64/liblber.so.199

For this, you need to have the compat-openldap package installed.

When using R3SETUP to install older product releases, you might encounter an error looking like this:

[...] error while loading shared libraries: libstdc++-libc6.1-1.so.2: cannot open shared object file: No such file or directory

In this case, run the following command as the root user to create a symlink to the newer version of the library:

ln -s libstdc++-libc6.2-2.so.3 /usr/lib/libstdc++-libc6.1-1. so.2Backup

When using BRBACKUP, don't use the cpio tool as a backend because it can't restore archives larger than 4GB. See note 20577 for details.

Additional notes for installation with IBM DB2 RDBMS

On some Linux kernels shipped during the RHEL 5.1 and 5.2 timeframe the ABAP import may stop which would need restarting of the DB2 LUW database.

The preferred way to fix this is upgrading the Linux kernel to version 2.6.18-128.el5 or later which is contained in RHEL 5.3. If this is not feasible, you can either disable direct I/O for the database or use the ext2 file system instead of ext3 for the database files.

Additional notes for installation with Oracle RDBMS

The following examples are for the x86_64 platform. You might need to adjust paths according to your setup.

When running the runInstaller/RUNINSTALLER commands, you may get a warning like the following:

Checking installer requirements...

Checking operating system version: must be redhat-3, SuSE-9, redhat-4, UnitedLinux-1.0, asianux-1 or asianux-2

Failed <<<<

In this case, create or change /oracle/stage/102_64/database/install/oraparam.ini so that it contains these lines:

[Certified Versions]

Linux=redhat-3,SuSE-9,redhat-4,UnitedLinux-1. 0,asianux-1,asianux-2, redhat-5

When installing Oracle on Itanium hardware, apply the necessary patches as described in note #986578.

Header Data

Release Status: Released for CustomerReleased on: 06.04.2010 10:50:13Master Language: EnglishPriority: Recommendations/additional infoCategory: Installation information

Primary Component:BC-OP-LNX-RH Red Hat Linux

Note 386605 - SAP Memory Management for Linux (32-bit)

Summary

Symptom

You want to make more efficient use of the existing main memory for SAP software. As of Linux kernel 2.4, there is a new option available for this purpose.

Other terms

Memory Management, Linux, Linux on zSeries, TEXTENV_INVALID, Signal 7, Signal 11, /dev/shm, TMPFS, x86_64


On 32-bit Linux, an operating system process can address between 2 GB and 3 GB of memory (approximately), depending on the Linux kernel in use. An unrestricted-use address space (User Space) of 3 GB applies to the Linux kernels tested by SAP (for more information, see Note 171356). Although the address space has a total of 4 GB for 32-bit software, the Linux kernel requires 1 GB for its own consumption (kernel space).There are theoretical address-space restrictions for 64-bit applications (for the moment).

1. Different memory areas are allocated for the SAP system, some of which are shared memory areas, and some process local areas. In the shared memory, the ABAP program buffer (abap/buffersize), the SAP generic key buffer (zcsa/table_buffer_area) and the internal table buffer (rtbb/buffer_length) require a relatively large amount of space. In total, more than 1 GB of memory may be required (not including user-specific areas) for efficient system performance. SAP transaction ST02 provides a good overview of the allocated shared memory areas (for more information, see Note 103747). This means that between 1 GB and 2 GB of address space per process is left for the remaining memory areas, depending on the 32-bit Linux kernel that you use.2. In addition, a process can request further process-local memory (heap) and user-contexts (refer to the points below) until the available address space is completely exhausted, or it reaches an SAP heap quota (abap/heap_area_dia, abap/heap_area_nondia, abap/heap_area_total). Typically, at least 800 MB of memory can be addressed for heap in the 32-bit address space - depending on the SAP Buffer and SAP Extended Memory settings.3. When you execute a dialog step, each SAP process assigned to process a user request allocates memory. You must cancel part of this memory for the following dialog step. You can only completely release the memory allocated for the user after the user has logged off. This memory allocated per user session is also referred to as a user context. User contexts describe the user profile, ABAP


programs executed, and the variables allocated by those ABAP programs. ABAP programs dynamically set up internal tables that can contain thousands of records and occupy many MB of memory. Because different processes may process the individual dialog steps of a user, you must be able to pass a user context as efficiently as possible, which is why the largest part is stored in the shared memory. The SAP workprocess that executes the user's next dialog process only needs to receive a pointer to the shared memory, so that it can access the user context. The part of the user context implemented in the shared memory is called extended memory.

a) With Linux kernel 2.2, the SAP System must simultaneously map the user contexts of all active users in the address space of the work processes. This corresponds to the standard UNIX implementation of the extended memory (EM). The total of all currently active user contexts is therefore limited by the address-space restrictions of the Intel 32-bit platform. As a result, approximately 1.2 GB (maximum) is specifically available for all user contexts together.This means that there is actually a maximum of (approximately) 1.2 GB available for all user contexts on this platform. You can activate this implementation variant of SAP Memory Management using the instance profile parameter es/implementation=std.b) As of Linux kernel 2.4, you can activate an alternative implementation for 32-bit systems, which provides approximately 500 MB of extended memory per user session (you can configure this implementation using the parameter em/address_space_MB). The program always includes the required user contexts in this interval. In total, the user contexts now share an extended memory that is limited by the configured swap space and the main memory (SAP parameters em/initial_size_MB, em/max_size_MB).You can activate this implementation variable of SAP Memory Management using the instance profile parameter es/implementation=map.

From experience, we know that a maximum of approximately 2 GB of address space is available for SAP shared memory segments (SAP buffer and extended memory) in the 2.4 and 2.6 Linux kernels. Since this is usually limited to 500 MB per user session, about 1.5 GB generally remains available for the SAP buffer on 32-bit systems.Unfortunately, the address space used for SAP shared memory segments varies from Linux version to Linux version. Therefore, the determining factors of the different variants for the SAP memory configuration are described in more detail in this note (see below).

Solution

If, for example, problems occur when you increase the user context, the ABAP program terminates with an error and the business functions cannot be used. The ABAP short dump contains the information required to analyze the problem. You must check whether:

o ABAP can be used more effectively.

o the operating system parameters are optimally set.

o the SAP profile parameters can be changed so that more memory can be used for the user contexts.

For efficient operation, it is very important that sufficient extended memory is available. This note explains how to use the new function to do this. To provide more extended memory for SAP users, SAP offers a more flexible and very administration-friendly extended memory administration based on Linux kernel 2.4. The following information applies to:

SAP kernel 4.5B, as of patch level 731

SAP kernel 4.6D, as of patch level 945 (manually configurable as of patch level 488)

SAP kernel 6.x

SAP kernel 7.x.

Note:These instructions apply to all 32-bit and 64-bit Linux systems. However, the available address space in 64-bit systems is sufficient, which is why it is not necessary to map the extended memory. Nevertheless, the administration-friendly parameter management described in the following can also benefit users of 64-bit systems.

The SAP workprocess can now display each required user context individually in the address space (this is based on the TMP file system (TMPFS or /dev/SHM) that was imported with Linux kernel 2.4).This means that a single user context (depending on the SAP buffer configuration) is restricted to approximately 1.5 GB (around 500 MB SAP EM, with the remaining address space available as a heap) on 32-bit Linux systems. However, the total of the user contexts in the system can become significantly bigger (essentially only limited by RAM + swap). This is exactly the same as the memory management in Windows.In terms of the size of the individual user contexts, 64-bit Linux systems are usually only subject to the restrictions set by the RAM and swap.

If your system meets the following prerequisites, you can use the map-EM administration:

1. Linux kernel 2.4 with the TMPFS mounted under /dev/shm (see below).2. SAP kernel 4.5B, 4.6D, 6.x or 7.x as specified above3. Setting the profile parameter in the (instance) profile of the SAP application server activates the behavior described above:

es/implementation = map

As of SAP kernel 6.20 to SAP kernel 7.10, this corresponds to the default setting.Alternatively, you can activate the 'std' memory management by explicitly setting es/implementation=std, and this corresponds to the normal behavior on a Unix system. However, you should only consider doing this on systems that use a 64-bit SAP kernel (for more information, see Note 941735).

Zero Administration Memory Management on Linux (ZAMM)

As of patch level 731 for SAP kernel 4.5B, 945 for SAP kernel 4.6D and all patch levels for SAP kernel 6.20 and higher, setting "es/implementation=map" also causes the activation of a significantly simplified method for configuring memory management. The relevant profile parameters are automatically preset in the same way as the implementation on Windows. The memory configuration of the instance can only occur using the PHYS_MEMSIZE parameter.In this context, we strongly recommend that you delete the parameters listed below from the SAP System's profile, so that the SAP kernel default values are not overridden. Otherwise, the automatic mechanism will not work or will only partially work (for some of the parameters).Exceptions are permitted in well-founded cases such as recommendations by the SAP Support or during SAP Service sessions.

The following profile parameters and parameter values are affected if ZAMM is activated:Some parameters are set dynamically depending on PHYS_MEMSIZE, and we specify the corresponding value ranges below. The values described are valid as of kernel patch level 116 (6.40), 48 (7.00) and higher.

a) rdisp/ROLL_SHM32 bit: between 1024 ( 8 MB) and 16384 ( 128 MB)64 bit: between 32768 (256 MB) and 131072 (1024 MB)b) rdisp/ROLL_MAXFS32 bit: 32768 (256 MB)64 bit: 131072 (1024 MB)c) rdisp/PG_SHM32 bit: between 1024 ( 8 MB) and 8192 ( 64 MB)64 bit: between 32768 (256 MB) and 65536 ( 512 MB)d) rdisp/PG_MAXFS32 bit: 32768 (256 MB)64 bit: 131072 (1024 MB)e) ztta/roll_area32 bit: 3500000 (3.5 MB)64 bit: 6500000 (6.5 MB)

f) ztta/roll_first32 / 64 bit: 1g) ztta/roll_extension (Maximum size of a user context in the SAP EM)32 / 64 bit: 4000000000 (3800 MB -> em/address_space_MB limits the size of a user context in the EM)h) em/max_size_MB (maximum size of EM)32 / 64 bit: Percentage share of the instance in TMPFSi) em/initial_size_MB (initial size of the EM; if there is a higher demand for EM, em/initial_size_MB is automatically increased by 50% of the value, provided that em/max_size_MB has not yet been reached)32 / 64 bit: Absolute value of PHYS_MEMSIZE (for 32-bit limited to 2040 MB)j) em/address_space_MB (Address window in the EM workprocess, quantity of EM that each single user context may fully occupy provided ztta/roll_extension has not yet been reached; this interval is reserved from the start of the instance)32 bit: 512 (MB)64 bit: 4096 (MB)k) em/blocksize_KB (size of the blocks of EM chains)32 bit: at least 1024 (1 MB)64 bit: 4096 (4 MB)

ZAMM uses the physical memory (refer to the parameter name PHYS_MEMSIZE), that is the Linux server's RAM, as a basis for calculating the memory parameters mentioned above. If PHYS_MEMSIZE has a value other than 100%, the SAP kernel always calculates the parameters in percent relating to the total RAM of the host.The majority of the parameters listed above are used in this case on feasible and, more or less, dynamic default values. The following two parameters depend directly on PHYS_MEMSIZE:

em/max_size_MB: is set to the percentage value of TMPFS, which is determined directly from PHYS_MEMSIZE or which is calculated from PHYS_MEMSIZE and RAM size.

em/initial_size_MB: is set directly to the value of PHYS_MEMSIZE or to the share (in MB) of the RAM size defined by the percentage values (on the 32-bit platform, this may deviate to a maximum of 2040 MB).

NOTE: Note that the values of parameters em/max_size_MB and em/initial_size_MB (for example, with the manual setting) must not be higher than the configured TMPFS. Otherwise, the memory space on /dev/shm may run out, which usually results in a system downtime and process terminations (with Signal 7 or Signal 11).

Examples for PHYS_MEMSIZE Setting the

PHYS_MEMSIZE = 50%

the instance is configured to use 50% of the available resources (this relates primarily to RAM and TMPFS), which can be suitable if you use two SAP instances of the same size on the same server.If you have several SAP instances on a server, ensure that each instance is assigned only a fraction of the overall resources using PHYS_MEMSIZE - or em/max_size_MB. Otherwise there is a risk that TMPFS will overflow.Comment: Under certain circumstances, a percentage value for PHYS_MEMSIZE may result in error messages during check routines for the system parameters within the SAP system (for example, transaction RZ10): E:PHYS_MEMSIZE not a numeric valueYou can ignore these error messages.

Setting the

PHYS_MEMSIZE =1024

the system calculates the percentage portion of the resources to be used. For a server with 4 GB main memory a value of 25% (1/4) is calculated, for example; internally, further calculations are made using PHYS_MEMSIZE=25%.

If PHYS_MEMSIZE is not set, the entire RAM is available to the instance (corresponding to PHYS_MEMSIZE = 100%).Note, however, that a certain inconsistency is apparent when querying the active system parameters (for example, transaction RZ10). If PHYS_MEMSIZE does not appear in the SAP system profiles, the default value (64 MB) is displayed as the active value. The program actually calculates the above-mentioned system parameters based on PHYS_MEMSIZE=100%.

Note on the configuration of the TMPFS

You can activate the TMPFS at operating system level as follows, depending on your Linux distribution:

1. SUSE SLES 8/9:

Modify the SHMFS_SIZE parameter in /etc/sysconfig/kernel (example: SHMFS_SIZE="6442450944" or "6G" corresponds to 6 GB TMPFS). The remarks below apply to the TMPFS dimensioning.

2. Red Hat Enterprise Linux 2.1/3/4 and SUSE SLES 10:

Add the following line to the /etc/fstab file:

tmpfs /dev/shm tmpfs size=<size> 0 0

When specifying the size <size> , you must take into account both the available RAM + Swap and the actual memory requirement of your SAP system. If, for example, your machine has 4 GB RAM and 8 GB Swap, you can limit the TMPFS to 6 GB using

size=6G or size=6144M

Take into account that

o TMPFS must be smaller than the total of RAM and swap

o TMPFS must have a size of at least 2 GB (32 bit) or 8 GB (64 bit)

o As a recommendation, a size of 75% of RAM + swap can be assumed for the TMPFS configuration.

A change in the size of the TMPFS in the specified locations only becomes effective after the next system reboot. There are options for avoiding a reboot until further notice:

a) In the case of changes in the /etc/fstab file, you can activate the modifications with the following command:

mount -o remount /dev/shmb) In the case of changes in the /etc/sysconfig/kernel file, you can modify the size <size> of TMPFS temporarily (until the next reboot) as follows:

mount -o remount,size=<size> -t shm none /dev/shm

NOTE: Before you execute the command, ensure that /dev/shm is not currently being used by SAP software.

After the next reboot, also ensure that the TMPFS mounted under /dev/SHM has sufficient available free memory: df -h /dev/shm

Additional information about Memory Management1. When the SAP instance still finds relevant files in /dev/shm when you start it, it will not launch. With newer versions of cleanipc (patch level 1 or higher in 4.5B and 4.6D), these files are also cleaned up.2. With systems that have a lot of main memory, discrepancies can occur between the automatic setting of the profile parameters described above and the internal consistency check. This problem is corrected in 4.5B as of patch level 773, in 4.6D as of patch level 1040 and in 6.20. Until then, you can set the problematic parameters manually as a workaround, for example, em/blocksize_KB = 8192.3. Currently, systems with significantly more than 32 GB physical main memory are not fully supported by the 32-bit Linux kernel. At the moment, these systems

should be run with approximately 32 GB of main memory. This restriction does not apply to 64-bit Linux systems.4. With SUSE Linux Enterprise Server 7 (SLES7), the TMPFS may be mounted twice during the boot sequence. This can cause the wrong sizes of the TMPFS and thereby cause wrong prerequisites for SAP Memory Management. A solution to this problem is available in the SUSE Support Database port (http://sdb.suse.de) under the key word "tmpfs" or "shm".5. Linux for zSeries is a 64-bit implementation. In addition, refer to Note 892818.

Available address space for SAP Shared Memory Segments

The address space allocation of a process differs, depending on the Linux distribution and version. This differing behavior is particularly significant in a 32-bit environment because only 4 GB (32 bits) of a process can be "seen", regardless of the main memory built into the machine. In a 64-bit environment, this problem becomes less important due to the much larger address space - instead, the question of performance comes to the fore again.With SAP Extended Memory or SAP buffers, you must take into account that this concerns shared memory (SHM) on operating systems, which is why the complete user space for this storage type is not available in some circumstances.Therefore, when storage parameters are configured from SAP to Linux, the attributes of the individual Linux versions described in the following can be useful:

SUSE Linux Enterprise Server 8 and 9 (x86 - 32 bit)/Red Hat Enterprise Linux 2.1 (x86 - 32 bit)

Operating system libraries are displayed on address 0x4000 0000 (1 GB) in the 32-bit (4 GB in size) address space. As a result, address space (user space) which can be used for applications and is 3 GB in size is distributed. Accordingly, the area that can be used for SAP SHM is approximately 2 GB in size (address approximately from 1 GB (0x4000 0000) to approximately 3 GB (0xC000 0000)).In addition, the remaining address space (for example, below address of 1 GB) can still be used for heap memory, if the SAP heap quotas (abap/heap_area_*) are set sufficiently high.

Red Hat Enterprise Linux 3 and 4 / SUSE Linux Enterprise Server 10 (x86 - 32 bit)

Operating system libraries are included in the upper edge of the user space, so that almost the entire user space (approximately 2.8 GB) is available for SAP shared memory segments.As a result, more memory can be configured for SAP buffers or SAP extended memory than on other operating systems, for example. However, it does not provide any more address space, so only a small amount of heap memory can be allocated after such an increase.

SUSE Linux Enterprise Server 9 (x86_64 - 64 bit) with 32 bit SAP kernel (46D_EXT)

The 32-bit SAP kernel can "see" only 4 GB of address space here, despite the 64-bit operating system. However, these 4 GB are completely usable for the SAP processes, since the Linux kernel space can be included in the 64-bit address space by the operating system.On SLES9 (x86_64) with a 32-bit SAP kernel provides approximately 2.6 GB for SAP shared memory, since operating system libraries fragment the address space from address 0x5555 5000 (approximately 1.365 GB).However, the remaining 32-bit address space can be used as heap memory (approximately 1.3 GB), juast as in the 32-bit version of SLES9.

Red Hat Enterprise Linux 4 (x86_64 - 64 bit) with a 32-bit SAP kernel (46D_EXT)

Here, the 32-bit SAP kernel can only see 4 GB of the 64-bit address space, just as is the case for SLES9 on the x86_64 platform.Since the operating system libraries are included at the lower edge of the 32-bit address space, approximately 3.8 GB are available for SAP shared memory.As is the case for RHEL 3 on 32 bit, there is relatively less memory space left available for heap memory, depending on the settings of the SAP extended memory and the SAP buffer.

64-bit distributions in general

Currently, only theoretical address space restrictions apply for all integrated 64-bit platforms (that is, systems that use a 64-bit hardware, a 64-bit operating system, and a 64-bit SAP kernel).

Header Data

Release Status: Released for CustomerReleased on: 21.05.2007 12:00:18Master Language: GermanPriority: Recommendations/additional infoCategory: ConsultingPrimary Component: BC-OP-LNX LinuxSecondary Components:BC-CST-MM Memory Management

Affected Releases

SoftwareComponent

ReleaseFrom

ReleaseTo

ReleaseAnd

subsequentSAP_APPL 45 45B 45B SAP_APPL 46C 46C 46C SAP_APPL 470 470 470 SAP_APPL 500 500 500 SAP_APPL 600 600 600 SAP_APPL 602 602 602 SAP_APPL 603 603 603 SAP_APPL 604 604 604 SAP_BASIS 46 46D 46D SAP_BASIS 60 620 640 SAP_BASIS 70 700 701 SAP_BASIS 71 710 711 Note 722890 - SAPinst or process started by SAPinst terminates abnormally

Summary

Symptom

SAPinst or a process started by SAPinst terminates abnormally

Other terms

SAPinst, UNIX, 621, 622, 641


Details:

Case 1:SAPinst terminates abnormally:Occurs only, if you use SAPinst version 621. If the problem occurs, SAPinst is normally terminated using the signal SIGABRT and a core file is written. Often the last output of SAPinst on the command line is "aborted". There is no error message in the log file.

Case 2:A process started by SAPinst terminates abnormally:This problem can occur with SAPinst version 621, 622 and 641.The process is usually terminated by the signal SIGSEGV and a core file is written. This happens only if the started process is running under another group than that group, under which SAPinst runs. Examples ofprocesses that run under a different group are R3load or SDM.This problem normally occurs only, if the group under which the process is running (for example sapsys or dba) has a very large ID.The error message in the log file shows that the child process has terminated abnormally. The program to be started by the process was not started. Therefore the program was not able to take any action, such as creating its own log files.


Solution1. Find out the version of SAPinst using the command sapinst -v.This note does not apply to SAPinst version 1.0.

Procedure for SAPinst version 621:1. Download the required patch from SAP Service Marketplace (SMP) athttp://service.sap.com/swdc--> Download --> Support Packages and Patches --> Entry by ApplicationGroup --> SAP NetWeaver --> SAP Netweaver components (< SAP NW 04) -->SAP WEB AS --> SAP WEB AS 6.20 --> SAP WEB AS ABAP -->SAP KERNEL 6.20 <32 or 64>-BIT --> < OS > --> Database independent--> SAPINST6201--> SAPPROD6201Note that there exists no special unicode version of SAPinst.The non-unicode version is used for the installation of unicode andnon-unicode systems.2. Back up the installation directory.3. Unpack the SAP archives you have downloaded from the SAPServiceMarketplace into the installation directory and start sapinstfrom there.

Procedure for SAPinst version 622:1. Download the required patch from SAP Service Marketplace (SMP) athttp://service.sap.com/swdc--> Download --> Support Packages and Patches --> Entry by ApplicationGroup --> SAP NetWeaver --> SAP Netweaver components (< SAP NW 04) -->SAP WEB AS --> SAP WEB AS 6.20 --> SAP WEB AS ABAP -->Kernel 6.20 <32 or 64>-BIT --> < OS > --> Database independent--> SAPINST6202Note that there exists no special unicode version of SAPinst.The non-unicode version is used for the installation of unicode andnon-unicode systems.2. Back up the installation directory.3. Extract the downloaded archive to a temporary directory.4. Change to the installation directory.5. Enter the command:<path to sapinst in temporary directory>/sapinst -extract6. Start./sapinstIf you have downloaded the patch before starting the installation youhave to call./sapinst <path to the original sapinst on the CD>/control.xmlinstead.

Procedure for SAPinst version 641:1. Download the required patch from SAP Service Marketplace (SMP) athttp://service.sap.com/swdc--> Download --> Support Packages and Patches --> Entry by Application Group --> Additional Components --> SAP Kernel --> SAP Kernel <32 or 64>-BIT -->

SAP KERNEL 640 <32 or 64>-BIT --> < OS > --> #Database independent --> SAPINST6401Note that there exists no special unicode version of SAPinst.The non-unicode version is used for the installation of unicode andnon-unicode systems.2. Back up the installation directory if you have already started theinstallation. In this case the installation directory contains thefiles control.xml, keydb.xml, sapinst.log etc..If you have not yet started the installation create a new installationdirectory.3. Extract the downloaded archive to a temporary directory.4. Change to the installation directory.5. Enter the command:<path to sapinst in temporary directory>/sapinst -extract6. From within the installation directory start./sapinstIf you have downloaded the patch before starting the installation youhave to call./sapinst <path to the original sapinst on the CD>/product.cataloginstead.

Header Data

Release Status: Released for CustomerReleased on: 12.05.2006 11:21:21Master Language: EnglishPriority: Correction with medium priorityCategory: Program errorPrimary Component:BC-INS-UNX Installation UnixNote 933778 - SAP ERP 2004 SR1 Installation on RedFlag Linux

Summary

Symptom

************************************************************************* SAP ERP04 Support Release Installation on RedFlag Linux************************************************************************

Other terms

ERP04 SR1, RedFlag



Installation issues not covered by standard installation guide

Solution

DO NOT CHANGE OR ADD INFORMATION TO THIS NOTE ! If you do want to c ontribute something, please issue a mail to: Dongxu Ma <[email protected]>

__ALWAYS__ take the latest official installation guide from: http://service.sap.com/instguides

Contents

Sections of this note are: 1. General 2. OS Dependencies 3. Pre-Installation 4. Installation 5. Post-Installation

This note covers the following database types: 1. MySQL MaxDB ADA 2. IBM DB2 Universal Database DB2 3. Oracle ORA

Changelog on this note:

Date Section Description

-----------------------------------------------------------------------

=======================================================================

1. General

Guide http://service.sap.com/instguidesSAP Patches http://service.sap.com/patches

=======================================================================

2. OS Dependencies

o Certified OS release:

* RedFlag Advance Server 4.1 I386 kernel-smp-2.4.21-9.30AX glibc-2.3.2-95.20.1AX

* RedFlag DC Server 5.0 (Trinity) x86_64 kernel-smp-2.6.9-11.19AX glibc-2.3.4-2.9.1AX

* RedFlag DC Server 5.0 on Power ppc64 kernel-smp-2.6.9-11.19AX glibc-2.3.4-2.9.1AX

o Check Note 855498 for general hardware and software requirements.

o Check Note 146289 for SAP kernel parameter settings.

o Check Note 722273 Section "NPTL" on thread library concern.

o Check Note 386605 for OS memory management.

=======================================================================

3. Pre-Installation

o Oracle:

Check Note 722273 regarding Oracle 9i installation; Also check Note 539921 and 306408 for more information on Oracle Patch Set.

For 10g installation and upgrade: check Notes 945315 871735 and 871096. Install IBM xlc runtime library.

o DB2 UDB:

Use 'db2_install' instead of 'db2setup' for installation; Also check Note 68854.

=======================================================================

4. Installation

o SAPinst cannot find a program named XTCC during installation:

Stop sapinst (CAUTION: __NOT__ reset), under the same work director y you invoked sapinst, restart sapinst with option "-extract", then res tart it again to continue with your installation.

o Oracle 9i Patch Set on SAP CD:

To apply the patch set on RedFlag, please invoke runInstaller with option "-ignoreSysPrereqs".

o SAPinst cannot connect to running Oracle Database:

sapinst failed at database load phase with tricky error in sapinst.logRunning "R3trans -d" as <sid>adm failed to connect to database. The Oracle 9i client package shipped with SAP ERP04 SR1 cannot work correctly. For a standalone installation type please backup all direct ories under /oracle/client/<REL> and symbol-link specific ones from $ORACLE_HOME/<REL>/lib; For a distributed system, please copy or mount all stuff under /oracle/client/<REL> from your database instance server , reserve the same file permissions. Also refer to Note 180430 for applying a new oracle client package later on.

=======================================================================

5. Post-Installation

- Linux on Power: perfrom a upgrade to SAP kernel 640 patch level >= 87.

- For 64bit OS: add 'es/implementation=std' to profile. Refer to Note 386605.

- MaxDB on ppc64: refer to Note 851105.

Note 945315 - SAP installation on Linux on POWER/Oracle 10.2

Summary

Symptom

You want to install SAP products with Oracle 10.2 on Linux on POWER. This note is an addition to the installation documentation and describes known errors that may occur during the installation.


Other terms

Linux on POWER, LoP, Oracle, installation

Reason and Prerequisites1. Prerequisites for installing Oracle 10.2 on Linux on POWER2. Required patch sets and patches for Oracle 10.23. When you install Oracle 10.2 on Linux on POWER, the following error occurs:Error in invoking target 'client_sharedlib' of makefile '/oracle/<SID>/102_64/network/lib/ins_net_client.mk'.The log file /oracle/oraInventory/logs/installActions<timestamp>.log contains the error message:INFO: ./../../../powerpc-suse-linux/bin/ld: cannot find -lxl4. The following error occurs when you install patch 4460775 or 4864648:OUI-67020 [...] Platform not compatible5. Installation on RedHat Enterprise Server 4 (RHEL4), Quarterly Update 2 or later:The following error occurs in the Oracle Universal Installer when you install the Oracle software under RHEL4 QU2 (or later):Error in invoking target 'relink' of makefile '/oracle/<SID>/102_64/precomp/lib/ins_precomp.mk'.6. Installation on SuSe Linux Enterprise Server 9 (SLES9):The following error is displayed in the Oracle alert log during the installation or operation on SLES9:ORA-27061 Waiting for async I/O failed7. You want to use the "reiserfs" file system.8. When you install Oracle patch set 10.2.0.4 on SLES11 or RHEL5, the following errors may occur: "Error in invoking target 'install' of makefile '/oracle/<SID>/102_64/network/lib/ins_net_server.mk'" and/or "Error in invoking target 'racg_install' of makefile '/oracle/<SID>/102_64/racg/lib/ins_has.mk'". The installation log under /oracle/oraInventory contains the error message "undefined reference to `snprintf@GLIBC_2.4'".

Solution

For point 1):The Oracle software requires the IBM XL C/C++ runtime environment. Note 1092448 describes how to install the runtime environment.Also see Note 975196.

For point 2):The required patches are described in SAP Note 871096. The patches listed in this note MUST be installed, in particular, patch set 10.2.0.4.

For point 3):The error message indicates that the xlc runtime environment was not found. Install the runtime environment as described under 1).

For point 4):Ensure that you only download the generic patches 4460775 and 4864648 from the SAP Service Marketplace and not from the Oracle Metalink.

For point 5):The error is corrected with Oracle patch 4767801. The patch is attached to this note. Install the patch and continue the installation of the Oracle software with "Retry". The error will becorrected with Red Hat Enterprise Linux 5 (RHEL5).

For point 6):This is an error in the "libaio" package for SLES9. The error is corrected in SLES9, Support Package 3 or higher. Update your operating system to SLES9, Support Package 3 or install Kernel Version 2.6.5-7.244 (or higher).

For point 7):Read Note 914177 if you use the "reiserfs" file system.

For point 8):Ignore the error messages mentioned above when you install patch set 10.2.0.4 and choose "Continue" to continue with the installation. After you install the patch set, use the workaround described in Note 1404424.

Header Data

Release Status: Released for CustomerReleased on: 18.11.2009 11:26:15Master Language: GermanPriority: Recommendations/additional infoCategory: Installation informationPrimary Component: BC-OP-PLNX Linux on IBM PowerPC HardwareSecondary Components:BC-DB-ORA-INS Installation SAP System with Oracle

sap note

Documents

sap extended memory

extended memory zttaroll

sap extended memory

sap systems

virtual memory

memory close

memory display

extended memory entry