SAP Note

April 21, 2018 | Author: Adeniran Olusanya Olumide | Category: Linux, Operating System, 64 Bit Computing, Linux Distribution, Red Hat
Share Embed Donate


Short Description

Download SAP Note...

Description

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 S AP 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 6 4 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 S TD 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 d ifferently 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), 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), 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: 0 client 0 initializing .... InitFreeList  block size is 4096 kByte. Using implementation std EsStdUnamFileMapInit: shmget() of 10737418240 bytes failed. errno = 28(No space left on device) EsStdInit: unable to allocate 10240 MB EsStdInit: try to allocate 8192 MB EsStdUnamFileMapInit: 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 MB EsStdInit: try to allocate 4 MB *** ERROR => EsStdInit: unable to allocate 10240 MB [esuxi.c 401] *** Error 11 while initializing OS dependent part. *** ERROR => DpEmInit: DpEmInit: EmInit (1) [dpxxdisp.c 9559] *** ERROR => DpMemInit: 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 2005 A A ---PXA--------------------PXA----------------------------------------------------------------A PXA INITIALIZATION A System page size: 4kb, admin_size: 31788kb. I *** ERROR => shmget(11906,1126400000,2016) shmget(11906,1126400000,2016) (22: Invalid argument) [shmux.c [shmux.c 1904] A RABAX in run level 1 A RABAX in unkown environment: task_type=0, 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: 0 X 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: 0 X client 0 initializing .... X Using implementation std ...

Header Data

Rele elease Status: Released for Cust ustomer  Released on: 12.11.2009 08 08:20:42 Mast Master er Lang Langua uage ge:: Ger German man Priority: Recommendations/additional in info Category: Consulting Primary Component:BC-OP-LNX Linux Affected Releases

Software Component KRNL64NUC KRNL64NUC KRNL64UC KRNL64UC KRNL64UC

Release

6 .4 0 7 .0 0 6 .40 7 .00 7 .10

From Release 6.40 7.00 6.40 7.00 7.10

To Release 6.40 7.00 6.40 7.00 7.10

And subsequent

X X X X 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 Reason and Prerequisites

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 hardware III/.. Other Linux environments that are supported. IV/... Special notes about installing the operating system

V/ .... General notes about installing the operating system VI/ ... SAP software: saplocales VII/ .. SAP software: NPTL VIII/ . SAP software: Additional comments: IX/ .., Notes that are specific to the database X/ .... Notes about IBM Power  XI/ ... Mounting installation CDs and installation DVDs XII/ .. Adding Linux application servers to existing SAP systems XIII/ . Using virtualization technologies XIV/ .. 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

o

o

o



SUSE Linux Enterprise Server 11 for AMD64 & Intel EM64T (SLES11x86_64) SUSE Linux Enterprise Server 11 for IBM Power (SLES11-PPC) 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) SUSE Linux Enterprise Server 11 for Intel Itanium2 Proc. Family (SLES11-IPF)

SUSE Linux Enterprise Server 10 o

o

o

o

SUSE Linux Enterprise Server 10 for AMD64 & Intel EM64T (SLES10x86_64) SUSE Linux Enterprise Server 10 for IBM Power (SLES10-PPC) 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) SUSE Linux Enterprise Server 10 for Intel Itanium2 Proc. Family (SLES10-IPF)



SUSE Linux Enterprise Server 9 o

o

o

o



o

SUSE Linux Enterprise Server 9 for Intel Itanium2 Proc. Family (SLES9IPF)

SUSE Linux Enterprise Server 8 for zSeries (SLES8-ZS, see Note 81737 for information about supported Linux kernels, glibc versions and required packages) SUSE Linux Enterprise Server 8 for Intel Itanium2 Proc. Family (SLES8-IPF, for release information, see Note 623653 )

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) 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)

Red Hat Enterprise Linux 4 o



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

Red Hat Enterprise Linux 5

o



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

SUSE Linux Enterprise Server 8 o



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

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)

o

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

Red Hat Enterprise Linux 3

o

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

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 171 356 (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: Installation Prior 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: Installation Prior to the installation, refer to the note corresponding to your SUSE version from the following list: 1310037 (SUSE Linux Enterprise Server 11: 1 1: Installation notes) 958253 (SUSE Linux Enterprise Server 10: 1 0: Installation notes) 797084 (SUSE Linux Enterprise Server 9: 9 : Installation notes) 767814 (SUSE Linux Enterprise Server 8: 8 : Installation notes) o

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. 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.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 space While 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. •



Hostname The "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). Distributionspecific tools are available to change the host name. Updating RPM packages The distributors (Novell SUSE and Red Hat) regularly provide u pdates 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 S AP 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, RP M, 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) saplocales-2.3.2-6 # adjusted SAP code pages (see saplocales_rhel30_i386_version-6.zip, attached to this note) 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 saplocales-2.3.4-4 # adjusted SAP code pages (see saplocales_rhel40_i386_version-4.zip, attached to this note) 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) 20) SUSE Linux Enterprise Server 9 for Intel Itanium2 Proc. Family 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) 25) SUSE Linux Enterprise Server 10 for Intel Itanium2 Proc. Family 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 pac kages 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 and SUSE Linux Enterprise Server 9) are based b ased 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 w ith NPTL if, for example, the call of "disk+work" ends with a "Floating Point Exception".) 2) SAPINST 3) 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 v alue lower than 2.4.21. This applies to the following SAP software: •

SAP kernel as of Version 7.00 As of Version 7.0, the SAP kernel ke rnel 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 9 If you want to use the SAP-Kernel S AP-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 required If 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

o



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

DB2 UDB V9 o

o

SLES 9 Service Package 2 or higher - IBM XL C/C++ Advanced Editions V8.0 for the Linux runtime environment component 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 required Additional 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 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 RH EL4 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.0  b) xlsmp.rte-1.5.0 c) vacpp.rte-7.0.0 The v7.0.1 runtime component is compatible with the following operating systems supported by SAP. o

o

Red Hat Enterprise Linux 4 Update 2 (RHEL4 U2) or higher 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: a) vacpp.rte-7.0.1-1   b) xlsmp.msg.rte-1.5.1-1 c) xlsmp.rte-1.5.1-1

(or a more recent version) (or a more recent version) (or a more recent version)

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

o

Red Hat Enterprise Linux 4.0 Update 2 (RHEL4 U2) or higher for IBM POWER  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 appea r 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. 5310 69. This measure alone does not involve any additional license costs. The "Windows central instance with Linux application ap plication 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 bo th 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 nonUnicode 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, sequen ce, 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

Rele elease Status: Released for Cust ustomer  Released on: 25.03.2010 17 17:19:49 Mast Master er Lang Langua uage ge:: Ger German man Priority: Correction with high priority Category: Installation in information Primary Component:BC-OP-LNX Linux Affected Releases

Software Component SAP_APPL SAP_APPL SAP_APPL SAP_APPL SAP_APPL SAP_APPL SAP_APPL SAP_APPL SAP_APPL SAP_APPL SAP_BASIS SAP_BASIS SAP_BASIS SAP_BASIS SAP_ABA SAP_ABA SAP_ABA SAP_ABA SAP_ABA SAP_ABA SAP_ABA SAP_ABA SAP_ABA

Release

40 45 46 C 47 0 50 0 60 0 60 2 60 3 60 4 60 5 46 60 70 71 50 A 62 0 64 0 70 0 71 0 71 1 70 1 70 2 72 0

From Release 40B 45B 46C 4 70 5 00 6 00 6 02 6 03 6 04 6 05 46B 6 10 7 00 7 10 50A 6 20 6 40 7 00 7 10 7 11 7 01 7 02 7 20

To Release 40B 45B 46C 470 500 600 602 603 604 605 46D 64 0 70 2 72 0 50A 6 20 6 40 7 00 7 10 7 11 7 01 7 02 7 20

And subsequent

 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 Reason and Prerequisites

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 achitectures SLES10-SP2: glibc-2.4-31.54 , all architectures RHEL3 and earlier versions of glibc in RHEL4 and RHEL5 series are 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 Reason and Prerequisites

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

This document deals with the installation and configuration of SAP server software on Red Hat Enterprise Linux 5 and a nd 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 o therwise. 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. w ell. 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 n otes on certified hardware which are listed in note no te 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

o

o

i686 on Intel 32bit and compatible or AMD64 or Intel EM64T when used in 32bit mode x86_64 on AMD64 or Intel EM64T  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 x8 6_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 Ha t Network via the officially supported ways (directly or via RHN Proxy or RHN Satellite): o

For installing individual packages: yum install [ [ [...]]]

where are the names of the packages to be installed, e.g.: yum install libXp o

For installing package groups: yum groupinstall '' ['' [' Download --> Support Packages and Patches --> Entry by Application Group --> SAP NetWeaver --> SAP Netweaver components (< SAP NW 04) --> SAP WEB AS --> SAP WEB AS 6.20 --> SAP WEB AS ABAP --> SAP KERNEL 6.20 -BIT --> < OS > --> Database independent --> SAPINST6201 --> SAPPROD6201  Note that there exists no special unicode version of SAPinst. The non-unicode version is used for the installation of unicode and non-unicode systems. 2. Back up the installation directory. 3. Unpack the SAP archives you have downloaded from the SAP ServiceMarketplace into the installation directory and start sapinst from there. Procedure for SAPinst version 622: 1. Download the required patch from SAP Service Marketplace (SMP) at http://service.sap.com/swdc --> Download --> Support Packages and Patches --> Entry by Application Group --> SAP NetWeaver --> SAP Netweaver components (< SAP NW 04) --> SAP WEB AS --> SAP WEB AS 6.20 --> SAP WEB AS ABAP --> Kernel 6.20 -BIT --> < OS > --> Database independent --> SAPINST6202  Note that there exists no special unicode version of SAPinst. The non-unicode version is used for the installation of unicode and non-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: /sapinst -extract 6. Start ./sapinst If you have downloaded the patch before starting the installation you have to call ./sapinst /control.xml instead. Procedure for SAPinst version 641: 1. Download the required patch from SAP Service Marketplace (SMP) at http://service.sap.com/swdc --> Download --> Support Packages and Patches --> Entry by Application Group --> Additional Components --> SAP Kernel --> SAP Kernel -BIT -->

SAP KERNEL 640 -BIT --> < OS > --> #Database independent independen t --> SAPINST6401  Note that there exists no special unicode version of SAPinst. The non-unicode version is used for the installation of unicode and non-unicode systems. 2. Back up the installation directory if you have already started the installation. In this case the installation directory contains the files control.xml, keydb.xml, sapinst.log etc.. If you have not yet started the installation create a new installation directory. 3. Extract the downloaded archive to a temporary directory. 4. Change to the installation directory. 5. Enter the command: /sapinst -extract 6. From within the installation directory start ./sapinst If you have downloaded the patch before starting the installation you have to call ./sapinst /product.catalog instead. Header Data

Rele elease Status: Released for Cust ustomer  Released on: 12.05.2006 11 11:21:21 Mast Master er Lang Langua uage ge:: En Engl glis ish h Priority: Correction with medium priority Category: Program error   Primary Component:BC-INS-UNX Installation Unix  Note 933778 - SAP ERP 2004 SR1 Installation on RedFlag Linux Summary Symptom

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

ERP04 SR1, RedFlag

Reason and Prerequisites

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  __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/instguides SAP Patches http://service.sap.com/patches =============================================================== ========



2. OS Dependencies o

Certified OS release:

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

I386

* 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 ag ain 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.log Running "R3trans -d" as 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/ and symbol-link specific ones from $ORACLE_HOME//lib; For a distributed system, please copy or mount all stuff under /oracle/client/ 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 Prerequisites 1. Prerequisites for installing Oracle 10.2 on Linux on POWER  2. Required patch sets and patches for Oracle 10.2 3. When you install Oracle 10.2 on o n Linux on POWER, the following error occurs: Error in invoking target 'client_sharedlib' of makefile '/oracle//102_64/network/lib/ins_net_client.mk'. The log file /oracle/oraInventory/logs/installActions.log contains the error message: INFO: ./../../../powerpc-suse-linux/bin/ld: cannot find -lxl 4. The following error occurs when you install patch 4460775 or 4864648: OUI-67020 [...] Platform not compatible 5. 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//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 failed 7. 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//102_64/network/lib/ins_net_server.mk'" '/oracle//102_64/network/lib/ins_net_server.m k'" and/or "Error in invoking target 'racg_install' of makefile '/oracle//102_64/racg/lib/ins_has.mk'". The installation log under /oracle/oraInventory contains the error message "undefined reference to `[email protected]_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 be corrected with Red Hat Enterprise Linux 5 (RHEL5). For point 6): This is an error in the "libaio" package pac kage 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 con tinue with the installation. After you install the patch set, use the workaround described in Note 1404424. Header Data

Release Status: Released for Customer   Released on: 18.11.2009 11 11:26:15 Master Language: German Priority: Recommendations/additional info Category: Installation in information Primar Primary y Comp Compone onent: nt: BC-OPBC-OP-PLN PLNX X Linu Linux x on IBM PowerP PowerPC C Hard Hardwar waree Secondary Components:BC-DB-ORA-INS Installation SAP System with Oracle

View more...

Comments

Copyright ©2017 KUPDF Inc.
SUPPORT KUPDF