Oracle RAC 11g R1安装指南 for Linux

需积分: 1 75 浏览量更新于2024-07-23 收藏 10.53MB PDF 举报

"RACGuides-Linux 是一份关于在Linux环境下安装Oracle Real Application Clusters (RAC) 11g Release 1 (11gR1) 的指南。这份文档详细介绍了安装前的准备、硬件与软件配置、安装步骤以及用户账户的设置等关键环节。" 在Oracle RAC 11gR1 on Linux的部署中，有几个核心知识点需要理解： 1. **所需知识**：在开始安装之前，你需要了解必要的软件需求，包括对32位和64位RPM包的要求。32位和64位的RPM包列表分别列出了安装所需的软件组件，确保操作系统与软件版本的兼容性。 - **32-Bit Required RPM's** 包括了适用于32位系统的必要软件包。 - **64-Bit Required RPM's** 提供了64位系统下的必需组件。 2. **处理器模型**：选择合适的处理器模型对于Oracle RAC的性能至关重要，因为不同的处理器架构可能影响到Oracle Clusterware和数据库的运行效率。 3. **安装步骤**：安装过程分为多个阶段，包括预安装配置、软件安装、后安装配置等，每个步骤都需要仔细操作以确保集群的稳定性和可靠性。 4. **硬件/软件配置**：在安装Oracle软件前后，硬件和软件配置会有所不同。在安装前，需要设定好硬件环境和基础软件，如操作系统、网络等；安装后，Oracle软件将与这些组件集成，形成完整的RAC环境。 5. **安装方法**：指南可能会提到多种安装方法，选择适合你情况的最佳实践，这可能包括图形化界面安装、命令行安装或者自动化脚本安装等。 6. **集群节点准备**：在安装RAC之前，需要对所有集群节点进行预处理，这涉及创建和配置多个操作系统用户组，如OSDBA、OSOPER、OSASM和OINSTALL。 - **OSDBA (DBA) Group** 是Oracle数据库管理员组，用于管理数据库权限。 - **OSOPER Group**（可选）是操作系统操作员组，允许执行某些操作级别的任务。 - **OSASM Group** 用于管理Automatic Storage Management (ASM)。 - **OINSTALL Group** 用于安装Oracle软件的所有用户。 7. **Oracle软件所有者用户**：需要确定是否已存在Oracle软件所有者用户，如果没有，则需创建；如果已存在，可能需要对其进行修改，以满足RAC的权限和安全需求。 8. **SSH配置**：由于RAC需要节点间的通信，配置Secure Shell (SSH) 无密码互信是必要的，以确保节点间的安全通信和自动化操作。 - **SSH Key Pair** 每个节点上生成RSA密钥对，并将公钥添加到所有其他节点的`authorized_keys`文件中，实现SSH免密登录。通过以上步骤，你可以成功地在Linux环境中搭建一个Oracle RAC 11gR1集群。在实施过程中，遵循最佳实践和详细指南可以确保安装的顺利进行，并为后续的数据库管理和维护打下坚实基础。

Private Ping test

Pinging stnsp001 private from stnsp001 should return stnsp001's private IP address

Pinging stnsp002 private from stnsp001 should return stnsp002's private IP address

Pinging stnsp001 private from stnsp002 should return stnsp001's private IP address

Pinging stnsp002 private from stnsp002 should return stnsp002's private IP address

•

VIP Ping test Pinging the VIP address at this point should fail. VIPs will be activated at the end of the

Oracle Clusterware install.

•

If any of the above tests fail you should fix name/address resolution by updating the DNS or local hosts files

on each node before continuing with the installation.

2.2.2. *Network Adapter configuration

If your network adapters allow configuration you should make sure that they are configured for Full Duplex

and at the 'fastest' speed consistent among nodes. They should not be left to 'auto-negotiate'.

2.3. *Time Sync

There is a general requirement for Oracle RAC that the time on all the nodes be the same. Typically this can

be achieved using Network Time Server protocol. At the very least you should ensure that the system clocks

on all nodes are as close as possible.

2.4. *Configuring Kernel Parameters

On all cluster nodes, verify that the kernel parameters shown in the following table are set to values greater

than or equal to the recommended value shown. The procedure following the table describes how to verify

and set the values.

Parameter Value File

semmsl 250 /proc/sys/kernel/sem

semmns 32000

semopm 100

semmni 128

shmmax Half the size of physical memory (in bytes) /proc/sys/kernel/shmmax

shmmni 4096 /proc/sys/kernel/shmmni

shmall 2097152 /proc/sys/kernel/shmall

file-max 65536 /proc/sys/fs/file-max

ip_local_port_range Minimum: 9000 Maximum:65500 /proc/sys/net/ipv4/ip_local_port_range

rmem_default 262144 /proc/sys/net/core/rmem_default

rmem_max 4194304 /proc/sys/net/core/rmem_max

wmem_default 262144 /proc/sys/net/core/wmem_default

wmem_max 1048576 /proc/sys/net/core/wmem_max

aio-max-nr 1048576 /proc/sys/fs/aio-max-nr

To view the current value specified for these kernel parameters, and to change them if necessary, follow these

steps: 1. Enter the commands shown in the following table to view the current values of the kernel parameters:

Parameters Command

semmsl, semmns,semopm, and semmni # /sbin/sysctl -a | grep sem

for shmall, shmmax, and shmmni # /sbin/sysctl -a | grep shm

file-max # /sbin/sysctl -a | grep file-max

2.2.1. *Network Ping Tests 14

ip_local_port_range # /sbin/sysctl -a | grep ip_local_port_range

rmem_default, rmem_max, wmem_default, and wmem_max # /sbin/sysctl -a | grep net.core

aio-max-nr # /sbin/sysctl -a | grep aio-max-nr

2. If the value of any kernel parameter is less than the recommended value, then complete the following

process: Using any text editor, create or edit the /etc/sysctl.conf file, and add or edit lines similar to the

following:

kernel.shmall = 2097152

kernel.shmmax = 2147483648

kernel.shmmni = 4096

kernel.sem = 250 32000 100 128

fs.file-max = 65536

net.ipv4.ip_local_port_range = 9000 65500

net.core.rmem_default = 262144

net.core.rmem_max = 4194304

net.core.wmem_default = 262144

net.core.wmem_max = 1048576

By specifying the values in the /etc/sysctl.conf file, they persist when you restart the system. Note: Include

lines only for the kernel parameter values that you want to change. For the semaphore parameters

(kernel.sem), you must specify all four values. However, if any of the current system parameter values are

greater than the recommended values, then keep using the larger values.

On Red Hat systems, to have these changes take effect immediately so that you do not have to restart the

system, enter the following command: /sbin/sysctl -p

3. Repeat steps 1 and 2 on all other nodes in the cluster.

On SUSE systems only, enter the following command to cause the system to read the /etc/sysctl.conf file

when it restarts: # /sbin/chkconfig boot.sysctl on

4. On SUSE Linux Enterprise Server 9.0 only, set the kernel parameter disable_cap_mlock as follows:

disable_cap_mlock = 1

5. After updating the values of kernel parameters in the /etc/sysctl.conf file, either restart the computer, or run

the command sysctl -p to make the changes in the /etc/sysctl.conf file available in the active kernel memory.

2.5. *Setting Shell Limits for the oracle User

To improve the performance of the software on Linux systems, you must increase the following shell limits

for the oracle user |Shell Limit |Item in limits.conf |Hard Limit|

Maximum number of open file descriptors nofile 65536

Maximum number of processes available to a single user nproc 16384

To increase the shell limits: 1. Add the following lines to the /etc/security/limits.conf file:

oracle soft nproc 2047

oracle hard nproc 16384

oracle soft nofile 1024

oracle hard nofile 65536

2. Add or edit the following line in the /etc/pam.d/login file, if it does not already exist:

session required /lib/security/pam_limits.so

3. Depending on the oracle user's default shell, make the following changes to the default shell startup file:

For the Bourne, Bash, or Korn shell, add the following lines to the /etc/profile file (or the file

/etc/profile.local on SUSE systems):

•

2.4. *Configuring Kernel Parameters 15

if [ $USER = "oracle" ]; then

if [ $SHELL = "/bin/ksh" ]; then

ulimit -p 16384

ulimit -n 65536

else

ulimit -u 16384 -n 65536

For the C shell (csh or tcsh), add the following lines to the /etc/csh.login file (or the file

/etc/csh.login.local on SUSE systems):

•

if ( $USER == "oracle" ) then

limit maxproc 16384

limit descriptors 65536

endif

Repeat this procedure on all other nodes in the cluster.1.

2.6. *Configuration of the Hangcheck-timer Module

Before installing Oracle Real Application Clusters on Linux systems, verify that the hangcheck-timer module

(hangcheck-timer) is loaded and configured correctly. hangcheck-timer monitors the Linux kernel for

extended operating system hangs that could affect the reliability of a RAC node and cause a database

corruption. If a kernel/device driver hang occurs, then the module restarts the node in seconds. There are 3

parameters used to control the behavior of the module:

The hangcheck_tick parameter: it defines how often, in seconds, the hangcheck-timer checks the

node for hangs. The default value is 60 seconds. Oracle recommends to set it to 1

(hangcheck_tick=1).

The hangcheck_margin parameter: it defines how long the timer waits, in seconds, for a response

from the kernel. The default value is 180 seconds. Oracle recommends to set it to 10

(hangcheck_margin=10)

The hangcheck_reboot parameter: If the value of hangcheck_reboot is equal to or greater than 1,

then the hangcheck-timer module restarts the system. If the hangcheck_ reboot parameter is set to

zero, then the hangcheck-timer module will not restart the node. It should always be set to 1.

If the kernel fails to respond within the sum of the hangcheck_tick and hangcheck_margin parameter values,

then the hangcheck-timer module restarts the system.

2.6.1. *Hangcheck-timer Module verification procedure

1. Log in as root, and enter the following command to check the kernel version:

# uname -a

2. Enter the following command on each node to determine which kernel modules are loaded:

# /sbin/lsmod

3. If the hangcheck-timer module is not listed for any node:

on Kernel 2.4 enter a command similar to the following to start the module on that node:

# /sbin/insmod hangcheck-timer hangcheck_tick=1 hangcheck_margin=10 hangcheck_reboot=1

on Kernel 2.6 enter a command similar to the following to start the module located in the directories of the

current kernel version:

2.5. *Setting Shell Limits for the oracle User 16

# insmod /lib/modules/kernel_version/kernel/drivers/char/hangcheck-timer.ko hangcheck_tick=1

hangcheck_margin=10 hangcheck_reboot=1

In the preceding command example, the variable kernel_version is the kernel version running on your system

that you have got from uname -a.

4. To confirm that the hangcheck module is loaded, enter the following command:

# lsmod | grep hang

The output should be similar to the following:

hangcheck_timer 3289 0

5. To ensure that the module is loaded every time the system restarts, verify that the local system startup file

contains the command shown in the previous step, or add it if necessary:

on Red Hat: On Red Hat Enterprise Linux systems, add the command to the /etc/rc.d/rc.local file.•

on SUSE: On SUSE systems, add the command to the /etc/init.d/boot.local file.•

2.7. *Platform Specific Setup

Show How to Disable RUN_PARALLEL on SLES (SuSE Linux): Hide Disable RUN_PARALLEL on

SLES:

As per Metalink Note:464061.1, on SuSE Linux disable RUN_PARALLEL by setting it to "no" in

/etc/sysconfig/boot. The default setting of "yes" prevents the Oracle Clusterware to start in most cases. For a

different workaround refer to the note for details.

Show How to Configure SELinux on OEL5 and RHEL5: Hide Configure SELinux on OEL5 and RHEL5:

As per Metalink Note:454196.1, on Oracle Enterprise Linux 5 & Redhat Enterprise Linux 5 it's required to

either disable or set SELinux to permissive mode using one of the methods below:

Editing /etc/selinux/config:

Change the SELINUX value to "SELINUX=disabled" or "SELINUX=permissive".♦

•

Appending kernel boot options:

Edit the kernel boot line and append "selinux=0" (to completely disable), or "enforcing=0"

(to set to permissive mode) to the kernel boot options. For example:

♦

•

title Red Hat Enterprise Linux AS (2.6.9-42.ELsmp)

root (hd0,0)

kernel /vmlinuz-2.6.9-42.ELsmp ro root=LABEL=/ rhgb quiet selinux=0

initrd /initrd-2.6.9-42.ELsmp.img

Do one of the above and then reboot the server for change to take effect, or if a reboot is not possible,

issue as root:

•

# setenforce 0

This will put SELinux into permissive mode immediately.

Show How to Ensure latest glibc is installed: Hide Ensure latest glibc is installed:

As per Metalink Note:731599.1, to avoid false node reboots, ensure your glibc rpm is updated as follows:

2.6.1. *Hangcheck-timer Module verification procedure 17

EL4 customers: install glibc-2.3.4-2.40 (or above) or upgrade to EL4u7•

EL5 customers: install glibc-2.5-24 (or above) or upgrade to EL5u2•

SLES10 customers: bug 416838 filed for this problem, contact Novell for fix.•

Unbreakable Linux customers or Redhat Network subscribers can issue:

# up2date glibc

Refer to above note for further details.

Show How to disable deletion of critical Clusterware files: Hide deleting critical Clusterware files:

The Oracle Clusterware places important socket files in /var/tmp/.oracle directory, which can be removed by

Linux crontab cleanup jobs. As per Metalink Note: 391790.1, ensure that such deletion does not occur. The

supplied builtin tmpwatch cronjob:

/usr/sbin/tmpwatch 720 /var/tmp

is safe since it does not delete any socket or special files, only regular files. However custom scripts or 3rd

party cleanup jobs might cleanup such files and cause Clusterware failures.

2.8. *Stage the Oracle Software

It is recommended that you stage the required software onto a local drive on Node 1 of your cluster.

Important. Ensure that you use only 32 bit versions of the Oracle Software on a 32bit OS and 64 bit versions

of the Oracle Software on a 64bit OS A suggested stage is as follows

Oracle 11g Release 1 EE (11.1.0.6) (1 DVD ) /mnt•

The 11gR1 now integrates the Oracle Clusterware, Database and Client install into one DVD with one

runInstaller program.

If you download the software from OTN you will not get the integrated installer. You will have separate

downloads for :

Oracle Clusterware and•

ASM/Database•

2.9. *Cluster Verification Utility stage check

Now you can run the CVU (Cluster Verification Utility) to check the state of the Operating System

configuration. CVU can be run from the installation media, but it is recommended to download the latest

version from:

http://www.oracle.com/technology/products/database/clustering/cvu/cvu_download_homepage.html

After the hardware and OS has been configured, it is recommended to run CVU to verify the nodes are

configured correctly:

runcluvfy.sh stage -post hwos -n stnsp001,stnsp002 -verbose

Show CVU -post hwos output Hide CVU output

./runcluvfy.sh stage -post hwos -n stnsp001,stnsp002 -verbose

Performing post-checks for hardware and operating system setup

2.7. *Platform Specific Setup 18

剩余135页未读，继续阅读

bjlq1234567890

粉丝: 0
资源: 2

Oracle RAC 11g R1安装指南 for Linux

RACGuides_Rac10gR2OnLinux.pdf

RACGuides_

RACGuides_Rac11gR2OnWindows.pdf

白色简洁风格的韩国个人网页源码下载.zip

倒车雷达51单片机超声波测距（含仿真）

白色宽屏风格的室内设计公司整站网站源码下载.zip

白色简洁风格的眼睛设计制作企业网站模板.zip

(178721838)基于Mysql和OpenCV的人脸识别系统（源码和部署教程）.zip

“预防夏季中暑”知识讲座教案课件.pptx

Java毕业设计-基于springboot+vue的在线教育平台源码+文档+视频教程

最新资源