| |
This article is only used to record some of the problems occurring in peacetime record Oracle RAC installation process, if you encounter later also added in small details.
1. HAIP hosts file double Intranet card configuration examples:
# Vi / etc / hosts
127.0.0.1 localhost.localdomain localhost
192.168.0.6 db1
192.168.0.7 db2
192.168.0.8 db1-vip
192.168.0.9 db2-vip
10.10.10.10 db1-priv1
20.20.20.10 db1-priv2
10.10.10.20 db2-priv1
20.20.20.20 db2-priv2
2. Configure multiple NIC teaming (optional feature)
Explanation:
(1) do bind to two ports on the same switch, server configuration can be configured as follows, first prompted to load the bonding kernel.
(2) on the server two network cards are on two different access switches, it can only be used standby mode, the personal feeling of instability factors, such as mandatory to manually configure the gateway.
Two network cards (3) are respectively connected to a server switch, configure the switch if you do not bind mode, using only standby mode.
(4) Oracle 11.2.0.2 RAC later version supports up to four high-performance intranet Katy, no binding, according to the circumstances appropriate multi-card deployment.
3. Oracle 11g RAC iptables configuration database is generally not the original configuration of the firewall, but the configuration requirements of a variety of factors, hard to find a foreign article a configuration, the application installation practices and no problems.
iptables -P OUTPUT ACCEPT
iptables -A INPUT -i lo -j ACCEPT
iptables -A INPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
iptables -A INPUT -p tcp -m tcp --dport 22 -j ACCEPT
iptables -A INPUT -m state --state NEW -m tcp -p tcp -s 192.168.0.0/24 --dport 1521 -j ACCEPT
iptables -A INPUT -p all -m state --state ESTABLISHED, RELATED -j ACCEPT
iptables -A INPUT -s 192.168.0.6/32 -i eth0 -j ACCEPT
iptables -A INPUT -s 192.168.0.7/32 -i eth0 -j ACCEPT
iptables -A INPUT -s 192.168.0.8/32 -i eth0 -j ACCEPT
iptables -A INPUT -s 192.168.0.9/32 -i eth0 -j ACCEPT
iptables -A INPUT -s 192.168.0.10/32 -i eth0 -j ACCEPT
iptables -A INPUT -i eth1 -j ACCEPT
iptables -A INPUT -i eth2 -j ACCEPT
iptables -A INPUT -s 10.10.10.0/24 -d 230.0.1.0 -j ACCEPT
iptables -A INPUT -s 10.10.10.0/24 -d 224.0.0.251 -j ACCEPT
iptables -A INPUT -s 20.20.20.0/24 -d 230.0.1.0 -j ACCEPT
iptables -A INPUT -s 20.20.20.0/24 -d 224.0.0.251 -j ACCEPT
iptables -A INPUT -i eth0 -d 230.0.1.0 -j ACCEPT
iptables -A INPUT -i eth0 -d 224.0.0.251 -j ACCEPT
iptables -A INPUT -p all -m state --state INVALID, NEW -j DROP
iptables -P INPUT DROP
service iptables save
4. For Linux 6.x platform, may be found in limits.conf file to modify the parameters nproc will be ignored.
# Vi /etc/security/limits.d/90-nproc.conf
# Modified to achieve the following restrictions on the nproc:
* Soft nproc 16384
root soft nproc unlimited
5. Close the THP
On RedHat6, OEL6, SLES 11 or UEK2 kernel, make sure to close THP (Transparent HugePages) to prevent performance issues leading to the expulsion of nodes and instances.
Reference documents:
ALERT Disable Transparent HugePages on SLES11 RHEL6 OEL6 and UEK2 Kernels (Doc ID 1557478.1)
# Vi /etc/rc.local
echo never> / sys / kernel / mm / transparent_hugepage / enabled
echo never> / sys / kernel / mm / transparent_hugepage / defrag
6. Configure shared storage ESXi5.1
VMware ESXi 5.1 installation RHEL6.5 11G RAC, virtual machine disk storage as a shared disk. Explain the need to pay attention.
Parallel SCSI controller selects the LIS Logic, select the type of "virtual", "virtual" disk can be shared on the same server, virtual disk device node select 1: 1, 1: 2 and so on, there is added 6 shared disk.
After you create a disk node1, node2 select an existing disk, select the path to add.
Add the following statement in node1, and node2 the vmx configuration file, otherwise you can not get the disk UUID
disk.enableUUID = "TRUE"
Description: This personal feeling environment stability is not high, set up a test environment with the use okay, there have been problems somehow, did not use a reliable shared storage.
7. EMC storage udev udev configure ASM disk configuration file example
EMC storage udev configuration file format is not the same, at least with IBM and other storage is not the same, so the record here in particular, the need to add a directory on /etc/udev/rules.d 50-udev.rules file, redhat 5 below there this document, to redhat 6 gone down, and the following information is added to 50-udev.rules, can now be properly installed on the oracle asm
vi /etc/udev/rules.d/50-udev.rules
SUBSYSTEM == "block", KERNEL == "emcpowera1", GROUP = "asmadmin", OWNER = "grid", MODE = "0660"
SUBSYSTEM == "block", KERNEL == "emcpowerb1", GROUP = "asmadmin", OWNER = "grid", MODE = "0660"
SUBSYSTEM == "block", KERNEL == "emcpowerc1", GROUP = "asmadmin", OWNER = "grid", MODE = "0660"
SUBSYSTEM == "block", KERNEL == "emcpowerd1", GROUP = "asmadmin", OWNER = "grid", MODE = "0660"
SUBSYSTEM == "block", KERNEL == "emcpowere1", GROUP = "asmadmin", OWNER = "grid", MODE = "0660"
SUBSYSTEM == "block", KERNEL == "emcpowerf1", GROUP = "asmadmin", OWNER = "grid", MODE = "0660"
SUBSYSTEM == "block", KERNEL == "emcpowerg1", GROUP = "asmadmin", OWNER = "grid", MODE = "0660"
SUBSYSTEM == "block", KERNEL == "emcpowerh1", GROUP = "asmadmin", OWNER = "grid", MODE = "0660"
SUBSYSTEM == "block", KERNEL == "emcpoweri1", GROUP = "asmadmin", OWNER = "grid", MODE = "0660"
SUBSYSTEM == "block", KERNEL == "emcpowerj1", GROUP = "asmadmin", OWNER = "grid", MODE = "0660"
SUBSYSTEM == "block", KERNEL == "emcpowerk1", GROUP = "asmadmin", OWNER = "grid", MODE = "0660" |
|
|
|