The nuances of installing Oracle 10g RAC on SUSE 11

The task was to install Oracle 10g RAC on SLES 11. In the course of the installation, I ran into a number of nuances that were poorly described on the Internet. I will not describe the installation process in detail. For this you can see the following descriptions. which I used when installing:
* in Russian
* in English

Initial data:
- external storage connected via Fiber Channel
- 2 remote nodes with installed SLES 11, there is kvm

Preparatory work

- configure and check ntp on all nodes, run with the -x flag (/ etc / sysconfig / ntp - in options)
- install additional packages (advice - install development package and full-featured X-sy)
- install java
- fix /etc/profile.d/oracle.sh - correct ORACLE_BASE, ORACLE_HOME, etc.
- fix /etc/profile.d/oracle.csh - correct ORACLE_BASE, ORACLE_HOME, etc.
- usermod -G dba, disk oracle
- Rac and Database have different housas, so before installing RAC, set, for example,
ORACLE_HOME = / opt / oracle / product / 10.2 / crs

Network configuration

- configure DNS
- we set IP and we register in DNS for each node

1. public IP, for example eth1
2. private IP (for interconnect, preferably internal VLAN), for example eth2
3. VIP IP (on the same network as public) - virtual addresses that are simply registered in the DNS, the cluster will then pick them up

- set up ssh keys so that the oracle user goes to all nodes without a password
')

ASM installation

Install ASMLIB

oracleasm driver from OS distribution
oracleasm-support-2.1.7-1.SLE11.x86_64.rpm package from Orakla website
oracleasmlib-2.0.4-1.sle11.x86_64.rpm package from Orakla website

Configuring ASMLIB

/etc/init.d/oracleasm configure
owner: oracle
group: dba
We create disks approximately as follows. The important point is on the partitions. On a disk device like / dev / mapper / mpathb, everything is also perfectly created. only then does not work.

/etc/init.d/oracleasm createdisk OCRDISK / dev / mapper / mpathb_part1
/etc/init.d/oracleasm createdisk VOTEDISK / dev / mapper / mpathb_part2
/etc/init.d/oracleasm createdisk VOL1_REDO / dev / mapper / mpathb_part4
/etc/init.d/oracleasm createdisk VOL1_DATA / dev / mapper / mpathc_part1
/etc/init.d/oracleasm createdisk VOL2_DATA / dev / mapper / mpathc_part2
/etc/init.d/oracleasm createdisk VOL1_INDEX / dev / mapper / mpathd_part1
/etc/init.d/oracleasm scandisks
/etc/init.d/oracleasm listdisks
/etc/init.d/oracleasm enable

We check ASMLIB

reboot
/etc/init.d/oracleasm listdisks

In case of problems, look
tail -n 100 /var/log/oracleasm

Installation

expanding the clusterware archive
As root user do

cd <distrib_path> / rootpre
[root @ rac1 rootpre] # ./rootpre.sh
[root @ rac1 rootpre] # xhost +

xhost + is very desirable, otherwise some setup scripts launched by the installer may not start
Officially, SLES 11 is not supported by Oracle, so as a user oracle

export DISPLAY =: 0.0
./runInstaller -ignoreSysPrereqs

In general, the installation process is successful, but when it comes to running root.sh, problems arise.

Root.sh script

So before running root.sh
- check that it is correctly exposed

• $ ORACLE_HOME
• export DISPLAY =: 0.0
• xhost +

- replace $ ORACLE_HOME / bin / ocslfmt.bin , for myself I found it on another working system, for more unhappy comrades I give a link for a clever solution to the problem
- remove lines from $ ORACLE_HOME / bin / vipca

if ["$ arch" = "i686" -o "$ arch" = "ia64" -o "$ arch" = "x86_64"]
then
LD_ASSUME_KERNEL = 2.4.19
export LD_ASSUME_KERNEL
fi

- remove lines from $ ORACLE_HOME / bin / srvctl

LD_ASSUME_KERNEL = 2.4.19
export LD_ASSUME_KERNEL

- run in x-ah
- if VIP addresses are not established - run vipca manually. in x-ah
vipca requires export DISPLAY=:0.0
- ignore the compilation bug, it is treated with a subsequent patch
In general, after running scripts on all nodes, the installation of the cluster can be considered successful.

ASM setup

After a successful installation of clusterware, run dbca and configure ASM.
Here, too, there is one nuance. associated with multipathd
In order to find the AFM correctly, specify / dev / mapper / * in the dbca search path of the ASM in the dbca
or it can be done after. if suddenly you found everything with dbca, and then lost it after another reboot with the command

ALTER SYSTEM SET asm_diskstring = '/ dev / mapper / *' SCOPE = BOTH SID = '+ ASM1';