Full explanation of Oracle 10g RAC Installation

Full explanation of Oracle 10g RAC Installation

Directory
1. ORACLE Database RAC description... 1-2
1.1RAC system description... 1-2
1.2 preparations before installation... 1-2
1.2.1 hardware preparations... 1-2
1.2.2 quasi-work on software... 1-2
2. Installation preparation... 2-3
2.1 modify the network configuration file... 2-3
2.2 create an ORACLE user and user group... 2-3
2.3 modify system parameters... 2-5
2.4 create the home Directory of CRS... 2-5
2.5 storage device settings... 2-5
3. Installation Steps... 3-7
3.1 install clusterware. 3-7
3.2 Installation Summary... 3-12
4. Create a database... 4-12
4.1 install database software... 4-12
4.2 create a database... 4-12

Because the image cannot be displayed, please refer to my documents:

Full interpretation of Oracle 10g RAC installation PDF download:

Free in http://linux.bkjia.com/

The username and password are both www.bkjia.com

The specific download directory is available in/June,/June 6,/Oracle 10g RAC Installation

Installing Oracle 10g + ASM test environment in RHEL

Install Oracle 10g R2 RAC on vmwarevm

1. ORACLE Database RAC description 1.1RAC System Description

Oracle rac is a cluster system launched by ORACLE for ORACLE Database. RAC is short for real application cluster, which means a real application cluster system. RAC can work independently in a CLUSTER mode and can be embedded into a third-party CLUSTER system, such as a so-called vender CLUSTER system such as sun cluster 3.2.

In combination with ORACLE's ASM (Automatic Storage Management) and Oracle Clusterware, it is recommended that databases run independently in the system without running third-party Cluster Systems and volume management systems.

1.2 preparations before installation

As the saying goes, it is best to read the official installation manual carefully before installing RAC, because many articles on the Internet are installed according to the environment of the author, in reality, there are many variables that may lead to many installation situations. Therefore, an online article is of reference value only for every installation engineer.

1.2.1 hardware preparation

In terms of hardware, first check whether the server type, operating system type, and memory are correctly connected to two or more servers, and whether the host system can access the storage correctly, whether all host systems share the modified storage.

For the host system, is there enough NICs? RAC requires at least one public and one private Nic, it is used for access to the database instance and for the heartbeat NIC (This heartbeat is also used to transmit data from some databases ).

1.2.2 quasi-work on Software

The software is convenient. First, select the corresponding database software based on the host type, including the database and clusterware software. It is best to select a newer version of the software, in terms of oracle rac, for many platforms, some bugs may exist in the software of the first version. After the correct version is selected, installation can be minimized.

In terms of operating systems, you should also install the best database software, such as solaris 10. It is best to use the update 10 version, we recommend that you use the latest 10 Recommended Patch packages. Patches must be updated, which can greatly reduce the generation of bugs.

2. Installation preparation

In this example, RAC is installed on two nodes of the ORACLE iSCSI server. Because T5120 is used to create two virtual hosts with LDM, therefore, the names of related NICs are all based on the naming method in the virtual machine.

After installing the operating system, you must enter the Recommended Patch pack for the operating system and use the most recent eis cd. If you do not have an eis cd, you can download the latest Recommended Patch pack from the oracle website, for example, the latest patch of solaris10 is as follows: This may require an account

Https://updates.oracle.com/download/12714436.html

2.1 modify the network configuration file

/Etc/hosts this file records future IP addresses, including public and private addresses:

192.168.0.123161 (local address of host 1)

192.168.0.132.162 (local address of host 2)

192.168.0.141_1-vip (public Address of host 1)

192.168.0.163162-vip (public Address of host 2)

192.168.0.151_1-priv (private address of host 1)

192.168.0.172.162-priv (private address of host 2)

You can set a private address to another CIDR block.

These addresses are required in the/etc/hosts file of another host.

The configuration file of the host Nic under/etc/. The public address can be used on the NIC of the local address in the future. The system can use a virtual Nic of plumb, for example, vnet0: 1. The private address must be specified separately, for example,/etc/hostname. vnet1, which is written into the orac1-priv to automatically add the private address Nic plumb when the system reboot.

After setting up all the configuration files, make sure that the following addresses can be pinged:

Ping orac1ping orac2ping orac1-privping orac2-priv

2.2 create corresponding ORACLE users and user groups

Create a unix group and user oracle according to the oracle database installation requirements:

Groupadd dba create dba group

Groupadd oinstall create oinstall Group

Useradd-g oinstall-G dba-d/opt/oracle-m-s/bin/sh oracle create an oracle user

Passwd oracle modify the password of an oracle user

It is very important to create these users and user groups. Do not underestimate them. First, ensure that the above gid and uid are consistent on all nodes. When installing Clusterware, if you do not set the permission for directories and Devices correctly, the software may fail to be correctly installed or installed.

The following definitions are required for the. profile file of an oracle user. You can modify and optimize the file according to the configuration of the host system:

ORACLE_BASE =/opt/oracle/app/oracle

Export ORACLE_BASE

ORACLE_HOME =/opt/oracle/app/oracle/10g

Export ORACLE_HOME

ORACLE_SID = inst-ora1

Export ORACLE_SID

PATH =$ {PATH}: $ ORACLE_HOME/bin

Export PATH

Other parameters such as LD_LIBRARY can be found in. profile file definition, SID each node needs to be defined as 1, 2, 3, 4 and so on, prefix for the entire cluster database defined Instance name, such as inst-ora, each node SID is inst-ora1, insta_ora2 and so on.

Establish a trust relationship:

If it is 10 Gb, you only need to establish the rsh trust relationship. If it is 11 GB, you must establish the ssh host trust relationship:

1. rsh Trust Relationship

Run the following command on all nodes:

Su-oracle

Touch. rhosts

Echo +>. rhosts

2. ssh Trust Relationship

It is very convenient to use commands to create these trust relationships. If you use the 11g runInstaller program, you can use the setup program provided by the program to establish the trust relationship:

Su-oracle

Mkdir. ssh (created without. ssh); chmod 755. ssh

/Usr/bin/ssh-keygen-t rsa

/Usr/bin/ssh-keygen-t dsa

Enter the appropriate content as prompted. the id_rds.pub and id_dsa.pub files are generated under the ssh directory, and all the content of the two files is copied to the authorized_keys file, chmod 644. ssh/authorized_keys file. This file should contain the id_rds.pub and id_dsa.pub files of all nodes.

2.3 modify system parameters

The kernel Parameter of the operating system needs to be modified according to the specific machine configuration. The following are typical system parameters. You can write these parameters to the/etc/system file. After modifying this file, the reboot system is required to take effect:

Set noexec_user_stack = 1

Set semsys: seminfo_semmni = 100

Set semsys: seminfo_semmns = 1024

Set semsys: seminfo_semms = 256

Set semsys: seminfo_semvmx= 32767

Set shmsys: shminfo_shmmax = 4294967295

Set shmsys: shminfo_shmmin = 1

Set shmsys: Sh minfo_shmmni = 100

Set shmsys: shminfo_shmseg = 10

Under Solaris 10, if you use a project for management, You can dynamically modify these kernel parameters, which will facilitate the production system online in the future.

2.4 create the home Directory of CRS

The home of CRS should not be put together with the home of ORACLE, because the CRS directory will eventually become the root user's permission.

Mkdir-p/opt/crs/oracle/product/10/app

Chown-R root: oinstall/opt/crs

Chmod-R 775/opt/crs/oracle

Note that the host in the crs directory is set to root: oinstall. If it is set to another host, run root after installation. THE sh script will have a lot of warnings, and the possibility of crs not running properly will be very high.

2.5 storage device settings

Storage devices are mainly used by Clusterware to store OCR and voting disks, and to store data and other files for the database. It is very important to determine how to use the storage device, which will affect the database architecture in the future, storage supports ASM, cluster file system, and raw devices. The following matrix provides support for CRS in various storage methods:

File Types Supported

Storage OptionCRS DatabaseRecovery

Automatic Storage ManagementNoYes

 

Cluster file systemYes Yes

 

NFS file system

PRIMECLUSTER and a certified Yes

NAS device (SPARConly)

 

Shared raw logical volumes (iSCSI only) Yes No

 

Shared raw partitions Yes No

We recommend that you use ASM Automatic Storage Management for storage management. For Cluster file system, most of the costs are required to purchase the appropriate software, however, SUN's QFS software can also be used (the software should be free of charge ). If raw bare devices are used, the requirements for users are relatively high, because raw needs to allocate a raw device to each dbf file when installing the database, if you need to add new files such as dbf in the future, the operation steps will be complicated.

When Using ASM, you must pay attention to the division of each LUN. Do not use the EFI format as the disk label. In many practices, we found that when using the EFI label format for storage, A strange phenomenon will occur. After the cluster is created, the database can be created smoothly, but the instance can only be started on one node, and the other node cannot be started. view the alertlog file, reports Errors for a ora-600 and errors such as queue file IO error. In solaris, The LUN is divided into 2 TB or less, and the VTOC label is used. The official documentation suggests creating large-space Luns to reduce the system's storage management, if the storage space is large, you can create multiple Luns smaller than 2 TB, and then create one or more ASM groups to manage these Luns.

Based on RAC requirements for storage space, the corresponding LUN or slice can be divided. The LUN and voting disk for storing OCR can be smaller. We recommend that you use 1 GB space, the number of Luns used to store database data files is larger.

If these Luns have been used, especially in RAC, then you need to clear the disk content by using the dd command. For example:

Dd if =/dev/zero of =/dev/rdsk/c2t0d0s0 bs = 1024 k count = 1000

In this example, c0d1s0 is used as the OCR storage device, and c0d1s0 is used as the voting disk. During installation, the installer will prompt which redundancy mode is used, which is generally in the Normal mode, that is, the OCR device requires two devices for mirror, and the voting disk requires three devices for redundancy. If these devices have performed raid 5 and other redundancy protection on the memory, these redundancy methods can adopt the External mode, that is, only a single device can be used.

The device permission must be set correctly. Otherwise, the installer reports an error. The specific permission settings are as follows:

Chown-R root: the host of the oinstall/dev/rdsk/c0d1s0 OCR disk is root, and the user is oinstall

Chmod 640/dev/rdsk/c0d1s0

Chown-R root: oinstall/dev/rdsk/c0d1s3 voting disk is set as a CRS disk

The chmod-R 660/dev/rdsk/c0d1s3voting disk file has 660 read/write attributes.

Set the raw device permission to ORACLE: dba for storing files such as oracle Database dbf, and set the write permission to 775.

1 2 3 Next Page