26.2. Installing Oracle 10gR2 Cluster Ready Services (CRS) with MPIO
Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
26.2. Installing Oracle 10gR2 Cluster Ready Services (CRS) with MPIO
There is a bug installing Oracle 10gR2 CRS services using MPIO(Multipath I/O). The bug has been reported to Oracle and the bug number and description states:
BUG 5005148 - CANNOT USE BLOCK DEVICES IN VOTING DISK AND OCR DURING 10G RAC INSTALLATION
BUG 5005148 - CANNOT USE BLOCK DEVICES IN VOTING DISK AND OCR DURING 10G RAC INSTALLATION
Copy to ClipboardCopied!Toggle word wrapToggle overflow
This has been fixed in Oracle 11g.
Before attempting to install CRS, ensure that all firewalls are disabled:
service iptables stop
chkconfig iptables off
service iptables stop
chkconfig iptables off
Copy to ClipboardCopied!Toggle word wrapToggle overflow
There are workarounds to successfully install CRS using MPIO. MPIO has to be disabled during installation. After the Vipca portion of the CRS installation is complete, the MPIO can be turned back on, restart CRS services. In the following examples using MPIO, friendly names are used for ease of manageability. In this example Oracle 10g R2 CRS is using internal redundancy for the OCR and VOTING disks.
Read /usr/share/doc/device-mapper-multipath-0.4.5/Multipath-usage.txt for more information on configuring multipath.
First, determine which block devices will be associated with MPIO devices with your OCR or Voting Disks and save the output to a log file.
Copy to ClipboardCopied!Toggle word wrapToggle overflow
Delete raw links to Multipath Devices on all nodes:
rm -f /dev/raw/*
rm -f /dev/raw/*
Copy to ClipboardCopied!Toggle word wrapToggle overflow
Shut down multipath:
multipath -F #shuts off Multipath
multipath -F #shuts off Multipath
Copy to ClipboardCopied!Toggle word wrapToggle overflow
Looking at the multipath.log output file, you can see which block devices will used for Oracle CRS. To be sure you have the correct disk on all nodes, look at /proc/partitons. In this installation example, each device has a unique size so it is easier to map. Now link the block devices to the raw devices on all nodes by modifying /etc/sysconfig/rawdevices. Run ll on the device to get the major minor number for a block device, as seen below.
ll /dev/sdc1
brw-rw---- 1 root disk 8, 33 Oct 1 12:46 /dev/sdc1 #ocr1
ll /dev/sdd1
brw-rw---- 1 root disk 8, 49 Oct 1 12:47 /dev/sdd1 #ocr2
ll /dev/sde1
brw-rw---- 1 root disk 8, 65 Oct 1 12:47 /dev/sde1 #vote1
ll /dev/sdg1
brw-rw---- 1 root disk 8, 97 Oct 1 12:48 /dev/sdg1 #vote2
ll /dev/sdh1
brw-rw---- 1 root disk 8, 113 Oct 1 12:49 /dev/sdh1 #vote3
# ll /dev/sdc1
brw-rw---- 1 root disk 8, 33 Oct 1 12:46 /dev/sdc1 #ocr1
# ll /dev/sdd1
brw-rw---- 1 root disk 8, 49 Oct 1 12:47 /dev/sdd1 #ocr2
# ll /dev/sde1
brw-rw---- 1 root disk 8, 65 Oct 1 12:47 /dev/sde1 #vote1
# ll /dev/sdg1
brw-rw---- 1 root disk 8, 97 Oct 1 12:48 /dev/sdg1 #vote2
# ll /dev/sdh1
brw-rw---- 1 root disk 8, 113 Oct 1 12:49 /dev/sdh1 #vote3
Copy to ClipboardCopied!Toggle word wrapToggle overflow
Change the configuration file /etc/sysconfig/rawdevices using vi or your favorite editor and add the following block devices.
Copy to ClipboardCopied!Toggle word wrapToggle overflow
Double check on the other nodes that the minor numbers for the block devices match. The second number in the example below, 8 in this case, is the minor number and 1 is the major number.
ll /dev/sdh1
brw-rw---- 1 root disk 8, 113 Oct 1 13:14 /dev/sdh1
$ ll /dev/sdh1
brw-rw---- 1 root disk 8, 113 Oct 1 13:14 /dev/sdh1
Copy to ClipboardCopied!Toggle word wrapToggle overflow
Copy /etc/sysconfig/rawdevices to other nodes then restart it. You will see the created raw devices in /dev/raw.
/etc/rc5.d/S56rawdevices start
Assigning devices:
/dev/raw/raw1 --> 8 33
/dev/raw/raw1: bound to major 8, minor 33
/dev/raw/raw2 --> 8 49
/dev/raw/raw2: bound to major 8, minor 49
/dev/raw/raw3 --> 8 65
/dev/raw/raw3: bound to major 8, minor 65
/dev/raw/raw4 --> 8 97
/dev/raw/raw4: bound to major 8, minor 97
/dev/raw/raw5 --> 8 113
/dev/raw/raw5: bound to major 8, minor 113
done
# /etc/rc5.d/S56rawdevices start
Assigning devices:
/dev/raw/raw1 --> 8 33
/dev/raw/raw1: bound to major 8, minor 33
/dev/raw/raw2 --> 8 49
/dev/raw/raw2: bound to major 8, minor 49
/dev/raw/raw3 --> 8 65
/dev/raw/raw3: bound to major 8, minor 65
/dev/raw/raw4 --> 8 97
/dev/raw/raw4: bound to major 8, minor 97
/dev/raw/raw5 --> 8 113
/dev/raw/raw5: bound to major 8, minor 113
done
Copy to ClipboardCopied!Toggle word wrapToggle overflow
Now check that the permissions are set for the Oracle installation.
ll /dev/raw
total 0
crwxrwxrwx 1 oracle dba 162, 1 Oct 1 13:13 raw1
crwxrwxrwx 1 oracle dba 162, 2 Oct 1 13:13 raw2
crwxrwxrwx 1 oracle dba 162, 3 Oct 1 13:13 raw3
crwxrwxrwx 1 oracle dba 162, 4 Oct 1 13:13 raw4
crwxrwxrwx 1 oracle dba 162, 5 Oct 1 13:13 raw5
# ll /dev/raw
total 0
crwxrwxrwx 1 oracle dba 162, 1 Oct 1 13:13 raw1
crwxrwxrwx 1 oracle dba 162, 2 Oct 1 13:13 raw2
crwxrwxrwx 1 oracle dba 162, 3 Oct 1 13:13 raw3
crwxrwxrwx 1 oracle dba 162, 4 Oct 1 13:13 raw4
crwxrwxrwx 1 oracle dba 162, 5 Oct 1 13:13 raw5
Copy to ClipboardCopied!Toggle word wrapToggle overflow
Now you can commence an Oracle Clusterware installation.
Note
If during the installation process, Oracle says the raw devices are busy, then Multipath was left on in one of the nodes.
After the VIPCA portion of the Oracle CRS is complete, you need to comment out the raw devices you created and copy /etc/sysconfig/rawdevices to the other nodes:
Copy to ClipboardCopied!Toggle word wrapToggle overflow
Delete the raw devices created for Oracle CRS installation.
rm -f /dev/raw/*
$ rm -f /dev/raw/*
Copy to ClipboardCopied!Toggle word wrapToggle overflow
Turn on Multipath I/O (MPIO) again.
multipath
$ multipath
Copy to ClipboardCopied!Toggle word wrapToggle overflow
Create a simple script in /etc/rc5.d/ (before CRS Starts but after MPIO starts) to bind raw devices using MPIO.
num="1"
for i in `ls /dev/mpath/ocr?p? | sort`
do
raw /dev/raw/raw${num} $i
let "num = $num + 1"
done
num="3"
for i in `ls /dev/mpath/vote?p? | sort`
do
raw /dev/raw/raw${num} $i
let "num = $num + 1"
done
num="1"
for i in `ls /dev/mpath/ocr?p? | sort`
do
raw /dev/raw/raw${num} $i
let "num = $num + 1"
done
num="3"
for i in `ls /dev/mpath/vote?p? | sort`
do
raw /dev/raw/raw${num} $i
let "num = $num + 1"
done
Copy to ClipboardCopied!Toggle word wrapToggle overflow
Then run the script, /etc/rc5.d/, that you just created.
/etc/rc5.d/S57local start
/dev/raw/raw1: bound to major 253, minor 25
/dev/raw/raw2: bound to major 253, minor 21
/dev/raw/raw3: bound to major 253, minor 22
/dev/raw/raw4: bound to major 253, minor 23
/dev/raw/raw5: bound to major 253, minor 24
# /etc/rc5.d/S57local start
/dev/raw/raw1: bound to major 253, minor 25
/dev/raw/raw2: bound to major 253, minor 21
/dev/raw/raw3: bound to major 253, minor 22
/dev/raw/raw4: bound to major 253, minor 23
/dev/raw/raw5: bound to major 253, minor 24
Copy to ClipboardCopied!Toggle word wrapToggle overflow
Verify the correct permissions are all set.
ll /dev/raw
total 0
crwxrwxrwx 1 oracle dba 162, 1 Oct 1 13:58 raw1
crwxrwxrwx 1 oracle dba 162, 2 Oct 1 13:58 raw2
crwxrwxrwx 1 oracle dba 162, 3 Oct 1 13:58 raw3
crwxrwxrwx 1 oracle dba 162, 4 Oct 1 13:58 raw4
crwxrwxrwx 1 oracle dba 162, 5 Oct 1 13:58 raw5
# ll /dev/raw
total 0
crwxrwxrwx 1 oracle dba 162, 1 Oct 1 13:58 raw1
crwxrwxrwx 1 oracle dba 162, 2 Oct 1 13:58 raw2
crwxrwxrwx 1 oracle dba 162, 3 Oct 1 13:58 raw3
crwxrwxrwx 1 oracle dba 162, 4 Oct 1 13:58 raw4
crwxrwxrwx 1 oracle dba 162, 5 Oct 1 13:58 raw5
Copy to ClipboardCopied!Toggle word wrapToggle overflow
Restart CRS and be sure the ONS processes all start. This ensures Oracle CRS is functional on this node.
/ora/crs/bin/crsctl start crs
Attempting to start CRS stack
The CRS stack will be started shortly
# /ora/crs/bin/crsctl start crs
Attempting to start CRS stack
The CRS stack will be started shortly
Copy to ClipboardCopied!Toggle word wrapToggle overflow
Repeat for the process for the rest of the nodes. Now the Oracle CRS installation is complete using Multipath I/O.
Once complete, you can check the status of the nodes:
Wir helfen Red Hat Benutzern, mit unseren Produkten und Diensten innovativ zu sein und ihre Ziele zu erreichen – mit Inhalten, denen sie vertrauen können. Entdecken Sie unsere neuesten Updates.
Mehr Inklusion in Open Source
Red Hat hat sich verpflichtet, problematische Sprache in unserem Code, unserer Dokumentation und unseren Web-Eigenschaften zu ersetzen. Weitere Einzelheiten finden Sie in Red Hat Blog.
Über Red Hat
Wir liefern gehärtete Lösungen, die es Unternehmen leichter machen, plattform- und umgebungsübergreifend zu arbeiten, vom zentralen Rechenzentrum bis zum Netzwerkrand.