Installing Oracle 9i on RHEL5 Guide
Installing Oracle 9i on RHEL5 Guide
Installing Oracle 9i on a system with RHEL5's virtualization support enabled can lead to erratic behavior during the installation process because this module installs a different kernel (Xen). To mitigate these issues, it is advised to skip installing virtualization support during the RHEL5 installation, thereby ensuring a stable installation environment for Oracle 9i .
After Oracle 9i source files are downloaded, they should be stored in the oracle user's home directory. The files, typically in .gz format, must be unzipped using 'gunzip'. Next, the archived .cpio files must be unpacked using the 'cpio' command to extract them into readable directories. This provides access to installation directories Disk1, Disk2, and Disk3 which are required for the subsequent installation steps .
SELinux, if not disabled, can interfere with the installation process of Oracle 9i by enforcing security policies that may block necessary operations. Therefore, it is recommended to disable SELinux during or after RHEL5 installation. This can be done by setting the SELINUX flag to 'disabled' in the /etc/selinux/config file .
If DBCA fails during the Oracle 9i installation due to JRE issues, the solution involves changing the installer's JRE by running specific commands in the terminal. This involves removing the existing JRE and creating symbolic links to the correct JRE version in the ORACLE_BASE directory. After making these changes, retrying the DBCA and any failed services should allow the installation to proceed successfully .
Environment variables play a critical role in defining the Oracle runtime environment, specifying where software and associated components are located. Variables like ORACLE_BASE, ORACLE_HOME, and LD_LIBRARY_PATH ensure that the system knows where to find the Oracle binaries and libraries, while PATH enhancements ensure that relevant executables can be found and executed. Properly configuring these variables in the oracle user's .bash_profile is necessary for successful installation and operation .
Oracle installation requires specific user permissions and group associations to ensure proper access to databases and resources during its operation. The installer will not run as the root user, necessitating the creation of an 'oinstall' group, along with 'dba' and 'oper' groups for administrative purposes. An 'oracle' user should then be created, associated with these groups, to manage the Oracle environment securely .
Manual installation of specific RPM packages is crucial because Oracle 9i requires certain libraries and development tools that may not be available by default on RHEL5. If these packages are missing, they can be manually installed using commands from the RHEL5 installation media. Checking the presence of packages with rpm -q and using rpm -Uvh for installation ensures that necessary components are available for a smooth Oracle installation .
Using older versions of the Java Runtime Environment (JRE) for Oracle 9i installation on RHEL5 is necessary because newer JRE versions may exhibit compatibility issues that affect Oracle's graphical user interface and tools like the Database Configuration Assistant (DBCA). The installation instructions specify using a specific older JRE version to ensure these tools function correctly .
Symbolic links are used to direct Oracle 9i to compatible library and compiler versions that may not be present otherwise on RHEL5. For example, when specific libraries are missing or incompatible, creating symbolic links like linking libstdc++ to an older version can simulate the presence of required libraries, allowing the Oracle installation to function as expected .
The configuration of kernel parameters is crucial for Oracle 9i installation, as it ensures the Linux kernel can handle database operations efficiently. Important parameters include setting kernel.shmmni to 4096, kernel.sem to '250 32000 100 128', fs.file-max to 65536, net.ipv4.ip_local_port_range to '1024 65000', and appropriate values for net.core.rmem and wmem defaults and maximums. These parameters can be added to the /etc/sysctl.conf file and loaded using the sysctl -p command .