Requirements for Installing Oracle 9iR2 64-bit on RHEL 4 x86-64

刺骨的言语ヽ痛彻心扉 2023-10-06 12:52 2阅读 0赞

<table> 
 <tbody> 
 <tr> 
 <td> Requirements for Installing Oracle 9iR2 64-bit on RHEL 4 x86-64 (AMD64/EM64T) (Doc ID 353529.1) </td> 
 <td> <img alt="" height="1" src="https://img-blog.csdnimg.cn/20200712110950303.png" width="1"> </td> 
 </tr> 
 </tbody> 
</table>

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

![20200712110950304.png][]

<table> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;"> In this Document 
 <table> 
 <tbody> 
 <tr> 
 <td style="width:.3pt;">&nbsp;</td> 
 <td> <a rel="nofollow">Purpose</a> </td> 
 </tr> 
 </tbody> 
 </table>&nbsp; 
 <table> 
 <tbody> 
 <tr> 
 <td style="width:.3pt;">&nbsp;</td> 
 <td> <a rel="nofollow">Scope</a> </td> 
 </tr> 
 </tbody> 
 </table>&nbsp; 
 <table> 
 <tbody> 
 <tr> 
 <td style="width:.3pt;">&nbsp;</td> 
 <td> <a rel="nofollow">Details</a> </td> 
 </tr> 
 </tbody> 
 </table>&nbsp; 
 <table> 
 <tbody> 
 <tr> 
 <td style="width:.3pt;">&nbsp;</td> 
 <td> <a rel="nofollow">References</a> </td> 
 </tr> 
 </tbody> 
 </table> 
 <div style="margin-left:0cm;"> 
 <hr> 
 </div> 
 <div> 
 APPLIES TO: 
 </div> Oracle Database - Enterprise Edition - Version 9.2.0.1 to 9.2.0.8 [Release 9.2] Linux x86-64 ***Checked for relevance on 22-JAN-2014*** 
 <div> 
 <a rel="nofollow"></a>PURPOSE 
 </div> Following requirements needs to be met for a successful installation of Oracle RDBMS Enterprise Edition version 9.2.0.x on Red Hat Enterprise Linux AS/ES 4.0 (RHEL4) on platform Linux x86_64 . It is NOT the purpose of this NOTE to repeat every "how-to" step that is presented in the 9iR2 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 9iR2 Installation Guide manual. You can download the base 9.2.0.4 from following URL. But you require a valid "edelivery" account for download. http://edelivery.oracle.com/EPD/Download/get_form?egroup_aru_number=10285079 As can be observed in the Certifications for 9iR2 on x86_64 RHEL4, Oracle RDBMS Enterprise Edition version 9.2.0.7 is the minimum required version. You will begin with a "software only" (no database) installation of 9.2.0.4, and immediately patch it to 9.2.0.7. The DBCA can then be used to create a 9.2.0.7 database. (A new or custom database will be at 9.2.0.7, a template database will be at 9.2.0.1. - reference&nbsp;<a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&amp;sourceId=353529.1&amp;id=339614.1" rel="nofollow">Note 339614.1</a>) You can download the 9.2.0.7 patchset from Metalink as&nbsp;<a href="https://support.oracle.com/epmos/faces/ui/patch/PatchDetail.jspx?parent=DOCUMENT&amp;sourceId=353529.1&amp;patchId=4163445" rel="nofollow">patch 4163445</a>.&nbsp;&nbsp; But you require a valid Metalink account for download. &nbsp; 
 <div> 
 <a rel="nofollow"></a>SCOPE 
 </div> The intended audience for this note&nbsp;is Oracle DBA's and&nbsp;customer's wanting to install Oracle 9iR2 64-bit on Red Hat Enterprise Linux 4.0 x86-64 (AMD64/EM64T).&nbsp; Since it is the expressed goal to keep Oracle Enterprise Linux functionally IDENTICAL to RHEL, this NOTE is also completely applicable to 64-bit (x86_64) OEL&nbsp;4 update 4 or greater.&nbsp; 
 <div> 
 <a rel="nofollow"></a>DETAILS 
 </div> 1. Install the required OS components selected all of the packages under the software development section.&nbsp; 
 <ul> 
 <li>This list is based upon a "default-RPMs" installation of RHEL AS/ES 4 update 1. When a newer "update" level is used, the RPM release numbers (such as 2.4-9.1.87) may be slightly higher (such as 2.4-9.1.93 or 2.4-9.2.37). This is fine so long as you are still using RHEL AS/ES 4 RPMs.</li> 
 <li>glibc-kernheaders-2.4-9.1.87.x86_64.rpm&nbsp;</li> 
 <li>glibc-headers-2.3.4-2.9.x86_64.rpm</li> 
 <li>glibc-devel-2.3.4-2.9.x86_64.rpm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;</li> 
 <li>compat-gcc-32-3.2.3-47.3.x86_64.rpm&nbsp;</li> 
 <li>compat-gcc-32-c++-3.2.3-47.3.x86_64.rpm&nbsp;</li> 
 <li>libstdc++-devel-3.4.3-22.1.x86_64.rpm&nbsp;</li> 
 <li>libaio-0.3.103-3.x86_64.rpm</li> 
 <li>Please do not rush, skip, or minimize this critical step.&nbsp; This list is based upon a "default-RPMs" installation of RHEL AS/ES 4. Additional RPMs (beyond anything known to Oracle) may be needed if a "less-than-default-RPMs" installation of RHEL AS/ES 4 is performed. For additional information on "default-RPMs", please see&nbsp;<a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&amp;sourceId=353529.1&amp;id=376183.1" rel="nofollow">Note 376183.1</a>, "Defining a "default RPMs" installation of the RHEL OS"</li> 
 </ul>The x86-64 packages are on the Red Hat Enterprise Linux 4 x86-64 distribution.&nbsp; The i386 packages are also on the Red Hat Enterprise Linux 4 x86-64 distribution. The command syntax to differentiate between installed i386 RPMs and installed x86-64 RPMs is presented in the last item of the "Additional Notes" section below. &nbsp; NOTE:&nbsp; i386 packages might require the --force option during installation if the 64-bit version of the same package is already installed.&nbsp; For example, "rpm -ivh --force glibc-devel-2.3.4-2.9.i386.rpm" may be required.&nbsp;&nbsp; 2. Configure the Unix environment&nbsp; The first&nbsp;critical&nbsp;environment item is related to the gcc v3.2 and g++ v3.2 RPMs that were installed above. Run these commands: &nbsp;&nbsp;&nbsp; mv /usr/bin/gcc /usr/bin/gcc.orig &nbsp;&nbsp;&nbsp; mv /usr/bin/g++ /usr/bin/g++.orig &nbsp;&nbsp;&nbsp; ln -s /usr/bin/x86_64-redhat-linux-gcc32 /usr/bin/gcc &nbsp;&nbsp;&nbsp; ln -s /usr/bin/x86_64-redhat-linux-g++32 /usr/bin/g++ If the "mv" (move) command lines above return an error, it only means that your system did not have a pre-existing /usr/bin/gcc or /usr/bin/g++ to rename. Next, the following environment settings are required for the Unix user performing the installation (eg. oracle) : &nbsp;&nbsp;&nbsp; %&nbsp;umask &nbsp;&nbsp;&nbsp;&nbsp;0022&nbsp; &nbsp;&nbsp;&nbsp; %&nbsp;echo $LD_ASSUME_KERNEL &nbsp;&nbsp;&nbsp;&nbsp;2.4.19&nbsp; - Modify your kernel settings in /etc/sysctl.conf (RedHat) as follows: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; kernel.shmall = physical RAM size / pagesize For most systems, this will be the value 2097152. See&nbsp;<a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&amp;sourceId=353529.1&amp;id=301830.1" rel="nofollow">Note 301830.1</a>&nbsp;for more information. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; kernel.shmmax = 1/2 of physical RAM.&nbsp; This would be the value 2147483648 for a system with 4Gb of physical RAM. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; kernel.shmmni = 4096 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; kernel.sem = 250 32000 100 128 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; fs.file-max = 512 x processes (for example 327680 for 640 processes) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; net.ipv4.ip_local_port_range = 9000 65500 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; @per Bug 7507772 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 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. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; kernel.hostname = yourhost.yourdomain.com #&lt;--- full qualified hostname !! &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; kernel.domainname = yourdomain #&lt;--- correct domain name !! &nbsp; Then run "sysctl -p" to activate these new settings Next, the "hostname" command should return the fully qualified hostname as shown&nbsp;below: &nbsp;&nbsp;&nbsp; % hostname &nbsp;&nbsp;&nbsp; hostname.domainname&nbsp; Next, if any Java packages are installed on the system, unset&nbsp;any Java&nbsp;environment variables (for example&nbsp; JAVA_HOME) The Unix user performing the installation (eg. oracle) should&nbsp;not&nbsp;have&nbsp;the Oracle install related variables&nbsp;set by default. For example setting ORACLE_HOME, PATH, LD_LIBRARY_PATH to include&nbsp;Oracle&nbsp; binaries in .profile, .bash_profile, .login file and /etc/profile.d should&nbsp;be completely avoided. 3.&nbsp;Configure the Unix user process and file limits Assuming that the "oracle" Unix user will perform the installation, do the following: &nbsp; &nbsp; -&nbsp;Add the following settings to /etc/security/limits.conf &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; oracle&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; soft&nbsp;&nbsp;&nbsp; nproc&nbsp;&nbsp; 2047 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; oracle&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hard&nbsp;&nbsp;&nbsp; nproc&nbsp;&nbsp; 16384 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; oracle&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; soft&nbsp;&nbsp;&nbsp; nofile&nbsp; 1024 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; oracle&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hard&nbsp;&nbsp;&nbsp; nofile&nbsp; 65536 &nbsp;&nbsp;&nbsp; - Add or edit the following line in the /etc/pam.d/login file, if it does not already exist: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; session&nbsp;&nbsp;&nbsp; &nbsp;required&nbsp;&nbsp;&nbsp; &nbsp;pam_limits.so&nbsp; &nbsp;&nbsp;&nbsp; - Add the following lines to /etc/profile: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if [ $USER = "oracle" ]; then &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if [ $SHELL = "/bin/ksh" ]; then &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ulimit -p 16384 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ulimit -n 65536 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; else &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ulimit -u 16384 -n 65536 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; fi &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; fi 4.&nbsp;&nbsp;Install 9iR2 using the&nbsp;Oracle Universal Installer (OUI) When performing the 9.2.0.4 "software only" installation, make sure to use the "runInstaller" version that comes with 9.2.0.4 software (OUI 2.2.0.18) When performing the&nbsp;9.2.0.7 installation, make sure&nbsp;to use the "runInstaller" version that comes with 9.2.0.7&nbsp;(OUI 10.1.0.4)&nbsp; ADDITIONAL NOTES 1. Linux x86-64, support on AMD64/EM64T and Intel Processor Chips that adhere to the x86-64 architecture with supported Linux releases: &nbsp;&nbsp;&nbsp; -- Oracle 32-bit running on AMD64/EM64T with 32-bit OS is supported. &nbsp;&nbsp;&nbsp; -- Oracle 32-bit running on AMD64/EM64T with 64-bit OS is&nbsp;not&nbsp;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. The following "rpm" command can be used to distinguish between a 32-bit or 64-bit package: &nbsp;&nbsp;&nbsp; # rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" | grep &lt;RPM_name&gt; For example: &nbsp;&nbsp;&nbsp; # rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" | grep glibc-devel &nbsp;&nbsp;&nbsp; glibc-devel-2.3.4-2.13 (i386) 
 <div> 
 <a rel="nofollow"></a>REFERENCES 
 </div> <a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&amp;sourceId=353529.1&amp;id=301830.1" rel="nofollow">NOTE:301830.1</a>&nbsp;- Upon startup of Linux database get ORA-27102: out of memory Linux-X86_64 Error: 28: No space left on device <a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&amp;sourceId=353529.1&amp;id=339614.1" rel="nofollow">NOTE:339614.1</a>&nbsp;- DBA_REGISTRY Shows Components Of A New Database Are At The Base Level, Even Though A Patchset Is Installed <a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&amp;sourceId=353529.1&amp;id=376183.1" rel="nofollow">NOTE:376183.1</a>&nbsp;- Defining a "default RPMs" installation of the RHEL OS <a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&amp;sourceId=353529.1&amp;id=567506.1" rel="nofollow">NOTE:567506.1</a>&nbsp;- Maximum SHMMAX values for Linux x86 and x86-64 </td> 
 </tr> 
 </tbody> 
</table>

[20200712110950304.png]: https://img-blog.csdnimg.cn/20200712110950304.png