# This file controls the state of SELinux on the system.\n# SELINUX= can take one of these three values:\n#\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 enforcing - SELinux security policy is enforced.\n#\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 permissive - SELinux prints warnings instead of enforcing.\n#\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 disabled - No SELinux policy is loaded.\nSELINUX=disabled\n# SELINUXTYPE= can take one of these two values:\n#\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 targeted - Targeted processes are protected,\n#\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 mls - Multi Level Security protection.\nSELINUXTYPE=targeted<\/pre>\nReboot the server and check if SELinux is down by using the following command:<\/p>\n
# \/usr\/sbin\/getenforce\nDisabled<\/pre>\nSELinux has to be disabled for both 11g and 12c installations.<\/p>\n
2) Network configuration<\/h4>\n
Address plan<\/strong>
\nYou need multiple IP addresses for your cluster.
\nEach node needs:<\/p>\n\n- An IP on the public network. This address corresponds to a network interface, and is used to allow the node to communicate on the network.<\/li>\n<\/ul>\n
\n- An IP on a private network, different subnet from the public one. It is also called Cluster Interconnect. This address corresponds to a second network interface. The Interconnect is a Network dedicated to communication between nodes and is not supposed to be accessible by other hosts not member of the cluster.<\/li>\n<\/ul>\n
\n- A virtual IP on the public network. The virtual IP is not really connected to the server, it does not appear in its network configuration. It is used for connection redundancy: if the node fails, its virtual IP is transferred on the leaving node and clients still can communicate with the cluster.<\/li>\n<\/ul>\n
You also need to configure up to three addresses on the public network for SCAN. The SCAN is a single name to access the cluster.
\nEach SCAN IP corresponds to a listener SCAN which redirects requests to nodes local listeners. Using this name, clients are not aware of the node on which database is running, and adding or removing a node in the cluster does not affect client connect configuration.
\nSCAN also provides failover and load balancing.
\nAs a summary, you need 9 IPs to create a two nodes cluster. IPs are described at next step.<\/p>\n
Name resolution<\/strong>
\nOnce IP addresses are defined, they must be resolvable by all nodes. Three options:<\/p>\n\n- Use of a local hosts file<\/li>\n<\/ul>\n
You may have something like this:<\/p>\n
127.0.0.1\u00a0\u00a0 localhost localhost.localdomain localhost4 localhost4.localdomain4\n::1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 localhost localhost.localdomain localhost6 localhost6.localdomain6\n192.168.100.1\u00a0\u00a0 \u00a0\u00a0 \u00a0 node01\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 node01.it.dbi-services.com<\/span>\n192.168.100.2 \u00a0\u00a0 \u00a0\u00a0\u00a0 node02 \u00a0\u00a0\u00a0 \u00a0 \u00a0\u00a0 node02.it.dbi-services.com<\/span>\n192.168.100.11 \u00a0\u00a0\u00a0\u00a0\u00a0 node01-vip \u00a0\u00a0\u00a0\u00a0 node01-vip.it.dbi-services.com<\/span>\n192.168.100.12 \u00a0\u00a0\u00a0\u00a0\u00a0 node01-vip \u00a0\u00a0\u00a0\u00a0 node02-vip.it.dbi-services.com<\/span>\n192.168.100.100\u00a0\u00a0\u00a0\u00a0\u00a0 cluster-scan\u00a0\u00a0\u00a0 cluster-scan.it.dbi-services.com<\/span><\/strong>\n192.168.200.1\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0 node01-priv\u00a0\u00a0\u00a0\u00a0 node01-priv.it.dbi-services.com<\/span>\n192.168.200.2 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 node02-priv\u00a0\u00a0\u00a0\u00a0 node02-priv.it.dbi-services.com<\/span><\/pre>\nImportant point: with local hosts file, you cannot use more than one IP for the SCAN because round robin is not available.<\/p>\n
\n- Use of a Domain Name Server<\/li>\n<\/ul>\n
In this case you have to create all addresses and hostnames on the DNS, and to enable round robin for SCAN addresses if you are using more that one address for the SCAN.
\nYou may have following entries in your DNS zone file:<\/p>\n
node01.it.dbi-services.com\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 IN A 192.168.100.1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>\nnode02.it.dbi-services.com\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 IN A 192.168.100.2 \u00a0\u00a0\u00a0 \u00a0 \u00a0\u00a0 <\/span>\nnode01-vip.it.dbi-services.com\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 IN A 192.168.100.11 \u00a0\u00a0\u00a0\u00a0 <\/span>\nnode02-vip.it.dbi-services.com\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 IN A 192.168.100.12<\/span>\ncluster-scan.it.dbi-services.com \u00a0\u00a0\u00a0 IN A 192.168.100.100<\/span>\n\u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 IN A 192.168.100.101<\/span>\n\u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 IN A 192.168.100.102\u00a0\u00a0\u00a0<\/span> \nnode01-priv.it.dbi-services.com\u00a0\u00a0\u00a0\u00a0\u00a0 IN A 192.168.200.1\u00a0\u00a0\u00a0\u00a0 <\/span>\nnode02-priv.it.dbi-services.com\u00a0\u00a0\u00a0\u00a0\u00a0 IN A 192.168.200.2\u00a0<\/span>\u00a0\u00a0\u00a0<\/code><\/pre>\n
\n<\/span><\/span><\/span><\/span><\/span><\/span><\/code><\/p>\n\n- Use of Oracle GNS – Grid Naming Service<\/li>\n<\/ul>\n
GNS was introduced with Grid Infrastructure 11.2 and provides dynamics DHCP addresses for SCAN and Virtual IPs. I will not detail this service in this blog, just know that it exists. For more information, you can consult Oracle documentation.<\/p>\n
We are going to use a DNS Server to resolve names and IPs.<\/p>\n
A word about SCAN<\/strong>
\nThe following schema gives an overview of the interconnection of a two nodes cluster:<\/p>\n![\"GridInfra\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/GridInfra.png\")
<\/p>\n
3) Users and groups<\/h4>\n\n- rdbms package<\/strong><\/li>\n<\/ul>\n
Download the rdbms preinstall package\u00a0 from the public repository or ULN. The package is in the latest yum repository (el6_latest or ol5_latest). You must enable it. For Oracle Linux 6, use the following command:<\/p>\n
# yum install oracle-rdbms-server-12cR1-preinstall<\/pre>\nThis package will automatically download required packages or libraries, create users and groups… It avoids fastidious configuration steps.
\nHowever, it does not everything. Some facultative oracle groups are not created by the package. This is the case for oper, and for the three new Oracle 12c groups backupdba, dgdba and kmdba.
\nMore, this package makes the system ready for rdbms installation only, meaning that all pre requisites for Grid Infrastructure are not automatically set.
\nNote that since Oracle 12c, the package does not edit the file \/etc\/security\/limits.conf<\/strong> anymore. Ulimits must be specified by hand.<\/p>\n\n- Groups creation<\/strong><\/li>\n<\/ul>\n
Database groups<\/strong>
\nThe following groups are not created by the rdbms package, and must be created manually:<\/p>\n# \/usr\/sbin\/groupadd -g 54323 oper\n# \/usr\/sbin\/groupadd -g 54327 backupdba\n# \/usr\/sbin\/groupadd -g 54328 dgdba\n# \/usr\/sbin\/groupadd -g 54329 kmdba<\/pre>\nAsm groups<\/strong>
\nSince the rdbms preinstall package is dedicated to Oracle RDBMS install, all pre requisites for Grid Infrastructure and ASM must be set manually. This includes the three following groups:<\/p>\n# \/usr\/sbin\/groupadd -g 54324 asmadmin\n# \/usr\/sbin\/groupadd -g 54325 asmdba\n# \/usr\/sbin\/groupadd -g 54326 asmoper<\/pre>\n
\n- Users creation and modification<\/strong><\/li>\n<\/ul>\n
The user oracle was already created by the rdbms preinstall package with oinstall and dba groups. But it is not member of all newly created groups.
\nMore, it has no rights for ASM, and is not able to see ASM disks to create a database. For that, the oracle user needs the asmdba group. You can drop and recreate the user, or just alter its parameters with this command:<\/p>\n
# \/usr\/sbin\/usermod -g oinstall -G dba,backupdba,dgdba,kmdba,oper,asmdba oracle<\/code><\/pre>\nGrid Infrastructure needs a software owner, member of oinstall, which is not created by the rdbms preinstall package. It is advised to create a dedicated user:<\/p>\n
# \/usr\/sbin\/useradd -u 54322 -g oinstall -G asmadmin,asmdba,asmoper grid<\/pre>\nDo not forget to specify password for both oracle and grid users:<\/p>\n
# passwd oracle\n# passwd grid<\/pre>\n
\n- SSH<\/strong><\/li>\n<\/ul>\n
The OUI (Oracle Universal Installer) is run on one node, and uses SSH and scp commands to run command and copy files on remote nodes during the install. SSH must be configured on all members of the cluster to avoid each command to prompt for a password. This configuration can be done during install process, with the OUI, or with a script provided by Oracle and available in \/software\/grid\/sshsetup<\/strong>.<\/p>\nTo make it with the script, connect as root on node01 and run the script as follow for both oracle and grid accounts:<\/p>\n
# .\/sshUserSetup.sh -user grid -hosts \"node01 node02\" -advanced -exverify \u2013noPromptPassphrase\n# .\/sshUserSetup.sh -user oracle -hosts \"node01 node02\" -advanced -exverify \u2013noPromptPassphrase<\/pre>\n <\/p>\n
The script will check connectivity between all node listed, and will ask for password twice for each node. Once configuration done, no password will be asked to establish a ssh connection in the future.<\/p>\n
SSH connectivity is checked for both 11g and 12c installations.<\/p>\n
4) Directory structure<\/h4>\n
Once users and groups are created, Oracle directories can be created, using the OFA standard:<\/p>\n
# mkdir -p \/u00\/app\/12.1.0\/grid\n# mkdir -p \/u00\/app\/grid\n# mkdir -p \/u00\/app\/oracle\n# chown -R grid:oinstall \/u00\/app\n# chown -R oracle:oinstall \/u00\/app\/oracle\n# chmod -R 775 \/u00\/app<\/pre>\n5) Ulimits settings<\/h4>\n
In Oracle 11g, the file \/etc\/security\/limits.conf<\/strong> was automatically configured by the rdbms preinstall package for the oracle user. We only had to copy \/ paste values from oracle to grid user.<\/p>\nIn Oracle 12c, the rdbms preinstall package does not configure ulimits. We must edit \/etc\/security\/limits.conf and set ulimits for oracle and grid users according to the Oracle documentation.<\/p>\n
# Setting for nofile soft limit is 1024\noracle\u00a0\u00a0 soft\u00a0\u00a0 nofile\u00a0\u00a0 1024\ngrid\u00a0\u00a0\u00a0\u00a0 soft\u00a0\u00a0 nofile\u00a0\u00a0 1024<\/pre>\n <\/p>\n
# Setting for nofile hard limit is 65536\noracle\u00a0\u00a0 hard\u00a0\u00a0 nofile\u00a0\u00a0 65536\ngrid\u00a0\u00a0\u00a0\u00a0 hard\u00a0\u00a0 nofile\u00a0\u00a0 65536<\/pre>\n <\/p>\n
# Setting for nproc soft limit is 2047\noracle\u00a0\u00a0 soft\u00a0\u00a0 nproc\u00a0\u00a0 2047\ngrid\u00a0\u00a0\u00a0\u00a0 soft\u00a0\u00a0 nproc\u00a0\u00a0 2047<\/pre>\n <\/p>\n
# Setting for nproc hard limit is 16384\noracle\u00a0\u00a0 hard\u00a0\u00a0 nproc\u00a0\u00a0 16384\ngrid\u00a0\u00a0\u00a0\u00a0 hard\u00a0\u00a0 nproc\u00a0\u00a0 16384<\/pre>\n <\/p>\n
# Setting for stack soft limit is 10240\noracle\u00a0\u00a0 soft\u00a0\u00a0 stack\u00a0\u00a0 10240\ngrid\u00a0\u00a0\u00a0\u00a0 soft\u00a0\u00a0 stack\u00a0\u00a0 10240<\/pre>\n <\/p>\n
# Setting for stack hard limit is 32768\noracle\u00a0\u00a0 hard\u00a0\u00a0 stack\u00a0\u00a0 32768\ngrid\u00a0\u00a0\u00a0\u00a0 hard\u00a0\u00a0 stack\u00a0\u00a0 32768<\/pre>\nValues for ulimit are the same for both Oracle 11g and Oracle 12c releases.<\/p>\n
6) ASM disks and diskgroups<\/h4>\n\n- ASM packages<\/strong><\/li>\n<\/ul>\n
To use Oracle ASM, two or three packages are required, depending on the situation. Here, we consider using ASMLib instead of Raw devices. So three packages will be required:<\/p>\n
\n- oracleasm-support<\/li>\n
- oracleasmlib<\/li>\n
- the driver oracle asm<\/li>\n<\/ul>\n
Download oracleasm-support from the repository:<\/p>\n
# yum install oracleasm-support<\/pre>\nThen, download oracleasmlib from the Oracle website and install it manually.<\/p>\n
# wget http:\/\/download.oracle.com\/otn_software\/asmlib\/oracleasmlib-2.0.4-1.el6.x86_64.rpm\n# rpm -iv oracleasmlib-2.0.4-1.el6.x86_64.rpm<\/pre>\nNote that this oracleasmlib package is for 64 bits system. It also exists for 32 bits systems.<\/p>\n
For the last package, it depends of your kernel. If your server is configured with the default Unbreakable Enterprise Kernel (UEK), the driver is already compiled in the kernel. If you are using the Red Hat compatible kernel, you must install the following package (for Oracle Linux 6):<\/p>\n
# yum install kmod-oracleasm<\/pre>\n <\/p>\n
For Oracle Linux 5, install the package corresponding to your kernel version:<\/p>\n
# yum install oracleasm-`uname -r`<\/pre>\n
\n- ASM disks<\/strong><\/li>\n<\/ul>\n
Database and cluster files will be stored in ASM disks. In order to create ASM disks, we must prepare available disks.
\nWe choosed to create 3 disks for CRS and 2 for data and FRA.<\/p>\n
Available disks are:<\/p>\n
\/dev\/sdb\n\/dev\/sdc\n\/dev\/sdd\n\/dev\/sde\n\/dev\/sdf<\/pre>\nUse the command fdisk to prepare disks from one node. Example for sdb:<\/p>\n
# fdisk \/dev\/sdb\nCommand (m for help): n\nCommand action\n\u00a0\u00a0 e\u00a0\u00a0 extended\n\u00a0\u00a0 p\u00a0\u00a0 primary partition (1-4)\np\nPartition number (1-4): 1\nFirst cylinder (1-1305, default 1):\nUsing default value 1\nLast cylinder or +size or +sizeM or +sizeK (1-1305, default 1305):\nUsing default value 1305Command (m for help): w\nThe partition table has been altered!\nCalling ioctl() to re-read partition table.<\/pre>\n
\n- Configure ASM<\/strong><\/li>\n<\/ul>\n
Once all disks are ready, you can create ASM disks. First, configure ASM on both nodes:<\/p>\n
# \/usr\/sbin\/oracleasm configure -i \nConfiguring the Oracle ASM library driver.<\/pre>\nThis will configure the on-boot properties of the Oracle ASM library \ndriver.\u00a0 The following questions will determine whether the driver is \nloaded on boot and what permissions it will have.\u00a0 The current values \nwill be shown in brackets ('[]').\u00a0 Hitting without typing an \nanswer will keep that current value.\u00a0 Ctrl-C will abort.\nDefault user to own the driver interface []: grid \nDefault group to own the driver interface []: asmadmin \nStart Oracle ASM library driver on boot (y\/n) [n]: y \nScan for Oracle ASM disks on boot (y\/n) [y]: y\nWriting Oracle ASM library driver configuration: done<\/pre>\nThen, initialize ASM module on both nodes:<\/p>\n
# \/usr\/sbin\/oracleasm init \nCreating \/dev\/oracleasm mount point: \/dev\/oracleasm \nLoading module \"oracleasm\": oracleasm \nMounting ASMlib driver filesystem: \/dev\/oracleasm<\/pre>\n
\n- Create ASM disks<\/strong><\/li>\n<\/ul>\n
Create ASM disks from one node:<\/p>\n
# oracleasm createdisk CRSFG1D1 \/dev\/sdb1\n# oracleasm createdisk CRSFG2D1 \/dev\/sdc1\n# oracleasm createdisk CRSFG3D1 \/dev\/sdd1\n# oracleasm createdisk U01FG1D1 \/dev\/sde1\n# oracleasm createdisk U90FG1D1 \/dev\/sdf1<\/pre>\nI choosed to name the failer groups U01* for database files, and U90* for the Flash Recovery Area, according to the OFA modele and our best practices.<\/p>\n
From the second node, scan ASM disks:<\/p>\n
# oracleasm scandisks\nReloading disk partitions: done\nCleaning any stale ASM disks...\nScanning system for ASM disks...\nInstantiating disk \"CRSFG1D1\"\nInstantiating disk \"CRSFG2D1\"\nInstantiating disk \"CRSFG3D1\"\nInstantiating disk \"U01FG1D1\"\nInstantiating disk \"U90FG1D1\"<\/pre>\nThen use the oracleasm listdisks command to see if ASM disks are all present on both nodes:<\/p>\n
# oracleasm listdisks\nCRSFG1D1\nCRSFG2D1\nCRSFG3D1\nU01FG1D1\nU90FG1D1<\/pre>\n
\n- Create ASM diskgroups<\/strong><\/li>\n<\/ul>\n
We need diskgroups for the cluster itself (voting disks), and for the database.<\/p>\n
\n- ASM diskgroups for CRS will be created during Grid Infrastructure deployment, in the step 11 of the OUI.<\/li>\n
- ASM diskgroups for DATA and FRA cannot be created if ASM is not already installed, because we must connect to the ASM instance. Those diskgroups will be created later, after having installed Grid Infrastructure. This step will be detailed in my future blog about the Grid Infrastructure binaries installation.<\/li>\n<\/ul>\n
7) Validation: cluvfy tool<\/h4>\n
Cluvfy is a tool provided by Oracle. It checks all software and hardware pre requisites on each node to make sure the install can be done. This tool is called before installing grid infrastructure, before adding a node, or before adding a database.<\/p>\n
Here, we want to be sure that our two nodes are ready to deploy Grid Infrastructure for a cluster environment. Locate the script in \/software\/grid and run it as grid user with following options from node01:<\/p>\n
$ \/software\/grid\/runcluvfy.sh stage -pre crsinst -osdba asmdba -orainv oinstall -n node01,node02 -r 12.1 -fixup -verbose > \/tmp\/cluvfy_output.log<\/pre>\n
\n- -osdba is for the SYSDBA role for asm<\/li>\n
- -orainv is for the OINSTALL role for asm (the owner of the software)<\/li>\n
- -n is for the nodes list<\/li>\n
- -r is for the release<\/li>\n
- -verbose is to display details for each check<\/li>\n
- -fixup is to fix automatically failed pre requisites, if possible. For example:<\/li>\n<\/ul>\n
Fix: OS Kernel Parameter: swappiness\n\u00a0 Node Name\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Status\n\u00a0 ------------------------------------\u00a0 ------------------------\n\u00a0 vmtestrac12c2\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 successful\n\u00a0 vmtestrac12c1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 successful\nResult: \"OS Kernel Parameter: swappiness\" was successfully fixed on all the applicable nodes\nFix up operations were successfully completed on all the applicable nodes.<\/pre>\nAfter cluvfy has stopped running, look for a “failed” keyword in the logfile. If all parameters have “passed” status on all nodes, you should get the following sentence in the cluvfy logfile:<\/p>\n
Pre-check for cluster services setup was successful on all the nodes.<\/pre>\nIt means that you are ready to start your installation. You can run the OUI and deploy Grid Infrastructure on the two nodes. Enjoy!
\nIn one of my next blog posting, I will go onto the details of the installation procedure and show you some new features in the OUI of Grid Infrastructure 12c.<\/p>\n","protected":false},"excerpt":{"rendered":"
Grid infrastructure 12c has recently been released. In this posting, I will show that the installation prerequisites are quite similar between Grid Infrastructure 11g and 12c. We will see parts of them during a review for the deployment of Grid Infrastructure on a two nodes RAC database cluster. Server hardware requirements Let’s see the hardware […]<\/p>\n","protected":false},"author":27,"featured_media":2734,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[42],"tags":[258,101,209],"type_dbi":[],"class_list":["post-2771","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-operating-systems","tag-grid","tag-installation","tag-oracle-12c"],"acf":[],"yoast_head":"\n
Oracle Grid Infrastructure 12c: prerequisites for installation - dbi Blog<\/title>\n<meta name=\"description\" content=\"Grid infrastructure 12c has recently been released. In this posting, I will show that the installation prerequisites are quite similar between Grid Infrastructure 11g and 12c. We will see parts of them during a review for the deployment of Grid Infrastructure on a two nodes RAC database cluster.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Oracle Grid Infrastructure 12c: prerequisites for installation\" \/>\n<meta property=\"og:description\" content=\"Grid infrastructure 12c has recently been released. In this posting, I will show that the installation prerequisites are quite similar between Grid Infrastructure 11g and 12c. We will see parts of them during a review for the deployment of Grid Infrastructure on a two nodes RAC database cluster.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2013-09-18T23:05:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_Oracle_12c_Plug.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"200\" \/>\n\t<meta property=\"og:image:height\" content=\"209\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Oracle Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Oracle Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"16 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/\"},\"author\":{\"name\":\"Oracle Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"headline\":\"Oracle Grid Infrastructure 12c: prerequisites for installation\",\"datePublished\":\"2013-09-18T23:05:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/\"},\"wordCount\":2311,\"commentCount\":0,\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_Oracle_12c_Plug.jpg\",\"keywords\":[\"Grid\",\"Installation\",\"Oracle 12c\"],\"articleSection\":[\"Operating systems\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/\",\"name\":\"Oracle Grid Infrastructure 12c: prerequisites for installation - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_Oracle_12c_Plug.jpg\",\"datePublished\":\"2013-09-18T23:05:00+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"description\":\"Grid infrastructure 12c has recently been released. In this posting, I will show that the installation prerequisites are quite similar between Grid Infrastructure 11g and 12c. We will see parts of them during a review for the deployment of Grid Infrastructure on a two nodes RAC database cluster.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/#primaryimage\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_Oracle_12c_Plug.jpg\",\"contentUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_Oracle_12c_Plug.jpg\",\"width\":200,\"height\":209},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Oracle Grid Infrastructure 12c: prerequisites for installation\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\",\"name\":\"Oracle Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"caption\":\"Oracle Team\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/oracle-team\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Oracle Grid Infrastructure 12c: prerequisites for installation - dbi Blog","description":"Grid infrastructure 12c has recently been released. In this posting, I will show that the installation prerequisites are quite similar between Grid Infrastructure 11g and 12c. We will see parts of them during a review for the deployment of Grid Infrastructure on a two nodes RAC database cluster.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/","og_locale":"en_US","og_type":"article","og_title":"Oracle Grid Infrastructure 12c: prerequisites for installation","og_description":"Grid infrastructure 12c has recently been released. In this posting, I will show that the installation prerequisites are quite similar between Grid Infrastructure 11g and 12c. We will see parts of them during a review for the deployment of Grid Infrastructure on a two nodes RAC database cluster.","og_url":"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/","og_site_name":"dbi Blog","article_published_time":"2013-09-18T23:05:00+00:00","og_image":[{"width":200,"height":209,"url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_Oracle_12c_Plug.jpg","type":"image\/jpeg"}],"author":"Oracle Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Oracle Team","Est. reading time":"16 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/"},"author":{"name":"Oracle Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"headline":"Oracle Grid Infrastructure 12c: prerequisites for installation","datePublished":"2013-09-18T23:05:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/"},"wordCount":2311,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_Oracle_12c_Plug.jpg","keywords":["Grid","Installation","Oracle 12c"],"articleSection":["Operating systems"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/","url":"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/","name":"Oracle Grid Infrastructure 12c: prerequisites for installation - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_Oracle_12c_Plug.jpg","datePublished":"2013-09-18T23:05:00+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"description":"Grid infrastructure 12c has recently been released. In this posting, I will show that the installation prerequisites are quite similar between Grid Infrastructure 11g and 12c. We will see parts of them during a review for the deployment of Grid Infrastructure on a two nodes RAC database cluster.","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_Oracle_12c_Plug.jpg","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_Oracle_12c_Plug.jpg","width":200,"height":209},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-12c-prerequisites-for-installation\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Oracle Grid Infrastructure 12c: prerequisites for installation"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee","name":"Oracle Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","caption":"Oracle Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/oracle-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/2771","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/27"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=2771"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/2771\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media\/2734"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=2771"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=2771"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=2771"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=2771"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_Oracle_12c_Plug.jpg\")
<\/p>\n