Oracle Cluster physical configuration requirements and restrictions

Oracle Cluster physical configuration requirements and restrictions

1. Oracle Clusterware supports up to 100 nodes in a cluster on deployments running Oracle Database 10 grelease 2 (10.2) and later releases.
 
In Versions later than 10.2, oracle clusters support clusters with a maximum of GB nodes.

2. Network Configuration:
Each node has at least two NICs (one for a public network and one for a private network)
Oracle does not support direct connection between cluster nodes.

Oracle Clusterware 11g release 2 (11.2) supports the use of dynamic host configuration protocol (DHCP) for the VIP addresses and the SCAN address, but not the public address.
 
Vip is supported after 11.2, scan ip uses dhcp, but public ip is not supported

3. Storage Configuration:
Oracle Clusterware supports NFS, iSCSI, Direct Attached Storage (DAS), Storage Area Network (SAN) storage, and Network Attached Storage (NAS ).
 
Ocr recommended redundancy = 5
Voting disk suggest 5; support up to 15

Voting disk supports up to 15 Disks

The voting disk files, which record node membership information,
And the Oracle Cluster Registry (OCR), which records cluster configuration information, information about the components that Oracle Clusterware controls, such as Oracle RAC databases, listeners, virtual IP addresses (VIPs ), and services and any applications.
 
Voting disk records node member information.
 
Ocr records the configuration information of the black silk cluster, such as the components controlled by the cluster: database, listener, vip, service, and other applications.

4. Cluster, asm, rdbms. compatibility issues
 
Oracle ASM release 11.2 requires OracleClusterware release 11.2 and supports
Oracle Database 11 grelease 2 (11.2), release 1 (11.1), Oracle Database 10g release 2 (10.2), and release 1 (10.1)
 
11.2 of asm requires a cluster of> = 11.2, but the supported databases can be 11.2, 11.1, 10.2, 10.1
 

5. ---- two configuration and management tools, oracle cluster
Server Control (SRVCTL): SRVCTL is a command-line interface that you can use to manage Oracle resources, such as databases, services, or listeners in the cluster.
 
Srvclt can be used to manage oracle resources such as databases, services, and listeners.

Oracle Clusterware Control (CRSCTL): CRSCTL is a command-line tool that you can use to manage Oracle Clusterware. CRSCTL shocould be used for general clusterware management and management of individual resources.
 
Crsctl manages cluster-level tools to manage the entire cluster or individual cluster resources.

The commands issued by the preceding two tools are valid for all nodes in the cluster. You can issue commands on any node in the cluster to control and configure cluster or rac resources.

Installing Oracle 12C in Linux-6-64

Install Oracle 11gR2 (x64) in CentOS 6.4)

Steps for installing Oracle 11gR2 in vmwarevm

Install Oracle 11g XE R2 In Debian