Oracle 10gR2 64bit on SuSE11 x86_64安装技术文档(原版英文)

 

Requirements for Installing Oracle 10gR2 64-bit (AMD64/EM64T) on SLES 11 [ID 956194.1]
		修改时间 10-DEC-2010     类型 BULLETIN     状态 PUBLISHED

In this Document
  Purpose
  Scope and Application
  Requirements for Installing Oracle 10gR2 64-bit (AMD64/EM64T) on SLES 11
  References

---

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.5 - Release: 10.2 to 10.2
SUSE \ UnitedLinux x86-64

Purpose

This note explains the requirements that need to be met for a successful installation of RDBMS release 10.2.0.x (a 1 DVD set) on SLES 11, 64-bit (x86-64).

It is NOT the purpose of this NOTE to repeat every "how-to" step that is presented in the 10gR2 Installation Guide manual. For example this NOTE does not include how to create the Linux OS account named "oracle", nor does it cover how to set environment variables. Both are adequate covered in Chapter 2 "Oracle Database Preinstallation Requirements" of the 10gR2 Installation Guide manual.

You can download the 10.2.0.X from following URL. But you require a valid OTN account for download. http://www.oracle.com/technology/software/products/database/oracle10g/htdocs/10201linx8664soft.html

Scope and Application

This procedure is meant for those planning/trying to install Oracle Server 10.2.0.1.0 (or above) on SLES 11 on the 64-bit (x86-64) platform.

Requirements for Installing Oracle 10gR2 64-bit (AMD64/EM64T) on SLES 11

I. Hardware:
===========
  1. Minimum Hardware Requirements
     a.) At least 1.0 Gb (1024 MB) of physical RAM
     b.) Swap disk space proportional to the system's physical memory as follows:

          RAM                               Swap Space 
          1024 Mb to 2048 Mb      1.5 x RAM 
          2049 Mb to 8 Gb             1 x RAM
          greater than 8 Gb              0.75 x RAM

     c.) 400 Mb of disk space (and less than 2Tb of disk space) in the /tmp directory.
     d.) Between 1.5 GB and 3.5 GB of disk space for the Oracle software, depending on the installation type
     e.) 1.2 Gb of disk space for a preconfigured database that uses file system storage (optional)


II. Software:
============
  1. Oracle recommends that you install the Linux operating system with the default software packages (RPMs) and do not customize the RPMs during installation. For additional information on "default-RPMs", please see Note 386391.1, "Defining a "default RPMs" installation of the SLES OS"
     a.) Additionally, SuSE (Novell) also requires that you install the following two "SLES Patterns":
          1.) C/C++ Compiler & Tools
          2.) 32 bit compatible libraries

  2. SuSE Linux Enterprise Server (SLES) 11, which is Kernel 2.6.27.19-5 or newer.

  3. Required OS Components (per SuSE (Novell) Certification)
     a.) The exact version number details of this list are based upon 64-bit (x86_64) SLES 11 SP0. When a higher "service pack" level is used, the RPM release numbers (such as 2.6.27.19-5) may be slightly higher (such as 2.6.27.19-17 or 2.6.27.47). Since all "service pack" levels of SLES 11 are certified, this is fine so long as you are still using 64-bit Linux (x86_64) SLES 11 RPMs.
     b.) According to SuSE (Novell), the following RPMs will already be present from the foundation of Linux that is required in Section II.1 above. For your convenience, the two required "SLES Patterns" will install following required packages:
          1.) binutils-2.19-11.28 (x86_64)
          2.) gcc-4.3-62.198 (x86_64)
          3.) gcc-c++-4.3-62.198 (x86_64)
          4.) glibc-2.9-13.2 (x86_64)
          5.) libstdc++43-4.3.3_20081022-11.18 (x86_64)
          6.) libstdc++33-3.3.3-11.9 (x86_64)
          7.) libstdc++-devel-4.3-62.198 (x86_64)
          8.) make-3.81-128.20 (x86_64)
          9.) sysstat-8.1.5-7.8 (x86_64)
          10.) xscreensaver-5.07-6.31 (x86_64)
          11.) libaio-0.3.104-140.22 (x86_64)
          12.) libaio-devel-0.3.104-140.22 (x86_64)
          13.) libaio-32bit-0.3.104-140.22 (x86_64)
          14.) libaio-devel-32bit-0.3.104-140.22 (x86_64)
          15.) gcc43-32bit-4.3.3_20081022-11.18 (x86_64)
          16.) gcc-32bit-4.3-62.198 (x86_64)
          17.) glibc-32bit-2.9-13.2 (x86_64)
          18.) glibc-devel-2.9-13.2 (x86_64)
          19.) glibc-devel-32bit-2.9-13.2 (x86_64)
          20.) libgcc43-32bit-4.3.3_20081022-11.18 (x86_64)
          21.) libstdc++43-32bit-4.3.3_20081022-11.18 (x86_64)
          22.) libstdc++33-32bit-3.3.3-11.9 (x86_64)
          23.) ksh-93t (x86_64)
          24.) libstdc++43-devel-4.3.3_20081022 (x86_64)
          25.) libstdc++43-devel-32bit-4.3.3_20081022 (x86_64)
          26.) libgcc43-4.3.3_20081022 (x86_64)

     c.) The remaining Install Guide requirements will have to be installed: 
          1.) Intentionally blank

  4. Additional Required OS Components (per the runInstaller OUI)
     a.) Intentionally blank

  5. Additional Required OS Components (per this NOTE)
     a.) Please do not rush, skip, or minimize this critical step. This list is based upon a "default-RPMs" installation of 64-bit (x86_64) SLES 11. Additional RPMs (beyond anything known to Oracle) may be needed if a "less-than-default-RPMs" installation of 64-bit (x86_64) SLES 11 is performed. For more information, please refer to Note 386391.1, "Defining a "default RPMs" installation of the SLES OS"
     b.) Intentionally blank

  6. Oracle Global Customer Support has noticed a recent trend with install problems that originates from installing too many RPMs. For example:
     a.) installing your own JDK version (prior to beginning the Oracle Software “runInstaller”) is not needed on Linux, and is not recommended on Linux. A pre-existing JDK often interferes with the correct JDK that the Linux Oracle Software “runInstaller” will place and use.
     b.) installing more than the required version of the gcc / g++ RPMs often leads to accidentally using (aka enabling or activating) the incorrect one. If you have multiple RDBMS versions installed on the same Linux machine, then you will likely have to manage multiple versions of gcc /g++ . For more information, please see Note 444084.1, "Multiple gcc / g++ Versions in Linux"

  7. All of the RPMs in section II. are on the SLES 11 64-bit (x86_64) distribution media.

III. Environment:
================
  1. Modify your kernel settings in /etc/sysctl.conf as follows. If the current value for any parameter is higher than the value listed in this table, do not change the value of that parameter. Range values (such as net.ipv4.ip_local_port_range) must match exactly.
     kernel.shmall = physical RAM size / pagesize For most systems, this will be the value 2097152. See Note 301830.1 for more information.
     kernel.shmmax = 1/2 of physical RAM, but not greater than 4GB. This would be the value 2147483648 for a system with 4Gb of physical RAM.
     kernel.shmmni = 4096
     kernel.sem = 250 32000 100 128
     fs.file-max = 512 x processes (for example 65536 for 128 processes)
     net.ipv4.ip_local_port_range = 9000 65500
         @per Bug 7507772
         The runInstaller (OUI) checks may expect this to be the old guidance of “1024 65000”. The new guidance from Oracle development is “9000 65500”. Please allow the runInstaller (OUI) to proceed with the new guidance from Oracle development.
     net.core.rmem_default = 262144
     net.core.rmem_max = 262144
     net.core.wmem_default = 262144
     net.core.wmem_max = 262144
     vm.hugetlb_shm_group = <oinstall group id number> (for example 1000 if /etc/group line for oinstall is 1000)

  2. To activate these new settings into the running kernel space, run the “sysctl –p” command as root.

  3. Set Shell Limits for the oracle User. Assuming that the "oracle" Unix user will perform the installation, do the following:

     a.) Add the following settings to /etc/security/limits.conf
          oracle soft nproc 2047
          oracle hard nproc 16384
          oracle soft nofile 1024
          oracle hard nofile 65536

     b.) Add or edit the following line in the /etc/pam.d/xdm file, if it does not already exist:
          session required pam_limits.so

     c.) Add or edit the following line in the /etc/pam.d/su file, if it does not already exist:
          session required pam_limits.so

     d.) Add the following lines to /etc/profile.local:
          if [ $USER = "oracle" ]; then
               if [ $SHELL = "/bin/ksh" ]; then
                  ulimit -u 16384
                  ulimit -n 65536
               else
                  ulimit -u 16384 -n 65536
               fi
          fi


  4. The gcc and g++ RPM items above will ensure that the correct gcc / g++ versions are installed. It is also required that you ensure that these correct gcc / g++ versions are active, and in-use. Ensure that the commands "gcc --version" and "g++ --version" each return "4.3.x".

  5. The hostname command should return the fully qualified hostname as shown
below:
     % hostname --fqdn 
     hostname.domainname

  6. If any Java packages are installed on the system, unset the Java environment variables, for example JAVA_HOME.

  7. The oracle account used to install Oracle 10.2.0.1, should not have the Oracle install related variables set by default. For example setting ORACLE_HOME, PATH, LD_LIBRARY_PATH to include Oracle binaries in .profile, .login file and /etc/profile.d should be completely avoided.
     a.) Setting $ORACLE_BASE (not $ORACLE_HOME) is recommended, since it eases a few prompts in the OUI runInstaller tool.
     b.) following the successful install, it is recommended to set $ORACLE_HOME, and to set $PATH to include $ORACLE_HOME/bin at the beginning of the $PATH string.

  8. Now you are ready to invoke your Oracle Universal Installer.

     a.) it is best practice not to use any form of "su" to start the runInstaller, in order to avoid potential display-related problems.

     b.) The 10.2.0.1 OUI does not recognize SLES 11 as a valid platform. Therefore, you must invoke OUI as:
%./runInstaller -ignoreSysPrereqs

     c.) According to SuSE (Novell), during installation of 10.2.0.1 on SLES 11, a target "collector" linking error will occur. When this error is encountered during the 'linking' phase:
          1.) click continue (i.e.ignore the target "collector" linking error seen during the installation) and complete the 10.2.0.1 base-release installation. For additional information, please see NOTE 957982.1, "ERROR INVOKING TARGET 'COLLECTOR' OF MAKEFILE '$O_H/SYSMAN/LIB/INS_EMDB.MK' " 

     d.) When performing the 10.2.0.1 installation, make sure to use the "runInstaller" version that comes with 10.2.0.1 software.

     e.) When performing any subsequent 10.2.0.x patchset, make sure to use the "runInstaller" version that comes with the patchset.




ADDITIONAL NOTES
----------------
  1. Supported distributions of the 32-bit (x86) Linux OS can run on on AMD64/EM64T and Intel Processor Chips that adhere to the x86_64 architecture
     a.) Oracle 32-bit running on AMD64/EM64T with 32-bit OS is supported, but is NOT covered by this NOTE.
     b.) Oracle 32-bit running on AMD64/EM64T with 64-bit OS is not certified and is not supported.

  2. Asynchronous I/O on ext2 and ext3 file systems is supported if your scsi/fc driver supports that functionality.

  3. No extra patch is required for the DIRECTIO support for x86_64.

  4. No LD_ASSUME_KERNEL value should be used with the SLES 11 product.

References

NOTE:301830.1 - Upon startup of Linux database get ORA-27102: out of memory Linux-X86_64 Error: 28: No space left on device
NOTE:339614.1 - DBA_REGISTRY Shows Components Of A New Database Are At The Base Level, Even Though A Patchset Is Installed
NOTE:386391.1 - Defining a "default RPMs" installation of the SLES OS
NOTE:444084.1 - Multiple gcc / g++ Versions in Linux
NOTE:567506.1 - Maximum SHMMAX values for Linux x86 and x86-64
NOTE:605251.1 - Where To Locate The Oracle RDBMS Installation Guides, Upgrade Guides and Release Notes
NOTE:957982.1 - SLES 11: ERROR INVOKING TARGET 'COLLECTOR' OF MAKEFILE '$O_H/SYSMAN/LIB/INS_EMDB.MK'
PATCH:6810189 - 10.2.0.4.0 PATCH SET FOR ORACLE DATABASE SERVER