Install Oracle10g on a bare Device on RHEL5

Lab environment: RedHatEnterpriseLinuxServerrelease5ORALCE10g10.2.0.1 I. Disk planning partition my lab machine has three hard disks, sda, s

Lab environment: Red Hat Enterprise Linux Server release 5 ORALCE 10g 10.2.0.1 I. Disk planning partition my lab machine has three hard disks, sda, s

Lab environment:
Red Hat Enterprise Linux Server release 5
ORALCE 10g 10.2.0.1

I. Disk planning and partitioning
My lab machine has three hard disks, sda, sdb, and sdc. Sda is only used to install the operating system and application software. sdb is used to partition and store database system files such as system and sysaux. sdc is used to partition the disk, this hard disk is mainly used to store business data.

Use the fdisk command to partition. The specific process is omitted. After creating all partitions, run the following command to view the partition:
# Fdisk-l
Disk/dev/sda: 16.1 GB, 16106127360 bytes
255 heads, 63 sectors/track, 1958 cylinders
Units = cylinders of 16065*512 = 8225280 bytes
Device Boot Start End Blocks Id System
/Dev/sda1*1 1697 13631121 83 Linux
/Dev/sda2 1698 1958 2096482 + 82 Linux swap/Solaris
Disk/dev/sdb: 5368 MB, 5368709120 bytes
255 heads, 63 sectors/track, 652 cylinders
Units = cylinders of 16065*512 = 8225280 bytes
Device Boot Start End Blocks Id System
/Dev/sdb1 1 652 5237158 + 5 Extended
/Dev/sdb5 1 13 104359 + 83 Linux
/Dev/sdb6 14 26 104391 83 Linux
/Dev/sdb7 27 39 104391 83 Linux
/Dev/sdb8 40 52 104391 83 Linux
/Dev/sdb9 53 59 56196 83 Linux
/Dev/sdb10 60 182 987966 83 Linux
/Dev/sdb11 183 305 987966 83 Linux
/Dev/sdb12 306 428 987966 83 Linux
/Dev/sdb13 429 652 1799248 + 83 Linux
Disk/dev/sdc: 5368 MB, 5368709120 bytes
255 heads, 63 sectors/track, 652 cylinders
Units = cylinders of 16065*512 = 8225280 bytes
Device Boot Start End Blocks Id System
/Dev/sdc1 1 652 5237158 + 5 Extended
/Dev/sdc5 1 123 987934 + 83 Linux
/Dev/sdc6 124 246 987966 83 Linux
/Dev/sdc7 247 369 987966 83 Linux
/Dev/sdc8 370 492 987966 83 Linux
/Dev/sdc9 493 620 1028128 + 83 Linux
/Dev/sdc10 621 652 257008 + 83 Linux

2. Build mappings for bare Devices
At the root prompt, type:
# Raw-
Query the raw device name that has been created. It is blank currently. You can use it from the first device name,
At the root prompt, type:
Raw/dev/raw/raw1/dev/sdb5
Raw/dev/raw/raw2/dev/sdb6
Raw/dev/raw/raw3/dev/sdb7
Raw/dev/raw/raw4/dev/sdb8
Raw/dev/raw/raw5/dev/sdb9
Raw/dev/raw/raw6/dev/sdb10
Raw/dev/raw/raw7/dev/sdb11
Raw/dev/raw/raw8/dev/sdb12
Raw/dev/raw/raw9/dev/sdc5
Raw/dev/raw/raw10/dev/sdc6
Raw/dev/raw/raw11/dev/sdc7
Raw/dev/raw/raw12/dev/sdc8
Raw/dev/raw/raw13/dev/sdc9
Raw/dev/raw/raw14/dev/sdc10
At this point, we have created 14 raw device names for direct management by Oracle. Check the raw device names that have been created:

# Raw-
/Dev/raw/raw1: bound to major 8, minor 21
/Dev/raw/raw2: bound to major 8, minor 22
/Dev/raw/raw3: bound to major 8, minor 23
/Dev/raw/raw4: bound to major 8, minor 24
/Dev/raw/raw5: bound to major 8, minor 25
/Dev/raw/raw6: bound to major 8, minor 26
/Dev/raw/raw7: bound to major 8, minor 27
/Dev/raw/raw8: bound to major 8, minor 28
/Dev/raw/raw9: bound to major 8, minor 37
/Dev/raw/raw10: bound to major 8, minor 38
/Dev/raw/raw11: bound to major 8, minor 39
/Dev/raw/raw12: bound to major 8, minor 40
/Dev/raw/raw13: bound to major 8, minor 41
/Dev/raw/raw14: bound to major 8, minor 42

If you want to delete a raw device name (for example,/dev/raw/raw1), type:
# Raw/dev/raw/raw1 0 0
The created bare device becomes invalid after being restarted. You need to modify the system file.

Modify the system initialization file and add the following line to the/etc/rc. local file:
Raw/dev/raw/raw1/dev/sdb5
Raw/dev/raw/raw2/dev/sdb6
Raw/dev/raw/raw3/dev/sdb7
Raw/dev/raw/raw4/dev/sdb8
Raw/dev/raw/raw5/dev/sdb9
Raw/dev/raw/raw6/dev/sdb10
Raw/dev/raw/raw7/dev/sdb11
Raw/dev/raw/raw8/dev/sdb12
Raw/dev/raw/raw9/dev/sdc5
Raw/dev/raw/raw10/dev/sdc6
Raw/dev/raw/raw11/dev/sdc7
Raw/dev/raw/raw12/dev/sdc8
Raw/dev/raw/raw13/dev/sdc9
Raw/dev/raw/raw14/dev/sdc10
Chmod 660/dev/raw/raw1
Chmod 660/dev/raw/raw2
Chmod 660/dev/raw/raw3
Chmod 660/dev/raw/raw4
Chmod 660/dev/raw/raw5
Chmod 660/dev/raw/raw6
Chmod 660/dev/raw/raw7
Chmod 660/dev/raw/raw8
Chmod 660/dev/raw/raw9
Chmod 660/dev/raw/raw10
Chmod 660/dev/raw/raw11
Chmod 660/dev/raw/raw12
Chmod 660/dev/raw/raw13
Chmod 660/dev/raw/raw14
Chown oracle. dba/dev/raw/raw1
Chown oracle. dba/dev/raw/raw2
Chown oracle. dba/dev/raw/raw3
Chown oracle. dba/dev/raw/raw4
Chown oracle. dba/dev/raw/raw5
Chown oracle. dba/dev/raw/raw6
Chown oracle. dba/dev/raw/raw7
Chown oracle. dba/dev/raw/raw8
Chown oracle. dba/dev/raw/raw9
Chown oracle. dba/dev/raw/raw10
Chown oracle. dba/dev/raw/raw11
Chown oracle. dba/dev/raw/raw12
Chown oracle. dba/dev/raw/raw13
Chown oracle. dba/dev/raw/raw14
You can also modify the etc/udev/rules. d/60-raw.rules file and add the following records
ACTION = "add", KERNEL = "sdb5", RUN + = "/bin/raw/dev/raw/raw1% N"
ACTION = "add", KERNEL = "sdb6", RUN + = "/bin/raw/dev/raw/raw2% N"
ACTION = "add", KERNEL = "sdb7", RUN + = "/bin/raw/dev/raw/raw3% N"
ACTION = "add", KERNEL = "sdb8", RUN + = "/bin/raw/dev/raw/raw4% N"
ACTION = "add", KERNEL = "sdb9", RUN + = "/bin/raw/dev/raw/raw5% N"
ACTION = "add", KERNEL = "sdb10", RUN + = "/bin/raw/dev/raw/raw6% N"
ACTION = "add", KERNEL = "sdb11", RUN + = "/bin/raw/dev/raw/raw7% N"
ACTION = "add", KERNEL = "sdb12", RUN + = "/bin/raw/dev/raw/raw8% N"
ACTION = "add", KERNEL = "sdc5", RUN + = "/bin/raw/dev/raw/raw9% N"
ACTION = "add", KERNEL = "sdc6", RUN + = "/bin/raw/dev/raw/raw10% N"
ACTION = "add", KERNEL = "sdc7", RUN + = "/bin/raw/dev/raw/raw11% N"
ACTION = "add", KERNEL = "sdc8", RUN + = "/bin/raw/dev/raw/raw12% N"
ACTION = "add", KERNEL = "sdc9", RUN + = "/bin/raw/dev/raw/raw13% N"
ACTION = "add", KERNEL = "sdc10", RUN + = "/bin/raw/dev/raw/raw14% N"
KERNEL = "raw [1-9]", OWNER = "oracle", GROUP = "oinstall", MODE = "640"
KERNEL = "raw1 [0-4]", OWNER = "oracle", GROUP = "oinstall", MODE = "640"

# Start_udev
Refresh bare Devices
In this way, the system will re-create the required raw device name at the next startup (the above content can be simplified by using wildcards, but I am using wildcards that cannot be completely matched ).
The preceding operations may require the creation of oracle users and groups.