SAP OSS Notes: Note 1. Symptom. You want to use SAP software on SUSE LINUX Enterprise Server 1.

Other terms. SUSE, SLES, Enterprise Server, suse, Su. SE, Novell, novell, LINUX, linux, as/4. Series, p. Series, Power, Power. PC, power, ppc, s. All SAP hardware and software certifications for SLES 1. SLES for SAP 1. 1.

If you plan to install and run SAP kernels with version 7. Details about hardware platforms can be found in a section below. Requirements for support. To receive full support for your SAP system, the following requirements must be met (this list is not exclusive): To ensure support for problems that may occur with the operating system a valid support contract for SUSE LINUX Enterprise Server is required.

A support contract can be made directly with Novell or with a support partner who is authorized to redirect possible level 3 support queries to Novell. For the ppc (Linux on IBM Power Servers) platform a minium kernel version is required.

Please read the aproporiate section below. Naming convention for SLES 1.

If you intend to install Oracle and SAP on the same system, please, do not install the "Oracle Server Base" pattern (i.e. Provisioning Oracle Data Integrator (ODI) 12.1.3 on Oracle Java Cloud Service (JCS) Virtual Image. This document explains the step by step process of installing Oracle 11g R1 (11.1.0.6) Clusterware Software. Linux (pronounced /

In this SAP note we use the following abbreviations for SUSE LINUX Enterprise Server and the service packs: SLES 1. GA: SUSE Linux Enterprise Server 1. SLES 1. 1 SP1: SUSE Linux Enterprise Server 1. Service Pack 1. SLES 1. SUSE Linux Enterprise Server 1. SLES for SAP 1. 1: SUSE Linux Enterprise Server for SAP applications 1.

Install Oracle Database 11g R2 on Linux using Oracle ASM - (OL5) by Jeff Hunter, Sr. Database Administrator Contents. Introduction; Example Configuration.

Immediate access to all HP Exams and 1800+ other exam PDFs. This is the BEST deal at only $149.00 for unlimited access. Pass FAST with actual answers to actual. 4.1.2 Completing a Default Linux Installation. If you do not install the Oracle Preinstallation RPM, then Oracle recommends that you install your Linux operating. Provides a recent Linux kernel along with a set of system commands and libraries suitable for the embedded environment. Makes available system components such as X11.

Service Pack 1. Life cycle of SUSE LINUX Enterprise Server 1. SLES 1. 1)An overview of the various life cycles for the SUSE LINUX Enterprise Server product line can be found in SAP note 9. Service Packs for SUSE LINUX Enterprise Server 1. SLES 1. 1)Updates for SLES 1.

Service Packs (SP). When you import a Service Pack, many RPM packages are updated to a new version. For SLES 1. 1 you may use all Service Packs officially released by Novell. It is highly recommended to install the most current Service Pack.

Also, kindly notice that after the release of a new Service Pack, older versions of packages that are updated with this Service Pack, are considered obsolete. If you have an issue with a package, for which a newer version is available in a service pack, you might be requested to update to the new package version in order to be fully supported with your issues. The most current Service Pack for SLES 1. Service Pack 1 (also known as SLES 1.

SP1). Installing SUSE LINUX Enterprise Server 1. SLES 1. 1 (all versions)Install SLES 1. The documentation is also electronically available in a number of languages and can be found on the first SLES 1. See SAP note 1. 17.

This is described in section . This ensures the installation of the . Doing so, will prevent . This media is available at:           http: //download.

Select the . You will need a Novell account to proceed with the download. Note the following additional installation instructions (all platforms): Manually adjust the hard disk partitioning to the requirements of the SAP components. Usually, SAP components and any database components are installed on separate partitions. During network configuration do not set the option . Otherwise an additional entry in /etc/hosts will be created: 1.

This leads to errors in the hostname resolution later. If existing you need to remove this entry manually. If you configure the network settings manually, please make sure to include dns, gateway and routing. The . This can easily be done using . This automatically synchronizes the date and time of all SAP application servers.

For typical use types the recommended size of the swap is 2. GB for systems with main memory sizes greater or equal than 1. GB. Systems with less than 1. GB should have a swap partition size double that of the main memory (2 x RAM). When using ZLM you can even define software bundles and patch lists as snap shots of the online updates.

This allows to re- install a system with exactly same software versions (i. SMT is a proxy server for SLES updates and patches.

SMT is available on the Novell web site. SLES 1. 1 SP1: Configure uuidd -  The uuidd will be automatically activated when installing the sapconf package. Activated means, that the deamon is allowed to start when a time based uuid request comes in. You can check that by running the command.

After running that command the . Super Utilities Pro 9 9 3 Rustic Panel there. If you do not want to install the sapconf package, you will need to do the following steps: Modify your local permissions setting by adding the following line to your /etc/permissions. For more details please also read the man page of uuidd.

The direcory and files for pidfile and socketpath needs also to be owned by user and group uuidd. SLES 1. 1 GA: Configure uuidd -  Configure the system service uuidd to be started at boot time and also activate that service before you install SAP using the following commands: Modify your local permissions setting by adding the following line to your /etc/permissions. Enable the service uuidd either in Ya.

ST or with                    insserv uuidd                    /etc/init. For more details please also read the README file /usr/share/doc/packages/uuid- runtime/README. SUSE. uuid on your installed system. Activate sysstat (service boot. System Activity a. Rchiver (sar). You can activate sysstat either by using Ya. ST or command line.

If you have installed a current version of sapconf, the service sysstat should be automatically activated. Follow the instructions below to  check, if sysstat is activated, if you are not sure. The program sar is sampling system activity data. This makes it more easy to analyse system performance problems.

The service is intended to run during normal production. Checking, if sysstat is activated for system boot. The command should either output .

This command should either output . Select boot. sysstat. Select start now and also start during boot (runlevel B must be have an active checkmark). Activate sysstat using command line (the first command activates the service boot.

Furthermore updates of the nfs- server ( > = 1. The updates can be obtained either via download.

SUSE update mechanisms. For the duration of the SAP installation, the nscd daemon has to be stopped, i. During the installation, the boot loader configuration files are automatically adjusted to use the new kernel version. An additional entry in the boot loader configuration is available for booting the previous installed version of the kernel. This boot loader uses the configuration file .

Be aware, though, that you in this case you will not be able to fall back to the previously working kernel. GLIBC and . The update is not needed with SLES 1. SP1 anymore. These packages are currently not destributed via the online update channels.):           https: //you. ARCH> /update/SUSE- SLES/1. PTF/< FIX>                    Where < ARCH> is the system architecture of your system (x. These are provided by the sap- locale rpm package. For more information about sapconf or sapinit please refer to SAP note: 1.

Upgrading from SUSE LINUX Enterprise Server 1. SLES 1. 0)Customers who previously used SLES 1. Service Pack can use Ya.

ST to upgrade their system directly to SLES 1. Known issues regarding the upgrade from SLES 1. SLES 1. 1 are documented in the current release notes available at: http: //www. Using raw devices, Journaling File System, and LVMThe SAP note 4. Journaling File Systems. A detailed discussion about file systems and their usage is available at: http: //wiki.

File. Please consult the database vendors supportability and certification pages for more information. Note that the Linux kernels used in SLES 1.

SLES 1. 0 systems implement the so called LVM2 (LVM Version 2) format. The LVM2 format is recommended.

However, this format is incompatible with the previous LVM (LVM1 == LVM version 1) format, but SLES 1. This incompability means that LVM volumes can be upgraded to LVM2, but not back. It also means that when upgrading from an installation, where LVM1 partitions are in use, the old LVM1 format will still be used under SLES 1. Kindly refer to the . This guide is available at: http: //www. Recommended SAP kernel versions, NPTL and Linux.

It includes information about the following: 1 Reviewing Information About This Guide. This guide describes how to install Oracle Database by using the default installation options.

Tasks Described in This Guide. The procedures in this guide describe how to: Configure your system to support Oracle Database. Install Oracle Database on a local file system by using the Typical Installation option.

Configure a general- purpose Oracle Database installation that uses the local file system for database file storage. Results of a Successful Installation. After you successfully install Oracle Database: The database that you created and the default Oracle Net listener process run on the system. Oracle Enterprise Manager Database Control run on the system and can be accessed by using a web browser.

Tasks Not Described in This Guide. This guide covers the Typical Installation scenario and does not describe how to complete the following tasks: Using the Advanced Installation option to install the software. Installing the software on a system that has an existing Oracle software installation. Installing Oracle Clusterware and Oracle Real Application Clusters on a cluster.

Enabling Enterprise Manager e- mail notifications or automated backups. Enabling core file creation.

Verifying UDP and TCP kernel parameters. Using alternative storage options such as Oracle Automatic Storage Management.

Installing and configuring Oracle Grid Infrastructure. Where to Get Additional Installation Information.

For more information about installing Oracle Database, including information about the tasks not described in this guide, refer to one of the following guides: All these guides are available on the product disc. To access them, use a web browser to open the welcome. Platform- specific documentation is available in PDF and HTML formats in the Documentation section. Logging In to the System as root. Before you install the Oracle software, you must complete several tasks as the root user. To log in as the root user, complete one of the following procedures: Note.

You must install the software from an X Window System workstation, an X terminal, or a PC or other system with X server software installed. Following are the steps for installing the software from an X Window System workstation or X terminal: Start a local terminal session, for example, an X terminal (xterm). If you are not installing the software on the local system, then enter the following command to enable the remote host to display X applications on the local X server. Depending on the X server software that you are using, you may have to complete the tasks in a different order.

Start the X server software. Configure the security settings of the X server software to permit remote hosts to display X applications on the local system. Connect to the remote system where you want to install the software and start a terminal session on that system, for example, an X terminal (xterm). If you are not logged in as the root user on the remote system, then enter the following command to switch user to root. Checking the Hardware Requirements. The system must meet the following minimum hardware requirements: 3. Memory Requirements.

The following are the memory requirements for installing Oracle Database 1. Release 2 (1. 1. 2): Minimum: 1 GB of RAMRecommended: 2 GB of RAM or more. To determine the RAM size, enter the following command. Mem. Total /proc/meminfo. If the size of the RAM is less than the required size, then you must install more memory before continuing. The following table describes the relationship between installed RAM and the configured swap space recommendation: Note.

On Linux, the Huge. Pages feature allocates non- swappable memory for large page tables using memory- mapped files. If you enable Huge. Pages, then you should deduct the memory allocated to Huge. Pages from the available RAM before calculating swap space. Available RAMSwap Space Required. Between 1 GB and 2 GB1.

RAMBetween 2 GB and 1. GBEqual to the size of the RAMMore than 1. GB1. 6 GBTo determine whether the system architecture can run the software, enter the following command. This command displays the processor type. Verify that the processor architecture matches the Oracle software release to install.

If you do not see the expected output, then you cannot install the software on this system. To determine the size of the configured swap space, enter the following command. Swap. Total /proc/meminfo. If necessary, refer to the operating system documentation for information about how to configure additional swap space. To determine the available RAM and swap space, enter the following command. Note: Oracle recommends that you take multiple values for the available RAM and swap space before finalizing a value. This is because the available RAM and swap space keep changing depending on the user interactions with the computer.

Contact your operating system vendor for swap space allocation guidance for your server. The vendor guidelines supersede the swap space requirements listed in this guide. Automatic Memory Management. Starting with Oracle Database 1.

Automatic Memory Management feature requires more shared memory (/dev/shm)and file descriptors. The shared memory should be sized to be at least the greater of MEMORY. Verify that the processor architecture matches the Oracle software release to install.

If you do not see the expected output, then you cannot install the software on this system. Disk Space Requirements. The following are the disk space requirements for installing Oracle Database 1. Release 2 (1. 1. 2): At least 1 GB of disk space in the /tmp directory. To determine the amount of disk space available in the /tmp directory, enter the following command. If there is less than 1 GB of free disk space available in the /tmp directory, then complete one of the following steps: Delete unnecessary files from the /tmp directory to meet the disk space requirement. Set the TMP and TMPDIR environment variables when setting the oracle user's environment.

Extend the file system that contains the /tmp directory. If necessary, contact the system administrator for information about extending file systems. To determine the amount of free disk space on the system, enter the following command. The following tables describe the disk space requirements for software files, and data files for each installation type on Linux x. Installation Type. Requirement for Software Files (GB)Enterprise Edition. Standard Edition.

Installation Type. Requirement for Data Files (GB)Enterprise Edition. Standard Edition. Additional disk space, either on a file system or on an Oracle Automatic Storage Management disk group is required for the fast recovery area if you choose to configure automated backups. Checking the Software Requirements.

Depending on the products that you intend to install, verify that the following softwares are installed on the system. Note. Oracle Universal Installer performs checks on the system to verify that it meets the listed requirements. To ensure that these checks pass, verify the requirements before you start Oracle Universal Installer.

Note. The platform- specific hardware and software requirements included in this guide were current when this guide was published. However, because new platforms and operating system software versions might be certified after this guide is published, review the certification matrix on the My Oracle Support website for the most up- to- date list of certified hardware platforms and operating system versions.

Operating System Requirements. The following or later versions of the operating system are required for Oracle Database 1. Release 2 (1. 1. 2): Note: Starting with Oracle Database 1. Release 2 (1. 1. 2. Oracle Linux 7 and Red Hat Enterprise Linux 7 are supported on Linux x. Starting with Oracle Database 1.

Release 2 (1. 1. 2. Oracle Linux 6 and Red Hat Enterprise Linux 6 are supported on Linux x. Linux x. 86- 6. 4. Starting with Oracle Database 1. Release 2 (1. 1. 2. Asianux 4 is supported on Linux x.