SAP Note

(1)

SAP Note: 941735. Linux kernels SAP Note: 941735. Linux kernels Summary

Summary Symptom Symptom

Recommendation for parameterization of 64-bit Linux systems. Recommendation for parameterization of 64-bit Linux systems. Other terms

Other terms

Linux memory management, es/implementation, STD, MAP, TMPFS,

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

em/initial_size_MB

Reason and Prerequisites Reason and Prerequisites For SAP on Linux,

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

switch between the two systems using the SAP instance profile parameter es/implementation:

es/implementation: •

• MAP implementation (es/implementation=map)MAP implementation (es/implementation=map)

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

386605.

As of SAP kernel 6.20,

As of SAP kernel 6.20, an SAP system on Linux uses the MAP an SAP system on Linux uses the MAP implementation byimplementation by default, in which only the currently active

default, in which only the currently active user context is displayed in the address spaceuser context is displayed in the address space of the work process.

of the work process. •

• STD implementation (es/implementation=std)STD implementation (es/implementation=std) With this variant, the memory management of an S

With this variant, the memory management of an SAP system on Linux is theAP system on Linux is the same as on standard UNIX systems. This means that all

same as on standard UNIX systems. This means that all user contexts are displayed in theuser contexts are displayed in the address space at the same time,

address space at the same time, which means that this variant is only available for 6which means that this variant is only available for 64 bit4 bit systems.

systems.

While the MAP implementation should be used

While the MAP implementation should be used exclusively on 32-bit Linux in moreexclusively on 32-bit Linux in more cases, both variants can be

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

any 32-bit restrictions, there is no longer any need to use the special MAP implementation on 64-bit Linux systems .

implementation on 64-bit Linux systems .

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

activated by default as of SAP Kernel 7.10. Solution

(2)

If you want to use the S

If you want to use the STD implementation with older SAP kernels, you can TD implementation with older SAP kernels, you can activate itactivate it using the profile parameter

using the profile parameter es/implementation=stdes/implementation=std.. Relevant parameters for the STD implementation Relevant parameters for the STD implementation A) SAP profile parameters

A) SAP profile parameters •

• em/initial_size_MBem/initial_size_MB

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

system.

In the SAP Extended Memory, there

In the SAP Extended Memory, there are additional SAP internal memory areas,are additional SAP internal memory areas, which cannot be directly accessed by the user contexts. These include the areas that are which cannot be directly accessed by the user contexts. These include the areas that are configured using the parameters em/global_area_MB and

configured using the parameters em/global_area_MB and abap/shared_objects_size_MB.abap/shared_objects_size_MB. Note: For the user contexts in the system, only the difference of

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) em/initial_size_MB - (em/global_area_MB + abap/shared_objects_size_MB) can be used as Extended Memory.

can be used as Extended Memory. •

• ztta/roll_extensionztta/roll_extension

This parameter specifies how much SAP Extended

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

individual user context.

This quota can be set d

This quota can be set differently for dialog and background work processes if ifferently for dialog and background work processes if necessary. To do this, use the

necessary. To do this, use the parametersparametersztta/roll_extension_diaztta/roll_extension_dia for dialog work for dialog work processes or

processes or ztta/roll_extension_nondiaztta/roll_extension_nondia for background work processes.for background work processes. The three profile parameters used with the MAP implementation

The three profile parameters used with the MAP implementation

((em/address_space_MBem/address_space_MB,,em/max_size_MBem/max_size_MB andandPHYS_MEMSIZEPHYS_MEMSIZE) are not relevant if ) are not relevant if you use the STD implementation.

you use the STD implementation.

B) Linux operating system parameters B) Linux operating system parameters The following Linux kernel parameters can

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

do this, you must edit the file /etc/sysctl.conf accordingly: •

• kernel.shmmaxkernel.shmmax

This kernel parameter specifies how large an

This kernel parameter specifies how large an individual SysV Shared Memoryindividual SysV Shared Memory Segment is allowed to be. In the case of an STD implementation, the parameter must be 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 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.

(3)

•

• kernel.shmallkernel.shmall

This kernel parameter specifies how much SysV Shared

This kernel parameter specifies how much SysV Shared Memory is available inMemory is available in the Linux system as a whole. As

the Linux system as a whole. As an estimate for the requirements of the SAP system, youan estimate for the requirements of the SAP system, you can use the total of the SAP Extended Memory (em/initial_size_MB) + SAP buffer can use the total of the SAP Extended Memory (em/initial_size_MB) + SAP buffer (transaction ST02 -> Detail analysis menu -> Storage, row

(transaction ST02 -> Detail analysis menu -> Storage, row with the entry "Total").with the entry "Total"). If several SAP systems are running on a Linux

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

server.

As a configuration recommendation, kernel. shmall can be configured as the As a configuration recommendation, kernel. shmall can be configured as the amount of virtual memory in the Linux

amount of virtual memory in the Linux system (RAM + Swap).system (RAM + Swap).

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

permits 20 GB SysV Shared Memory in the Linux system as a whole.system as a whole. •

• TMPFSTMPFS

With the STD implementation, the SAP Extended

With the STD implementation, the SAP Extended Memory is no longer stored inMemory is no longer stored in the TMPFS (under /dev/shm). However, the

the TMPFS (under /dev/shm). However, the TMPFS is required by the Virtual MachineTMPFS is required by the Virtual Machine Container (VMC). For this reason, we still recommend the same configuration of the Container (VMC). For this reason, we still recommend the same configuration of the TMPFS:

TMPFS:

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

•

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

first large memory type. The allocation sequence for "NonDia" work processes iswork processes is as follows:

as follows: 1. Roll

1. Roll memory (ztta/roll_first),memory (ztta/roll_first),

2. Heap memory (abap/heap_area_nondia), 2. Heap memory (abap/heap_area_nondia), 3. Roll memory (ztta/roll_area -

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

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

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

from that used in the MAP implementation: 1. Roll

1. Roll memory (ztta/roll_first),memory (ztta/roll_first), 2. Extended Memory

(4)

3. Roll memory (ztta/roll_area -

3. Roll memory (ztta/roll_area - ztta/roll_first)ztta/roll_first),, 4. Heap memory (abap/heap_area_dia).

4. Heap memory (abap/heap_area_dia).

The allocation sequence can be changed using the RSMEMORY report. The allocation sequence can be changed using the RSMEMORY report. •

• In transaction ST02, the "In Memory" display for the In transaction ST02, the "In Memory" display for the "Extended Memory" entry"Extended Memory" entry shows the SAP Extended Memory available for the SAP instance. The value of 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.

the parameter em/initial_size_MB is used as a basic value. However, theHowever, the Extended Memory is

Extended Memory isnotnotautomatically increased to the value of automatically increased to the value of em/max_size_MB with the STD implementation.

em/max_size_MB with the STD implementation.

Frequent problems in connection with the STD implementation Frequent problems in connection with the STD implementation The following problems or error messages may occur

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

implementation: •

• ERROR shmget() (28: No space left on device)ERROR shmget() (28: No space left on device) Example from dev_w0:

Example from dev_w0: ...

... M

M SHM_ROLL_ADM SHM_ROLL_ADM (addr: (addr: 0x2a99dc7000, 0x2a99dc7000, size: size: 2672386)2672386) M

M SHM_PAGING_ADM SHM_PAGING_ADM (addr: (addr: 0x2bb1ae6000, 0x2bb1ae6000, size: size: 656416)656416)

I *** ERROR => shmget(13040,112000000,2016) (28: No space left on device) I *** ERROR => shmget(13040,112000000,2016) (28: No space left on device) [shmux.c 1407]

[shmux.c 1407]

I *** ERROR => shmget(13040,112000000,992) (28: No space left on device) I *** ERROR => shmget(13040,112000000,992) (28: No space left on device) [shmux.c 1407]

[shmux.c 1407] I

I *** *** ERROR ERROR => => Shm Shm Pool Pool Create Create Error. Error. PoolKey=40, PoolKey=40, Key=48. Key=48. [shmux.c [shmux.c 1892]1892] ...

...

Example from dev_disp: Example from dev_disp: ...

...

EmInit: MmSetImplementation( 2 ). EmInit: MmSetImplementation( 2 ). MM global diagnostic options set: 0 MM global diagnostic options set: 0 client 0 initializing ....

client 0 initializing .... InitFreeList

InitFreeList

block size is 4096 kByte. block size is 4096 kByte. Using implementation std Using implementation std

EsStdUnamFileMapInit: shmget() of 10737418240 bytes failed. EsStdUnamFileMapInit: shmget() of 10737418240 bytes failed. errno = 28(No space left on device)

errno = 28(No space left on device) EsStdInit: unable to allocate 10240 MB EsStdInit: unable to allocate 10240 MB EsStdInit: try to allocate 8192 MB EsStdInit: try to allocate 8192 MB

errno = 28(No space left on device) EsStdInit: unable to allocate 8192 MB EsStdInit: unable to allocate 8192 MB

(5)

... ...

EsStdInit: try to allocate 8 MB EsStdInit: try to allocate 8 MB

errno = 28(No space left on device) EsStdInit: unable to allocate 8 MB EsStdInit: unable to allocate 8 MB EsStdInit: try to allocate 4 MB EsStdInit: try to allocate 4 MB ***

*** ERROR ERROR => => EsStdInit: EsStdInit: unable unable to to allocate allocate 10240 10240 MB MB [esuxi.c [esuxi.c 401]401] *** Error 11 while initializing OS dependent part.

*** Error 11 while initializing OS dependent part. *** ERROR

*** ERROR => D=> DpEmInit: pEmInit: EmInit EmInit (1) (1) [dpxxdisp.c [dpxxdisp.c 9559]9559] *** ERROR

*** ERROR => D=> DpMemInit: pMemInit: DpEmInit DpEmInit (-1) (-1) [dpxxdisp.c [dpxxdisp.c 9486]9486] *** DP_FATAL_ERROR => DpSapEnvInit: DpMemInit

*** DP_FATAL_ERROR => DpSapEnvInit: DpMemInit *** DISPATCHER EMERGENCY SHUTDOWN *** *** DISPATCHER EMERGENCY SHUTDOWN *** ...

...

According to 'man 2 shmget' , the error "No space left on device" (ENOSPC) 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 signifies that the requested memory exceeds the system limit for Shared Memory (SHMALL).

(SHMALL).

Therefore, check the value

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

(/proc/sys/kernel/shmall). •

• ERROR shmget() (22: Invalid argument)ERROR shmget() (22: Invalid argument) Example from dev_w0:

Example from dev_w0: ... ... A Fri Oct 22 16:18:47 2005 A Fri Oct 22 16:18:47 2005 A A A A ---PXA---PXA--- ----A

A PXA PXA INITIALIZATIONINITIALIZATION A

A System page System page size: 4kb, size: 4kb, admin_size: 31788kb.admin_size: 31788kb. I

I *** ERROR => s*** ERROR => shmget(11906,1126400000,2016) (22: Invalid argument) [hmget(11906,1126400000,2016) (22: Invalid argument) [shmux.cshmux.c 1904]

1904] A

A RABAX in RABAX in run level run level 1 A 1 A RABAX in RABAX in unkown environment: tunkown environment: task_type=0, run ask_type=0, run level=1,level=1, rabax state=80000000

rabax state=80000000 ...

...

According to 'man 2 shmget', the error "Invalid argument" (EINVAL) signifies According to 'man 2 shmget', the error "Invalid argument" (EINVAL) signifies that you try to create a Shared

that you try to create a Shared Memory Segment (in this case the ABAP program buffer Memory Segment (in this case the ABAP program buffer (abap/buffersize) that is larger than permitted by SHMMAX.

(abap/buffersize) that is larger than permitted by SHMMAX. Therefore, check the value

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

(/proc/sys/kernel/shmmax). •

(6)

In particular, after an operating system change to

In particular, after an operating system change to Linux, ensure that the profileLinux, ensure that the profile parameter "ES/TABLE" is not set using the

parameter "ES/TABLE" is not set using the SAP profiles (in other words, make sure thatSAP profiles (in other words, make sure that the SAP kernel default value

the SAP kernel default value "ES/TABLE = UNIX_STD" is reported)."ES/TABLE = UNIX_STD" is reported).

For example, if the instance profiles are copied from Advanced Interactive For example, if the instance profiles are copied from Advanced Interactive eXecutive (AIX), "ES/TABLE = SHM_SEGS" may be

eXecutive (AIX), "ES/TABLE = SHM_SEGS" may be set. As a result, the SAP systemset. As a result, the SAP system on Linux still uses the AIX memory management,

on Linux still uses the AIX memory management, even if "es/implementation = std" iseven if "es/implementation = std" is set. On Linux, this may result in a poor performance and increased paging.

set. On Linux, this may result in a poor performance and increased paging. In the SAP logs (dev_w*), setting "ES/TABLE

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

following: ...

... X

X EmInit: EmInit: MmSetImplementation( MmSetImplementation( 2 ).2 ). X

X MM global MM global diagnostic options diagnostic options set: 0set: 0 X

X EM/TOTAL_SIZE_MB EM/TOTAL_SIZE_MB = = 262144262144 ...

...

Remove parameters such as ES/TABLE, ES/SHM_SEG_SIZE, and Remove parameters such as ES/TABLE, ES/SHM_SEG_SIZE, and EM/TOTAL_SIZE_MB from the profiles and restart the instance.

EM/TOTAL_SIZE_MB from the profiles and restart the instance. Correct log entries are as follows:

Correct log entries are as follows: ...

... X

X EmInit: EmInit: MmSetImplementation( MmSetImplementation( 2 ).2 ). X

X MM global MM global diagnostic options diagnostic options set: 0set: 0 X client 0 initializing ....

X client 0 initializing .... X

X Using Using implementation implementation stdstd ...

...

Header Data Header Data

R

Releleeaasse e SSttaattuuss:: RReelleeaasseed d ffoor r CCususttoommeer r R

Reelleeaasseed d oonn:: 1122..1111..2200009 09 088::2200::4422 Ma

Mastster er LaLangnguauagege:: GeGerrmamann P

Prriioorriittyy:: RReeccoommmmeennddaattiioonnss//aaddddiittiioonnaal il innffoo C

Caatteeggoorryy:: CCoonnssuullttiinngg

Primary Component:BC-OP-LNX Linux Primary Component:BC-OP-LNX Linux Affected Releases

(7)

Software Software Component

Component ReleaseRelease

From From Release Release To To Release Release And And subsequent subsequent K KRRNNLL6644NNUUCC 66..4400 66..4400 66..4400 XX K KRRNNLL6644NNUUCC 77..0000 77..0000 77..0000 XX K KRRNNLL6644UUCC 66..4400 66..4400 66..4400 XX K KRRNNLL6644UUCC 77..0000 77..0000 77..0000 XX K KRRNNLL6644UUCC 77..1100 77..1100 77..1100 XX Subscribe

Subscribe|| Add to FavoritesAdd to Favorites

Note 171356 - SAP software on

Note 171356 - SAP software on Linux: Essential informationLinux: Essential information

Summary Summary Symptom Symptom

You want to install SAP software on

You want to install SAP software on Linux.Linux. Other terms

Other terms

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

IA-64, IA64, x86_64, AMD, Opteron, EM64T, POWER, zSeries, System z Reason and Prerequisites

Reason and Prerequisites

You want to install SAP software on

You want to install SAP software on Linux. You require the appropriate LinuxLinux. You require the appropriate Linux distribution and permitted hardware to do this.

distribution and permitted hardware to do this.

After you successfully install Linux and before you carry out the

After you successfully install Linux and before you carry out the actual SAP installation,actual SAP installation, you must also take some other matters into consideration

you must also take some other matters into consideration that are not mentioned in thethat are not mentioned in the installation guide and are therefore addressed in this note.

installation guide and are therefore addressed in this note. Solution

Solution

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

Contents

I/.... Released Linux Distributions: I/.... Released Linux Distributions: II/... Supported hardware

II/... Supported hardware

III/.. Other Linux environments that are supported. III/.. Other Linux environments that are supported. IV/... Special notes about installing the operating

(8)

V/ .... General notes about

V/ .... General notes about installing the operating systeminstalling the operating system VI/ ... SAP software: saplocales

VI/ ... SAP software: saplocales VII/ .. SAP software: NPTL VII/ .. SAP software: NPTL

VIII/ . SAP software: Additional comments: VIII/ . SAP software: Additional comments: IX/ .., Notes that are specific to the

IX/ .., Notes that are specific to the databasedatabase X/ .... Notes about IBM Power

X/ .... Notes about IBM Power

XI/ ... Mounting installation CDs and installation DVDs XI/ ... Mounting installation CDs and installation DVDs

XII/ .. Adding Linux application servers to existing SAP systems XII/ .. Adding Linux application servers to existing SAP systems XIII/ . Using virtualization technologies

XIII/ . Using virtualization technologies XIV/ .. Use of Raw Devices,

XIV/ .. Use of Raw Devices, "Journaling File system" and LVM"Journaling File system" and LVM I/ Released Linux Distributions

I/ Released Linux Distributions

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

Linux:

1. 64-bit systems: 1. 64-bit systems: •

• SUSE Linux Enterprise Server 11SUSE Linux Enterprise Server 11

o

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

(SLES11-x86_64) x86_64)

o

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

o SUSE Linux Enterprise Server 11 for IBM System zSUSE Linux Enterprise Server 11 for IBM System z

(SLES11-ZS, see Note 81737

(SLES11-ZS, see Note 81737 for information about supported Linuxfor information about supported Linux kernels, glibc versions and required packages)

kernels, glibc versions and required packages)

o

o SUSE Linux Enterprise Server 11 for Intel Itanium2 Proc. FamilySUSE Linux Enterprise Server 11 for Intel Itanium2 Proc. Family

(SLES11-IPF) (SLES11-IPF) •

o

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

(SLES10-x86_64) x86_64)

o

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

o SUSE Linux Enterprise Server 10 for IBM System zSUSE Linux Enterprise Server 10 for IBM System z

(SLES10-ZS, see Note 81737

(SLES10-ZS, see Note 81737 for information about supported Linuxfor information about supported Linux kernels, glibc versions and required packages)

o

(SLES10-IPF) (SLES10-IPF)

(9)

•

o

o SUSE Linux Enterprise Server 9 for AMD64 & Intel EM64TSUSE Linux Enterprise Server 9 for AMD64 & Intel EM64T

(SLES9-x86_64,

(SLES9-x86_64,for release information, see Note 816097for release information, see Note 816097))

o

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

o SUSE Linux Enterprise Server 9 for zSeriesSUSE Linux Enterprise Server 9 for zSeries

(SLES9-ZS, see Note 81737 for

(SLES9-ZS, see Note 81737 for information about supported Linuxinformation about supported Linux kernels, glibc versions and required packages)

o

o SUSE Linux Enterprise Server 9 for Intel Itanium2 Proc. Family (SLES9-SUSE Linux Enterprise Server 9 for Intel Itanium2 Proc. Family

(SLES9-IPF) IPF) •

o

o SUSE Linux Enterprise Server 8 for zSeriesSUSE Linux Enterprise Server 8 for zSeries

(SLES8-ZS, see Note 81737 for

(SLES8-ZS, see Note 81737 for information about supported Linuxinformation about supported Linux kernels, glibc versions and required packages)

o

(SLES8-IPF,

(SLES8-IPF,for release information, see Note 623653for release information, see Note 623653)) •

• Red Hat Enterprise Linux 5Red Hat Enterprise Linux 5

o

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

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

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

o Red Hat Enterprise Linux 5 for IBM System z (RHEL5-ZS, see NoteRed Hat Enterprise Linux 5 for IBM System z (RHEL5-ZS, see Note

81737 for information about supported Linux

81737 for information about supported Linux kernels, glibc versions andkernels, glibc versions and required packages)

required packages) •

• Red Hat Enterprise Linux 4Red Hat Enterprise Linux 4

o

o Red Hat Enterprise Linux 4 for AMD64 & Intel EM64TRed Hat Enterprise Linux 4 for AMD64 & Intel EM64T

(RHEL4-x86_64,

(RHEL4-x86_64,for release information, see Note 816097for release information, see Note 816097))

o

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

o Red Hat Enterprise Linux 4 for Intel Itanium (RHEL4-IA64)Red Hat Enterprise Linux 4 for Intel Itanium (RHEL4-IA64)

•

(10)

o

o Red Hat Enterprise Linux 3 for Intel Itanium (RHEL3-IA64)Red Hat Enterprise Linux 3 for Intel Itanium (RHEL3-IA64)

2. 32-bit systems: 2. 32-bit systems:

o

o SUSE Linux Enterprise Server 10 for x86 (SLES10-X86)SUSE Linux Enterprise Server 10 for x86 (SLES10-X86) o

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

o SUSE Linux Enterprise Server 8 (SLES8)SUSE Linux Enterprise Server 8 (SLES8) o

o SUSE Linux Standard Server 8SUSE Linux Standard Server 8

(Note: As a result, all statements used for the 32-bit version of

(Note: As a result, all statements used for the 32-bit version of SUSESUSE Linux Enterprise Server 8 also apply for the

Linux Enterprise Server 8 also apply for the 32-bit version of the SUSE32-bit version of the SUSE Linux Standard Server 8.)

Linux Standard Server 8.)

o

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

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

o Red Hat Enterprise Linux 3 (RHEL3)Red Hat Enterprise Linux 3 (RHEL3)

The following Linux distribution was also released for 32-bit systems and R/3

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

4.x, but not for the recommended SAP kernel in the EXT version (4.0B_EXT, 4.5B_EXT, 4.6D_EXT):

4.5B_EXT, 4.6D_EXT):

o

o Red Hat Enterprise Linux 2.1 (RHEL2.1)Red Hat Enterprise Linux 2.1 (RHEL2.1)

If you want to change over to the EXT kernel and already use an earlier Linux 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. 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 Up to and including SAP Release 4.6x, the following technically obsolete Linux distributions are also available

distributions are also available for 32-bit systems:for 32-bit systems:

o

o SUSE Linux Enterprise Server 7 (SLES7)SUSE Linux Enterprise Server 7 (SLES7)

(Note: see Note 750884 for information about the end of maintenance for (Note: see Note 750884 for information about the end of maintenance for SUSE SLES7)

SUSE SLES7)

o

o SUSE Linux Enterprise Server (SLES)SUSE Linux Enterprise Server (SLES) o

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

o Red Hat 6.2Red Hat 6.2 o

(11)

For further information about this, see Note 171

For further information about this, see Note 171356 (up to and including 356 (up to and including Version 173).Version 173). As soon as you use SAP

As soon as you use SAP software on one of the specified Linux software on one of the specified Linux distributions, we stronglydistributions, we strongly recommend that you take out a

recommend that you take out aservice contractservice contract. You can do this via the manufacturer of . You can do this via the manufacturer of the Linux distribution or via an

the Linux distribution or via an OEM provider, who will offer an equal level OEM provider, who will offer an equal level of supportof support for one of the distributions certified by SAP. Otherwise, support may be

for one of the distributions certified by SAP. Otherwise, support may be denied if errorsdenied if errors occur in connection with the operating system.

occur in connection with the operating system. II/ Supported hardware

II/ Supported hardware

Note that only the host types released by

Note that only the host types released by the hardware partners are suitable for using SAPthe hardware partners are suitable for using SAP software productively on Linux.

software productively on Linux.

For current information about this, see the following

For current information about this, see the following SAP Notes:SAP Notes: 606107 (Bull) 606107 (Bull) 1403020 (Cisco) 1403020 (Cisco) 300900 (Dell) 300900 (Dell) 171383 (Fujitsu Siemens) 171383 (Fujitsu Siemens) 171371 (HP) 171371 (HP) 171380 (IBM) 171380 (IBM) 765424 (IBM POWER) 765424 (IBM POWER) 411970 (IBM zSeries) 411970 (IBM zSeries) 1379130 (NEC) 1379130 (NEC) 907727 (SGI) 907727 (SGI) 597470 (SUN) 597470 (SUN) 832402 (Unisys) 832402 (Unisys)

Furthermore, you can find information on

Furthermore, you can find information on the Internet:the Internet: http://www.sap.com/linux

http://www.sap.com/linux (Link: (Link: "Supported "Supported Platforms")Platforms")

If you are unsure about what to do, you can contact the hardware partners that are If you are unsure about what to do, you can contact the hardware partners that are represented in SAP LinuxLab, for

represented in SAP LinuxLab, for example by email: [email protected] by email: [email protected] Other Linux environments that are supported.

Other Linux environments that are supported.

Using SAP software is also permitted in certain Linux environments. Using SAP software is also permitted in certain Linux environments. For current information about this, see the following

For current information about this, see the following SAP Notes:SAP Notes: 1278782 (Egenera)

1278782 (Egenera) 1266874 (Symantec) 1266874 (Symantec)

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

[email protected]

IV/ Special notes about installing the operating system IV/ Special notes about installing the operating system

•

• Red Hat Linux: InstallationRed Hat Linux: Installation

Prior to the installation, refer to the notes corresponding to your Red Hat version Prior to the installation, refer to the notes corresponding to your Red Hat version from the following list:

(12)

1048303 (Red Hat Enterprise Linux 5) 1048303 (Red Hat Enterprise Linux 5)

722273 (Red Hat Enterprise Linux 3 and 4) 722273 (Red Hat Enterprise Linux 3 and 4) 625674 (RHEL 2.1: Notes on installation) 625674 (RHEL 2.1: Notes on installation)

618173 (RHEL 2.1: on Red Hat Enterprise Linux 2.1) 618173 (RHEL 2.1: on Red Hat Enterprise Linux 2.1) •

• SUSE Linux: InstallationSUSE Linux: Installation

Prior to the installation, refer to the note corresponding

Prior to the installation, refer to the note corresponding to your SUSE versionto your SUSE version from the following list:

from the following list:

1310037 (SUSE Linux Enterprise Server 1

1310037 (SUSE Linux Enterprise Server 11: Installation notes)1: Installation notes) 958253 (SUSE Linux Enterprise Server 1

958253 (SUSE Linux Enterprise Server 10: Installation notes)0: Installation notes) 797084 (SUSE Linux Enterprise Server 9

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

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

o

o Among other things, this note describes the "sapinit" RPM (or up to andAmong other things, this note describes the "sapinit" RPM (or up to and

including SLES 9 Service Package 2: "SUSE-sapinit" RPM). This should including SLES 9 Service Package 2: "SUSE-sapinit" RPM). This should be installed in order for the parameters of

be installed in order for the parameters of the Linux kernel to be setthe Linux kernel to be set correctly.

correctly.

o

o If you use the BRTOOLS (for example If you use the BRTOOLS (for example brbackup) delivered by SAP,brbackup) delivered by SAP,

problems may arise when the system compresses data files. As of SLES problems may arise when the system compresses data files. As of SLES 8,8, Novell SUSE does not deliver

Novell SUSE does not deliver the "compress" program that is otherwisethe "compress" program that is otherwise used on UNIX for licensing reasons. The problem can be avoided if you used on UNIX for licensing reasons. The problem can be avoided if you set the following parameters in the file init<SID>.sap:

set the following parameters in the file init<SID>.sap: compress_cmd = "gzip -c $ > $"

compress_cmd = "gzip -c $ > $" uncompress_cmd = "gunzip -c $ > $" uncompress_cmd = "gunzip -c $ > $" V/ General notes about installing the operating system V/ General notes about installing the operating system

•

• System languageSystem language

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

are running SAP software. •

• Swap spaceSwap space

While the Linux distribution is being installed, create partitions of the type While the Linux distribution is being installed, create partitions of the type "swap" when you organize the

"swap" when you organize the hard disk(s).hard disk(s).

Recommended total size: Twice the main memory structure (2 x RAM). 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 According to Note 153641, a swap space of 20 GB is generally sufficient on 64- bit Linux for operating an SAP

bit Linux for operating an SAP system (including the database).system (including the database). For earlier 32-bit Linux versions, the maximum size of

For earlier 32-bit Linux versions, the maximum size of a swap partition is 2 GB,a swap partition is 2 GB, but if you require more space, distribute the swap

but if you require more space, distribute the swap space over multiple swapspace over multiple swap partitions.

partitions.

The Linux kernel does not

The Linux kernel does not usually require much swap space, since other limitsusually require much swap space, since other limits have already been reached before the swap space has reached full capacity ("late have already been reached before the swap space has reached full capacity ("late swap allocation").

swap allocation").

However, if you discover that more swap space

(13)

software, you can use the distribution-specific tools to increase your swap space software, you can use the distribution-specific tools to increase your swap space at any time.

at any time. •

• HostnameHostname

The "hostname" command must only return the

The "hostname" command must only return the host name and not the host name and not the "Fully"Fully Qualified Domain Name" (for example: Fully Qualified Domain Name: Qualified Domain Name" (for example: Fully Qualified Domain Name:

ls3001.wdf.sap-ag.de; required output from "hostname": ls3001). ls3001.wdf.sap-ag.de; required output from "hostname": ls3001). Distribution-specific tools are available to change the host name.

specific tools are available to change the host name. •

• Updating RPM packagesUpdating RPM packages

The distributors (Novell SUSE and Red Hat) regularly provide u

The distributors (Novell SUSE and Red Hat) regularly provide u pdates for your pdates for your software. The distributors test these updates with regard to compatibility with the 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 SAP software before releasing them. From an SAP point of view, these updates can be imported in the

can be imported in the productive environment immediately after they areproductive environment immediately after they are available. This compatibility is guaranteed only if the original packages

available. This compatibility is guaranteed only if the original packages of theof the distributors are used, to which a customer is entitled within the framework of a distributors are used, to which a customer is entitled within the framework of a valid support contract with the distributor or an authorized

valid support contract with the distributor or an authorized OEM.OEM.

The same also applies for the "Collections of updates", that is "Service Packs" The same also applies for the "Collections of updates", that is "Service Packs" (Novell SUSE) or "Updates" (Red Hat).

(Novell SUSE) or "Updates" (Red Hat).

We recommend that you import the latest available

We recommend that you import the latest available "Service Pack" (Novell"Service Pack" (Novell SUSE) or the latest "Update" (Red Hat). You should use the latest available SUSE) or the latest "Update" (Red Hat). You should use the latest available installation media when you are installing this.

installation media when you are installing this.

If an update to an imported package (for example, kernel or glibc) unexpectedly 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.

does not work, return to the last Service Pack or update level that worked. Note for all "Service Packs" and "Updates"

Note for all "Service Packs" and "Updates": If you are using a non-Unicode: If you are using a non-Unicode version of the SAP software, you must install the "saplocales"

version of the SAP software, you must install the "saplocales" again after everyagain after every update of the "glibc" RPM (see below or Note 516716).

update of the "glibc" RPM (see below or Note 516716). Also note

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

kernel, see Note 784391. VI/ SAP software: saplocales VI/ SAP software: saplocales For non-Unicode versions of the S

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

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 thisIf you set up Unicode systems only, you can ignore the next section of this note.

note. •

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

It is therefore essential that you refer to this note. •

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

(14)

These are the available "saplocales" packages: These are the available "saplocales" packages: 1) Red Hat Enterprise Linux 2.1

1) Red Hat Enterprise Linux 2.1 saplocales-2.20.4-1

saplocales-2.20.4-1 # # adjusted adjusted SAP SAP code code pagespages

(see saplocales_rhel21_i386_version-1.zip, attached to this note) (see saplocales_rhel21_i386_version-1.zip, attached to this note) 2) Red Hat Enterprise Linux 3

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

(see saplocales_rhel30_i386_version-6.zip, attached to this note) (see saplocales_rhel30_i386_version-6.zip, attached to this note) 3) Red Hat Enterprise Linux 3

3) Red Hat Enterprise Linux 3 (64-bit systems)(64-bit systems) saplocales-2.3.2-5

saplocales-2.3.2-5 # # adjusted adjusted SAP SAP code code pagespages saplocales-32bit-2.3.2-5

saplocales-32bit-2.3.2-5 # # adjusted adjusted SAP SAP code code pagespages

(see saplocales_rhel30_ia64_version-5.zip, attached to this note) (see saplocales_rhel30_ia64_version-5.zip, attached to this note) 4) Red Hat Enterprise Linux 4 for x86

4) Red Hat Enterprise Linux 4 for x86 saplocales-2.3.4-4

(see saplocales_rhel40_i386_version-4.zip, attached to this note) (see saplocales_rhel40_i386_version-4.zip, attached to this note) 5) Red Hat Enterprise Linux 4 for AMD64 & Intel EM64T

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

(see saplocales_rhel40_x8664_version-4.zip, attached to this note) (see saplocales_rhel40_x8664_version-4.zip, attached to this note) 6) Red Hat Enterprise Linux 4 for IBM POWER

6) Red Hat Enterprise Linux 4 for IBM POWER saplocales-2.3.4-4

(see saplocales_rhel40_ppc64_version-4.zip, attached to this note) (see saplocales_rhel40_ppc64_version-4.zip, attached to this note) 7) Red Hat Enterprise Linux 4 for Intel Itanium

7) Red Hat Enterprise Linux 4 for Intel Itanium saplocales-2.3.4-4

(see saplocales_rhel40_ia64_version-4.zip, attached to this note) (see saplocales_rhel40_ia64_version-4.zip, attached to this note) 8) Red Hat Enterprise Linux 5 for x86

8) Red Hat Enterprise Linux 5 for x86 saplocales-2.5-2

saplocales-2.5-2 # # adjusted adjusted SAP SAP codepagescodepages

(see saplocales_rhel5_i386_version-2.zip, attached to this note) (see saplocales_rhel5_i386_version-2.zip, attached to this note) 9) Red Hat Enterprise Linux 5 for AMD64 & Intel EM64T

9) Red Hat Enterprise Linux 5 for AMD64 & Intel EM64T saplocales-2.5-2

(15)

(see saplocales_rhel5_x86_64_version-2.zip, attached to this note) (see saplocales_rhel5_x86_64_version-2.zip, attached to this note) 10) Red Hat Enterprise Linux 5

10) Red Hat Enterprise Linux 5 for IBM POWER for IBM POWER saplocales-2.5-2

(see saplocales_rhel5_ppc64_version-2.zip, attached to this note) (see saplocales_rhel5_ppc64_version-2.zip, attached to this note) 11) Red Hat Enterprise Linux 5

11) Red Hat Enterprise Linux 5 for IBM System zfor IBM System z saplocales-2.5-2

(see saplocales_rhel5_s390x_version-2.zip, attached to this note) (see saplocales_rhel5_s390x_version-2.zip, attached to this note) 12) Red Hat Enterprise Linux 5

12) Red Hat Enterprise Linux 5 for Intel Itaniumfor Intel Itanium saplocales-2.5-2

(see saplocales_rhel5_ia64_version-2.zip, attached to this note) (see saplocales_rhel5_ia64_version-2.zip, attached to this note) 13) SUSE Linux Enterprise Server 8 (32-bit systems)

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

(see saplocales_sles8_i386_version-4.zip, attached to this note) (see saplocales_sles8_i386_version-4.zip, attached to this note) 14) SUSE Linux Enterprise Server 8 for IBM zSeries

14) SUSE Linux Enterprise Server 8 for IBM zSeries saplocales-2.2.5-2

(see saplocales_sles8_s390x_version-2.zip, attached to this note) (see saplocales_sles8_s390x_version-2.zip, attached to this note) 15) SUSE Linux Enterprise Server 8 for Intel Itanium2 Proc. Family 15) SUSE Linux Enterprise Server 8 for Intel Itanium2 Proc. Family

saplocales-2.2.5-3

(see saplocales_sles8_ia64_version-3.zip, attached to this note) (see saplocales_sles8_ia64_version-3.zip, attached to this note) 16) SUSE Linux Enterprise Server 9 for x86

16) SUSE Linux Enterprise Server 9 for x86 saplocales-2.3.3-11

(see saplocales_sles9_i386_version-11.zip, attached to this note) (see saplocales_sles9_i386_version-11.zip, attached to this note) 17) SUSE Linux Enterprise Server 9 for AMD64 & Intel EM64T 17) SUSE Linux Enterprise Server 9 for AMD64 & Intel EM64T

saplocales-2.3.3-11

(see saplocales_sles9_x86_64_version-11.zip, attached to this note) (see saplocales_sles9_x86_64_version-11.zip, attached to this note) 18) SUSE Linux Enterprise Server 9 for IBM POWER

(16)

saplocales-2.3.3-11

(see saplocales_sles9_ppc64_version-11.zip, attached to this note) (see saplocales_sles9_ppc64_version-11.zip, attached to this note) 19) SUSE Linux Enterprise Server 9 for IBM zSeries

19) SUSE Linux Enterprise Server 9 for IBM zSeries saplocales-2.3.3-11

saplocales-2.3.3-11

(see saplocales_sles9_ia64_version-11.zip, attached to this note) (see saplocales_sles9_ia64_version-11.zip, attached to this note) 21) SUSE Linux Enterprise Server 10 for x86

21) SUSE Linux Enterprise Server 10 for x86 Up to SLES 10 Service Pack 1:

Up to SLES 10 Service Pack 1: saplocales-2.4-2

saplocales-2.4-2 # # modified modified SAP SAP codepagescodepages

(see saplocales_sles10_i386_version-2.zip, attached to this note) (see saplocales_sles10_i386_version-2.zip, attached to this note) As of SLES 10 Service Pack 2:

As of SLES 10 Service Pack 2: saplocales-2.4-3

(see saplocales_sles10_i386_version-3.zip, attached to this note) (see saplocales_sles10_i386_version-3.zip, attached to this note) 22) SUSE Linux Enterprise Server 10

22) SUSE Linux Enterprise Server 10 for AMD64 & Intel EM64Tfor AMD64 & Intel EM64T Up to SLES 10 Service Pack 1:

(see saplocales_sles10_x8664_version-2.zip, attached to this note) (see saplocales_sles10_x8664_version-2.zip, attached to this note) As of SLES 10 Service Pack 2:

(see saplocales_sles10_x8664_version-4.zip, attached to this note) (see saplocales_sles10_x8664_version-4.zip, attached to this note) 23) SUSE Linux Enterprise Server 10 for IBM POWER

23) SUSE Linux Enterprise Server 10 for IBM POWER Up to SLES 10 Service Pack 1:

(see saplocales_sles10_ppc64_version-2.zip, attached to this note) (see saplocales_sles10_ppc64_version-2.zip, attached to this note) As of SLES 10 Service Pack 2:

(see saplocales_sles10_ppc64_version-3.zip, attached to this note) (see saplocales_sles10_ppc64_version-3.zip, attached to this note) 24) SUSE Linux Enterprise Server 10 for IBM System z

(17)

Up to SLES 10 Service Pack 1: Up to SLES 10 Service Pack 1: saplocales-2.4-2

saplocales-2.4-2 # # modified modified SAP SAP codepagescodepages saplocales-32bit-2.4-2

saplocales-32bit-2.4-2 # # adjusted adjusted SAP SAP code code pagespages

(see saplocales_sles10_s390x_version-2.zip, attached to this note) (see saplocales_sles10_s390x_version-2.zip, attached to this note) As of SLES 10 Service Pack 2:

Up to SLES 10 Service Pack 1: Up to SLES 10 Service Pack 1: saplocales-2.4-2

(see saplocales_sles10_ia64_version-2.zip, attached to this note) (see saplocales_sles10_ia64_version-2.zip, attached to this note) As of SLES 10 Service Pack 2:

(see saplocales_sles10_ia64_version-3.zip, attached to this note) (see saplocales_sles10_ia64_version-3.zip, attached to this note) 26) SUSE Linux Enterprise Server 11:

26) SUSE Linux Enterprise Server 11: Use the "sap-locale" RPM package

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

update channels (see Notes 187864 and 1310037).

The "saplocales" RPM packages are attached to this note. If this contains a more recent 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 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:

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 The attachments to this note are zip archives that you can unpack as shown in the following example:

following example:

unzip saplocales_sles10_x8664_version-4.zip unzip saplocales_sles10_x8664_version-4.zip You can import the resulting RPM pac

You can import the resulting RPM packages as follows:kages as follows: rpm -ivh saplocales-2.4-4.x86_64.rpm

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

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

Note 516716).

VII/ SAP software: NPTL VII/ SAP software: NPTL

(18)

Current Linux distributions (as of Red Hat Enterprise Linux 3 Current Linux distributions (as of Red Hat Enterprise Linux 3 andand SUSE Linux Enterprise Server 9) are b

SUSE Linux Enterprise Server 9) are based on "Native Posix Threading ased on "Native Posix Threading Library"Library" (NPTL). This is an improved implementation of the

(NPTL). This is an improved implementation of the threading mechanism. It adheresthreading mechanism. It adheres more closely to the POSIX requirements than the

more closely to the POSIX requirements than the previous implementation on Linuxprevious implementation on Linux ("LinuxThreads").

("LinuxThreads").

As regards NPTL, note that some

As regards NPTL, note that some software must first be adjusted to NPTL so that it cansoftware 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 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

compatibility mode, so that problem software can also be used on NPTL. To used on NPTL. To do this, setdo this, set the environment variable LD_ASSUME_KERNEL to 2.4.1:

the environment variable LD_ASSUME_KERNEL to 2.4.1: Bash Shell: export LD_ASSUME_KERNEL=2.4.1 Bash Shell: export LD_ASSUME_KERNEL=2.4.1 C

C shell: shell: setenv setenv LD_ASSUME_KERNEL LD_ASSUME_KERNEL 2.4. 2.4. 11 The following SAP software requires you to set the

The following SAP software requires you to set the environment variableenvironment variable LD_ASSUME_KERNEL to 2.4.1 before you execute this software. LD_ASSUME_KERNEL to 2.4.1 before you execute this software. 1) SAP kernels up to and including Version 6.20

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 (Exception: the current patch level of the SAP kernel 4.6D_EXT and 6.20

are compatible with NPTL.) are compatible with NPTL.)

(Note: Your SAP kernel is not compatible w

(Note: Your SAP kernel is not compatible with NPTL if, for example,ith NPTL if, for example, the call of "disk+work" ends with a

the call of "disk+work" ends with a "Floating Point Exception".)

"Floating Point Exception".) 2) SAPINST

2) SAPINST

3) SAP DB database or MaxDB database, see Note 788272 3) SAP DB database or MaxDB database, see Note 788272

(Exception: versions for AMD64/EM64T) (Exception: versions for AMD64/EM64T) 4) Oracle database: runInstaller,

4) Oracle database: runInstaller,

However, there is also the opposite case that LD_ASSUME_KERNEL cannot be set, or However, there is also the opposite case that LD_ASSUME_KERNEL cannot be set, or at least not to a v

at least not to a value lower than 2.4.21. This alue lower than 2.4.21. This applies to the following SAP software:applies to the following SAP software: •

• SAP kernel as of Version 7.00SAP kernel as of Version 7.00 As of Version 7.0, the SAP ke

As of Version 7.0, the SAP kernel generates the following error message:rnel generates the following error message: "SAP Web Application Server requires NPTL on Linux."

"SAP Web Application Server requires NPTL on Linux." "Please refer to section NPTL of SAP note 171356." "Please refer to section NPTL of SAP note 171356."

"Running in LinuxThreads-compatibility mode only allowed "Running in LinuxThreads-compatibility mode only allowed

while running a SAP upgrade." while running a SAP upgrade."

If the error message occurs during an SAP upgrade, you can ignore it. Otherwise, If the error message occurs during an SAP upgrade, you can ignore it. Otherwise, deactivate the environment variable LD_ASSUME_KERNEL,

deactivate the environment variable LD_ASSUME_KERNEL, to avoid gettingto avoid getting the error message.

the error message.

VIII/ SAP software: Additional comments: VIII/ SAP software: Additional comments: SAP kernel 7.10 on RHEL 4 or SLES 9 SAP kernel 7.10 on RHEL 4 or SLES 9 If you want to use the S

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

(19)

IX/ Notes that are specific to the database IX/ Notes that are specific to the database

Informix database: Additional installation notes (R/3 4.0B and 4.5B) 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 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 must take into account important additional information. In this regard, the subdirectory UNIX/LINUX_32 on the kernel CD contains

UNIX/LINUX_32 on the kernel CD contains the file README. Its contents arethe file README. Its contents are particularly important if you are trying to avoid problems that are associated with 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"). "password encryption" (/etc/pam.d/passwd contains the entry "crypt" instead of "md5").

DB2 UDB database: Additional RPM packages required DB2 UDB database: Additional RPM packages required If you want to use DB2 UDB

If you want to use DB2 UDB as a database, you must install the support for the as a database, you must install the support for the KornKorn shell before installing the DB2 database software. The

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

is available on one of the Linux installation CDs.of the Linux installation CDs. Additional considerations for DB2 on IBM POWER: Additional considerations for DB2 on IBM POWER:

•

• DB2 UDB V8 (as of FixPak 9)DB2 UDB V8 (as of FixPak 9)

o

o SLES 9 or higher - IBM XL C/C++ Advanced Editions V7.0/V8.0 for theSLES 9 or higher - IBM XL C/C++ Advanced Editions V7.0/V8.0 for the

Linux runtime environment component Linux runtime environment component

o

o RHEL 4 or higher - IBM XL RHEL 4 or higher - IBM XL C/C++ Advanced Editions V7.0/V8.0 for theC/C++ Advanced Editions V7.0/V8.0 for the

Linux runtime environment component Linux runtime environment component •

• DB2 UDB V9DB2 UDB V9

o

o SLES 9 Service Package 2 or higher - IBM XL C/C++ Advanced EditionsSLES 9 Service Package 2 or higher - IBM XL C/C++ Advanced Editions

V8.0 for the Linux runtime environment component V8.0 for the Linux runtime environment component

o

o RHEL 4 U2 or higher RHEL 4 U2 or higher - IBM XL C/C++ Advanced Editions V8.0 - IBM XL C/C++ Advanced Editions V8.0 for thefor the

Linux runtime environment component Linux runtime environment component You can find further information below in

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

Power".

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

•

• Oracle 10g:Oracle 10g:

o

o SLES 9 or higher - IBM XL C/C++ Advanced Editions V7.0/8.0 for theSLES 9 or higher - IBM XL C/C++ Advanced Editions V7.0/8.0 for the

(20)

o

o RHEL 4 or higher - IBM XL RHEL 4 or higher - IBM XL C/C++ Advanced Editions V7.0/8.0 for theC/C++ Advanced Editions V7.0/8.0 for the

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

Important: You must meet certain requirements to install Oracle 10g with the "IBM XL: 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 C/C++ Advanced Editions V8.0 for the Linux runtime environment component". For more detailed information about this workaround, see Note 975196.

more detailed information about this workaround, see Note 975196. X/ Notes about IBM Power

X/ Notes about IBM Power For DB2 UDB Version V9, V8

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

available at:

http://www.ibm.com/software/awdtools/xlcpp/support http://www.ibm.com/software/awdtools/xlcpp/support Here, search for "Linux Runtime".

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

kernel version.

Additional prerequisites: Additional prerequisites:

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

supported by SAP.

o

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

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

Install the RPM packages of the v7.

Install the RPM packages of the v7. 0 runtime component in this order:0 runtime component in this order: a) xlsmp.msg.rte-1.5.0 a) xlsmp.msg.rte-1.5.0 b) xlsmp.rte-1.5.0 b) xlsmp.rte-1.5.0 c) vacpp.rte-7.0.0 c) vacpp.rte-7.0.0 The v7.0.1 runtime component

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

supported by SAP.

o

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

POWER POWER

o

o SUSE LINUX Enterprise Server 9.0 (SLES 9) for IBM POWER 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: Install the RPM packages of the v7.0. 1 runtime component in this order:

a)

a) vacpp.rte-7.0.1-1 vacpp.rte-7.0.1-1 (or (or a a more more recent recent version)version) b)

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

(21)

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

supported by SAP.

o

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

POWER POWER

o

o SUSE Linux Enterprise Server 9 Service Pack 2 (SLES 9 Service PackageSUSE Linux Enterprise Server 9 Service Pack 2 (SLES 9 Service Package

2) for IBM POWER 2) for IBM POWER

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

a)

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

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

c) vacpp.rte-8.0.0-0.ppc64.rpm vacpp.rte-8.0.0-0.ppc64.rpm (or (or a a more more recent recent version)version) XI/ Mounting installation CDs and installation DVDs

XI/ Mounting installation CDs and installation DVDs

All installation CDs and installation DVDs created without a Rock Ridge Extension must All installation CDs and installation DVDs created without a Rock Ridge Extension must be included in the

be included in the file system with the option -o map=off, so that file names appeafile system with the option -o map=off, so that file names appea r withr with upper case spelling. You can use the following command accordingly:

upper case spelling. You can use the following command accordingly: mount -r -t iso9660 -o map=off /dev/cdrom /mnt/cdrom

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

XII/ Adding Linux application servers to existing SAP systems 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 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

SAP system (at least Release 4.0B). See also Notes 156548 and 5310Notes 156548 and 531069. This measure69. This measure alone does not involve any additional license costs.

alone does not involve any additional license costs. The "Windows central instance with Linux ap

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

of your SAP server.

To install the application server, you require bo

To install the application server, you require both the Linux distribution (see above) andth the Linux distribution (see above) and the kernel CD provided for Linux

the kernel CD provided for Linux from the set of installation or upgrade CDs for your from the set of installation or upgrade CDs for your SAP release. You can

SAP release. You can obtain this kernel CD free of charge obtain this kernel CD free of charge from your SAP sales partner.from your SAP sales partner. We are aware of one (possible) problem regarding heterogeneous SAP systems: For We are aware of one (possible) problem regarding heterogeneous SAP systems: For non-Unicode systems, the

Unicode systems, the sort sequencesort sequence depends on the operating system used. There are nodepends on the operating system used. There are no specific requirements defined by SAP in this regard.

specific requirements defined by SAP in this regard. For this reason, different results areFor this reason, different results are possible when outputting lists on different application servers.

possible when outputting lists on different application servers. A similar problem may occur if you migrate the

A similar problem may occur if you migrate the existing SAP system from another existing SAP system from another operating system to Linux. After the migration, the sort sequence

operating system to Linux. After the migration, the sort sequence may have changed.may have changed. For all problems concerning the sort sequen

For all problems concerning the sort sequence, the Linux distributors offer the option of ce, the Linux distributors offer the option of adjusting the Linux sort sequence to customer-specific requirements as part of the

adjusting the Linux sort sequence to customer-specific requirements as part of the support. For more information, see Note 1069443.

(22)

XIII/ Using virtualization technologies XIII/ Using virtualization technologies For more information about which SAP

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

Linux, see Note 1122387.

XIV/ Use of Raw Devices, "Journaling File system", and LVM XIV/ Use of Raw Devices, "Journaling File system", and LVM For information about using Raw Devices

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

Header Data Header Data

R

Releleeaasse e SSttaattuuss:: RReelleeaasseed d ffoor r CCususttoommeer r R

Reelleeaasseed d oonn:: 2255..0033..2200110 10 177::1199::4499 Ma

Mastster er LaLangnguauagege:: GeGerrmamann P

Prriioorriittyy:: CCoorrrreeccttiioon n wwiitth h hhiiggh h pprriioorriittyy C

Caatteeggoorryy:: IInnssttaallllaattiioon in innffoorrmmaattiioonn Primary Component:BC-OP-LNX Linux Primary Component:BC-OP-LNX Linux Affected Releases