ORACLE11gr2RAC installation Implementation Plan

It is not difficult to install RAC. It is difficult to implement the plan in the early stage. After the hardware is purchased according to the user's requirements, we should make a detailed plan before implementation, this includes host planning, SAN Switch planning, storage cabinet planning, OR

It is not difficult to install RAC. It is difficult to implement the plan in the early stage. After the hardware is purchased according to the user's requirements, we should make a detailed plan before implementation, this includes host planning, SAN Switch planning, storage cabinet planning, OR

It is not difficult to install RAC. It is difficult to implement the plan in the early stage. After the hardware is purchased according to the user's requirements, we should make a detailed plan before implementation, this includes host planning, SAN Switch planning, storage cabinet planning, and ORACLE database software planning. The entire software and hardware should be integrated to fully consider the security, reliability, availability, and other factors of the RAC system, always remember that a well-planned RAC system can make full use of its advantages over a single node, while also providing convenience for later O & M management. This blog post mainly provides reference for the early implementation of RAC planning.

Network Topology

I. Host Planning

System Configuration

Hard Disk: 6*300G 15 krpm SAS

Memory: GB memory

CPU: 4*8 core E7-4830 2.13 GHZ

Quantity

2

RAID level

RAID10

Operating system version

RHEL6.4 _ X86_64

Host Name

Node1 and node2

Nic Configuration

Eth1 \ Eth3 is used for business networks and uses bind0 of Active/standby.

Eth2 \ Eth4 is used for the heartbeat network of the cluster and uses bind1 of Active/standby.

IP address

Node1

PublicIP: 192.168.0.1

VIP: 192.168.0.10

PrivateIP: 10.0.0.1

Node2

PublicIP: 192.168.0.2

VIP: 192.168.0.10

PrivateIP: 10.0.0.2

SCAN-IP

192.168.0.63

Gateway

192.168.0.62

Local disk

/Boot

Start partition 500 M

Swap

Swap partition 64 GB

/

Remaining space in the root Partition

/U01

Oracle Database Software partition 100 GB

Multi-path Software

RDAC

Ii. SAN1 switch ZONE planning

System Configuration

24 ports, 8 active ports, 8 8 8 gb sfp modules

Zone name

Corresponding Port

Channel description

Port description

0

Connection to the storage master A port

1

Connect to the Master B port of the storage

2

Connect to NODE1

3

Connect to NODE2

Zone_a

0/1/2

Connect NODE1 to storage

Zone_ B

0/1/3

Connect NODE2 to storage

Other zones

Remaining Port

Unallocated

SAN2 switch ZONE planning

System Configuration

24 ports, 8 active ports, 8 8 8 gb sfp modules

Zone name

Corresponding Port

Channel description

Port description

0

Connect to the storage's backup control port

1

Backup control port B connected to storage

2

Connect to NODE1

3

Connect to NODE2

Zone_a

0/1/2

Connect NODE1 to storage

Zone_ B

0/1/3

Connect NODE2 to storage

Other zones

Remaining Port

Unallocated

NOTE: For the SAN Switch ZONE plan, remember that the 1.1 SAN switches correspond to one controller. Therefore, you can calculate that each volume has four paths for storage.

Iii. Disk Array volume Planning

System Configuration

Hard Disk: 10*600G 15 krpm SAS, 48G memory FC port: 8*8 Gb FC

Software: multi-path Software

Quantity

1 unit

Manage IP addresses

192.168.1.57

RAID level

The nine disks are RAID-5, and the remaining one is hot standby.

Strip size

1 M

LUN

LUN1

1G, OCR disk group

LUN2

1G, OCR disk group

LUN3

1G, OCR disk group

LUN4

1 TB, DATA_DG disk, which stores database files

LUN5

1 TB, DATA_DG disk, which stores database files

LUN6

1 TB, DATA_DG disk, which stores database files

LUN7

1 TB, FLASH_DG disk group, storing database files

LUN8

386 GB, disk group, storing database files

4. ORACLE database software planning

1. Network Planning

Node

Project

IP address

Domain Name

Host Name

Node1

Service IP Address

192.168.100.1

Node1.localdomain

Node1

Virtual IP Address

192.168.100.10

Node1-vip. localdomain

Node1-vip

Private IP

10.0.0.1

Node1-priv. localdomain

Node1-priv

Node2

Service IP Address

192.168.100.2

Node2.localdomain

Node2

Virtual IP Address

192.168.100.11

Node2-vip. localdomain

Node2-vip

Private IP

10.0.0.2

Node2-priv. localdomain

Node2-priv

SCAN IP

192.168.100.15

Scan-cluster.localdomain

Scan-cluster

2. oracle Planning

Software Version

ORACLE 11.2.0.4 EE

RAC?

Yes

ORACLE_SID

Node1

Devdb1

+ ASM1

Node2

Devdb2

+ ASM2

Key environment variables of oracle users

(Node2)

ORACLE_UNQNAME = devdb

ORACLE_SID = devdb2

ORACLE_BASE =/u01/app/oracle

ORACLE_HOSTNAME = devdb2.localdomain

ORACLE_HOME =/u01/app/oracle/product/11.2.0/db_1

Key environment variables of grid users

(Node2)

ORACLE_SID = + ASM2

ORACLE_BASE =/u01/app/grid

ORACLE_HOME =/u01/app/11.2.0/grid

Users and groups

Oracle: oinstall, asmdba, dba, role

Grid: oinstall, asmadmin, asmdba, asmoper, dba

Memory Allocation

AMM management mode, SGA + PGA = 64 GB

ASM Planning

GRIDDG (VOL1, VOL2, VOL3)

OCR \ vote disk group, NORMAL Redundancy

DATADG (VOL4)

Database data disk group, EXTERNAL Redundancy

FLASHDG (VOL7)

Data flash back and archiving logs

Remaining asm disks (VOL5, VOL6, and VOL8)

Can be allocated as needed

Database initialization parameters

Processes

1000

Open_cursors

1000

Session_cached_cursors

100

Db_recovery_file_dest_size

900 GB

Undo_retention

10800

NLS_CHARACTERSET

ZHS16GBK

NLS_NCHAR_CHARACTERSET

AL16UTF16

Archive path

+ FLASHDG

Access Port

1521

Tablespace

SYSTEM

SYSAUX

UNDO

TEMP

QZDATA

Business table data table space, set as needed, disable automatic expansion feature, 8 GB per data file

Run the following command to increase the tablespace size:

Alter tablespace qzdata add datafile size 8G;

QZINDX

Service index data table space, set as needed, disable automatic expansion feature, 8 GB per data file

Run the following command to increase the tablespace size:

Alter tablespace qzindx add datafile size 8G;

Other tablespaces

Set as needed to disable auto scaling. Each data file is 8 GB.

V. installation script

To facilitate implementation and reduce human errors in the implementation process, it is necessary to compile some scripts to help implementation. six small scripts are included, which are modified according to actual requirements and executed in sequence.

This article is from the "Qingfeng Wanfeng" blog. Please keep this source