Oracle series: Installing the mongolerac database (1)

The installation of the OracleRAC database is more complex than that of a standalone database, because the entire installation process involves network, operating system, and storage. Improper configuration of one link may cause installation failure. This article will detail RAC

The installation of the OracleRAC database is more complex than that of a standalone database, because the entire installation process involves network, operating system, and storage. Improper configuration of one link may cause installation failure. This article will detail RAC

The installation of the Oracle RAC database is more complex than that of a standalone database, because the entire installation process involves network, operating system, and storage. Improper configuration of one link may lead to installation failure. This article describes the installation process of the RAC database in detail.

1. System Configuration Requirements before installation
Components required for installing the Oracle Rac database can be divided into two parts: hardware and software. The following is a recommended software and hardware configuration:

To facilitate the installation of the RAC database, we recommend that you select the following system package when installing the operating system:

Desktop environment: xwindows system and GNOME desktop environment.

Development tools: development tools, x software development, gnome software development, and kde software development.

For more detailed topology information, see

The Oracle Rac database involves public networks and private networks. Therefore, network division and IP address planning are required. The following table lists the IP addresses, host names, and network connection types of the RAC database to be installed:

2. Set database installation Resources
The packages required to install the RAC database are divided into three parts: the oracle RAC installation package, the Oracle ASMLib toolkit, and the system patch package. The installation version of Oracle is oracle11g. The detailed package information is as follows:
(1) Oracle 11g Release 1 (11.1.0.6.0) Software Package
:
Package Name:
Linux_11gR1_database_1013.zip
Linux_x86_11gr1_clusclusware.zip
Software Package Description: two installation programs need to be downloaded. One is the Oracle Rac installation package, and the other is the Oracle ClusterWare installation package.
(2) Oracle ASMLib Toolkit
:
Package Name:
Oracleasmlib-2.0.4-1.el5.i386.rpm
Oracleasm-2.6.18-194.11.1.el5-2.0.5-1.el5.i686.rpm
Oracleasm-support-2.1.3-1.el5.i386.rpm
Software Package Description: these three software packages are required to use the ASM storage management method.
(3) system patch package
:
Package name: redhat-release-5-1.0.el5.centos.1.i386.rpm
Software Package Description: Because Centos is not listed on the Oracle support platform, it cannot be passed during installation and detection. By installing this software package, the Hong Kong server is rented to ensure the installation and detection pass smoothly.

3. Configure host resolution files
To enable normal communication between each host, you need to modify the local resolution file on each node, that is, the/etc/hosts file. Add the following configuration information to the two nodes:

4. Check required software packages
Perform the same operation on each node:
Run the following command:
Rpm-q make binutils libaio-devel libaio elfutils-libelf-devel compat-libstdc ++-33 libgcc gcc-c ++ glibc sysstat libstdc ++-devel unixODBC- devel unixODBC
If a software package is not installed, install it.

5. Configure System Kernel Parameters
Because the Linux Kernel Parameter information is stored in the memory, you can directly modify it by using commands and the modification takes effect directly. However, after the system restarts, the original parameter values will be lost, the system automatically goes to/etc/sysctl every time it starts. the conf file reads kernel parameters. Therefore, it is a good choice to write Kernel Parameter configurations into this file.
Oracle has strict requirements on Linux Kernel Parameters. Improper configuration and website space may cause installation failure and edit/etc/sysctl. conf file. The modified parameter configuration is as follows:

The following describes the meanings of common kernel parameters:
Kernel. shmmax: indicates the maximum value of a single shared memory segment, in bytes. This value is generally half of the physical memory, but it doesn't matter if it is bigger. Here it is set to 1 GB.
Kernel. shmmni: Minimum value of a single shared memory segment, usually 4 kb, that is, 4096bit
Kernel. shmall: indicates the total amount of available shared memory. The unit is page. On the 32-bit system, the previous page equals 4 k, that is, 4096 bytes.
 Fs. file-max: Maximum number of file handles. File handle indicates the number of files that can be opened in linux.
 Net. ipv4.ip _ local_port_range: indicates the port range, which is the Hong Kong server and the specified content.
Kernel. sem: used to set the Linux semaphore.
You can use the following command to View Details:
[Root @ node-rac1 rac] # cat/proc/sys/kernel/sem
250 32000 32 128
The meanings of the four output values are described as follows:
Eclipsemmsl: this parameter is used to control the maximum number of signals in each signal set. We recommend that you set SEMMNI to not less than 100 in Oracle.
Eclipsemmns: this parameter is used to control the maximum number of signals (not signal sets) in the entire Linux system.
Eclipsemopm: this parameter is used to control the signal operands that can be executed by each semop system call. We recommend that you set the SEMOPM value to not less than 100 in Oracle.
Eclipsemmni: This Kernel Parameter is used to control the maximum number of CITIC number sets in the entire Linux system. We recommend that you set SEMMNI to not less than 100 in Oracle.

6. Set Shell restrictions on Oracle users
Perform the same operation on each node as the root user.
First, modify/etc/security/limits. conf and add the following content at the end of the file:
Oracle soft nproc 2047
Hard nproc 16384
Oracle soft nofile 1024
Oracle hard nofile 65536
Next, modify/etc/pam. d/login and add the following content at the end of the file:
Session required/lib/security/pam_limits.so
Finally, modify/etc/profile and add the following content at the end of the file:

After all the modifications are completed, restart all Linux systems.

7. Configure the hangcheck-timer kernel module
Run the command as the root user and make the following configuration on all nodes.
Check whether the module exists:
[Root @ node-rac1 ~] # Find/lib/modules-name "hangcheck-timer.ko"
Edit/etc/modprobe. conf:
[Root @ node-rac1 ~] # Vi/etc/modprobe. conf
Add a line at the end of the file:
Options hangcheck-timer hangcheck_tick = 30 hangcheck_margin = 180
Then, configure the hangcheck-timer module as self-starting:
[Root @ node-rac1 ~] # Vi/etc/rc. d/rc. local
Add a line at the end of the file:
/Sbin/modprobe hangcheck_timer
Start hangcheck:
[Root @ node-rac1 ~] #/Sbin/modprobe hangcheck_timer
Finally, check whether hangcheck is successfully started:
[Root @ node-rac1 ~] # Grep hangcheck/var/log/messages | tail-2
Aug 26 19:08:17 Mysql1 kernel: Hangcheck: starting hangcheck timer 0.9.0 (tick is 30 seconds, margin is 180 seconds ).
If the above output is displayed, hangcheck is successfully started.