Bare equipment based on Linux to create 10g Database

Apr 10 posted in Oracle (RSS), 79 views.

First, the district do not want to step to the hard disk is divided into the following areas:
[root @ suk1 ~] # fdisk-l / dev / sdb

Disk / dev / sdb: 4294 MB, 4294967296 bytes
255 heads, 63 sectors / track, 522 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/ dev/sdb1 1 44 353398 + 83 Linux
/ dev/sdb2 45 69 200812 + 83 Linux
/ dev/sdb3 70 88 152617 + 83 Linux
/ dev/sdb4 89 522 3486 105 5 Extended
/ dev/sdb5 89 101 1043 91 83 Linux
/ dev/sdb6 102 114 1043 91 83 Linux
/ dev/sdb7 115 117 2406 6 83 Linux
/ dev/sdb8 118 120 2406 6 83 Linux
/ dev/sdb9 121 127 5619 6 83 Linux
/ dev/sdb10 128 134 5619 6 83 Linux

2, bound naked bound naked equipment equipment in two ways
1) with an order binding
[root @ suk1 raw] # raw / dev/raw/raw1 / dev/sdb1
/ dev/raw/raw1: bound to major 8, minor 17
[root @ suk1 raw] # raw / dev/raw/raw2 / dev/sdb2
/ dev/raw/raw2: bound to major 8, minor 18
[root @ suk1 raw] # raw / dev/raw/raw3 / dev/sdb3
/ dev/raw/raw3: bound to major 8, minor 19
[root @ suk1 raw] # raw / dev/raw/raw5 / dev/sdb5
/ dev/raw/raw5: bound to major 8, minor 21
[root @ suk1 raw] # raw / dev/raw/raw6 / dev/sdb6
/ dev/raw/raw6: bound to major 8, minor 22
[root @ suk1 raw] # raw / dev/raw/raw7 / dev/sdb7
/ dev/raw/raw7: bound to major 8, minor 23
[root @ suk1 raw] # raw / dev/raw/raw8 / dev/sdb8
/ dev/raw/raw8: bound to major 8, minor 24
[root @ suk1 raw] # raw / dev/raw/raw9 / dev/sdb9
/ dev/raw/raw9: bound to major 8, minor 25
[root @ suk1 raw] # raw / dev/raw/raw10 / dev/sdb10
/ dev/raw/raw10: bound to major 8, minor 26

[root @ suk1 raw] # raw-qa
/ dev/raw/raw1: bound to major 8, minor 17
/ dev/raw/raw2: bound to major 8, minor 18
/ dev/raw/raw3: bound to major 8, minor 19
/ dev/raw/raw5: bound to major 8, minor 21
/ dev/raw/raw6: bound to major 8, minor 22
/ dev/raw/raw7: bound to major 8, minor 23
/ dev/raw/raw8: bound to major 8, minor 24
/ dev/raw/raw9: bound to major 8, minor 25
/ dev/raw/raw10: bound to major 8, minor 26

Note:
/ dev/sdb4 is the extended partition, not to bare equipment bound to the partition.

In this way the naked binding equipment will restart in OS failure, in order to take effect after you restart, you can modify / etc / rc.local file, add this to / etc / rc.local file:
raw / dev/raw/raw1 / dev/sdb1
raw / dev/raw/raw2 / dev/sdb2
raw / dev/raw/raw3 / dev/sdb3
raw / dev/raw/raw5 / dev/sdb5
raw / dev/raw/raw6 / dev/sdb6
raw / dev/raw/raw7 / dev/sdb7
raw / dev/raw/raw8 / dev/sdb8
raw / dev/raw/raw9 / dev/sdb9
raw / dev/raw/raw10 / dev/sdb10

In this way is actually the implementation of the boot when / etc / rc.local file in order to carry out the raw binding.

2) bind with services modify / etc / sysconfig / rawdevices the following documents in order to automatically load when booting bare equipment
/ dev/raw/raw1 / dev/sdb1
/ dev/raw/raw2 / dev/sdb2
/ dev/raw/raw3 / dev/sdb3
/ dev/raw/raw5 / dev/sdb5
/ dev/raw/raw6 / dev/sdb6
/ dev/raw/raw7 / dev/sdb7
/ dev/raw/raw8 / dev/sdb8
/ dev/raw/raw9 / dev/sdb9
/ dev/raw/raw10 / dev/sdb10

And then start the services:
[root @ suk1 raw] # service rawdevices start
[root @ suk1 raw] # service rawdevices start
Assigning devices:
/ dev/raw/raw1 -> / dev/sdb1
/ dev/raw/raw1: bound to major 8, minor 17
/ dev/raw/raw2 -> / dev/sdb2
/ dev/raw/raw2: bound to major 8, minor 18
/ dev/raw/raw3 -> / dev/sdb3
/ dev/raw/raw3: bound to major 8, minor 19
/ dev/raw/raw5 -> / dev/sdb5
/ dev/raw/raw5: bound to major 8, minor 21
/ dev/raw/raw6 -> / dev/sdb6
/ dev/raw/raw6: bound to major 8, minor 22
/ dev/raw/raw7 -> / dev/sdb7
/ dev/raw/raw7: bound to major 8, minor 23
/ dev/raw/raw8 -> / dev/sdb8
/ dev/raw/raw8: bound to major 8, minor 24
/ dev/raw/raw9 -> / dev/sdb9
/ dev/raw/raw9: bound to major 8, minor 25
/ dev/raw/raw10 -> / dev/sdb10

Bind in this way in the OS of the bare device will remain in force after the restart.

3, modification of equipment is a bare naked main modification is the main equipment is also in two ways:
1) amend the order to amend an order is simple:
[root @ suk1 raw] # chown oracle: oinstall / dev/raw/raw1
[root @ suk1 raw] # chown oracle: oinstall / dev/raw/raw2
[root @ suk1 raw] # chown oracle: oinstall / dev/raw/raw3
[root @ suk1 raw] # chown oracle: oinstall / dev/raw/raw4
[root @ suk1 raw] # chown oracle: oinstall / dev/raw/raw5
[root @ suk1 raw] # chown oracle: oinstall / dev/raw/raw6
[root @ suk1 raw] # chown oracle: oinstall / dev/raw/raw7
[root @ suk1 raw] # chown oracle: oinstall / dev/raw/raw8
[root @ suk1 raw] # chown oracle: oinstall / dev/raw/raw9
[root @ suk1 raw] # chown oracle: oinstall / dev/raw/raw10

Since the / dev files are under the dynamic created in the OS after the restart, will become a main root: disk, to resolve this problem, you can write the above command to / etc / rc.local file :
chown oracle: oinstall / dev/raw/raw1
chown oracle: oinstall / dev/raw/raw2
chown oracle: oinstall / dev/raw/raw3
chown oracle: oinstall / dev/raw/raw4
chown oracle: oinstall / dev/raw/raw5
chown oracle: oinstall / dev/raw/raw6
chown oracle: oinstall / dev/raw/raw7
chown oracle: oinstall / dev/raw/raw8
chown oracle: oinstall / dev/raw/raw9
chown oracle: oinstall / dev/raw/raw10

This can re-boot every time to change the owner.

2) modify / etc/udev/permissions.d/50-udev.permissions documents will be / etc/udev/permissions.d/50-udev.permissions the 113 line from the
raw / *: root: disk: 0660
Amended to read
raw / *: oracle: oinstall: 0660

Modify the meaning of the bare device is the default owner for oracle: oinstall, the default mode is 0660.
Restart the OS test.

4, create a symbolic link can omit this step, but more intuitive to some, it is proposed the establishment of soft link
[oracle @ suk1 ~] $ cd $ ORACLE_BASE
[oracle @ suk1 oracle] $ ls
oraInventory product
[oracle @ suk1 oracle] $ mkdir-p oradata/test1
[oracle @ suk1 oracle] $ cd oradata/test1
[oracle @ suk1 oradata] $ ln-s / dev/raw/raw1 system01.dbf
[oracle @ suk1 oradata] $ ln-s / dev/raw/raw2 undotbs01.dbf
[oracle @ suk1 oradata] $ ln-s / dev/raw/raw3 sysaux01.dbf
[oracle @ suk1 oradata] $ ln-s / dev/raw/raw5 users01.dbf
[oracle @ suk1 oradata] $ ln-s / dev/raw/raw6 temp01.dbf
[oracle @ suk1 oradata] $ ln-s / dev/raw/raw7 control01.ctl
[oracle @ suk1 oradata] $ ln-s / dev/raw/raw8 control02.ctl
[oracle @ suk1 oradata] $ ln-s / dev/raw/raw9 redo01.ora
[oracle @ suk1 oradata] $ ln-s / dev/raw/raw10 redo02.ora

5, to create a database to start dbca, the database option to create the next step, choose to create a customer database,
Next, enter the SID,
......
Next, the storage options page, select the bare equipment,
......
Next, in the choice of the parameters page, select the character set; initialization file init file to choose, at the same time in this interface click on "All Initialization Parameters" pop-up interface in the document change control parameters as follows:
Next, in this step, only the two control files, online log groups, confirmed that the corresponding table space data file names corresponding to just create a symbolic link; and to identify the creation of data files, log files than the corresponding bare equipment small (the sake of simplicity, unity is set to small 1M)
Next, create the database.

No unexpected events occur, some time after the completion of the database can be installed on.

Throughout the whole process naked equipment to create a database based on the most important step is planning for the bare device, if the bare equipment set is too large, a waste of space, if too small, the installation will fail.