The following tables provide lists of basic system requirements to check.
This list is not comprehensive for all deployment options. For more specific details about these checks, and other configuration information, see Chapter 3 through Chapter 7.
If you are experienced with installing Oracle components in Linux or UNIX environments, then note that many manual setup tasks required on Linux or UNIX are not required on Windows.
The key differences between Linux or UNIX and Windows installations are:
Startup and shutdown services
With Windows, you log in to a user account with Administrator privileges to install the Oracle Database software. You can also specify an Oracle Home User (based on a standard non-administrative Windows user account) during installation. On Linux and UNIX systems, you must create and use a software owner user account, and this user must belong to the Oracle Inventory group.
On Windows systems, Oracle Universal Installer (OUI) sets environment variables such as
ORACLE_SID in the registry. On Linux and UNIX systems, you must manually set these environment variables.
If you have multiple Oracle databases in an Oracle home, then only the SID of the last Oracle database is set in the registry. See Oracle Universal Installer and OPatch User's Guide for Windows and UNIX for more information about managing Oracle homes.
Operating System Groups
On Windows systems, OUI creates the
ORA_HOMENAME_OPER groups, which are used for operating system authentication for Oracle instances. On Linux and UNIX systems, you must create the operating system groups manually.
Account for running Oracle Universal Installer (OUI)
With Windows, you log in to a user account with Administrator privileges to install the Oracle Database software. You can also specify an Oracle Home User (based on a standard non-administrative Windows User Account) during installation. On Linux and UNIX systems, you must create and use a software owner user account, and this user must belong to the Oracle Inventory group.
See Also:"Oracle Database Differences on Windows and UNIX," in Oracle Database Platform Guide for Microsoft Windows
Review the following hardware checklist for all installations:
Table 1-1 Server Hardware Checklist for Oracle Grid Infrastructure
|Server hardware||Server make, model, core architecture, and host bus adaptors (HBA) are supported to run with Oracle Grid Infrastructure and Oracle RAC.|
|Random Access Memory (RAM)||
At least 4 GB of RAM for Oracle Grid Infrastructure for a Cluster installations, including installations where you plan to install Oracle RAC..
|Virtual Memory configuration||Oracle recommends that you set the paging file size to match the amount of RAM available on the server, up to a maximum of 16 GB|
|Temp space allocation||At least 1 GB allocated to
|Storage hardware||Either Storage Area Network (SAN) or Network-Attached Storage (NAS). You cannot use NTFS formatted disks or partitions for Oracle Clusterware files or data files because they cannot be shared.|
|Local Storage Space for Oracle Software||
|Intelligent Platform Management Interface (IPMI) Configuration||
|Time Synchronization||Configure either Windows Time Service (WTS), Network Time Protocol (NTP), or Oracle Cluster Time Synchronization Service (CTSS) to synchronize the time used by each server in the cluster.|
Review the following environment checklist for all installations.
Table 1-2 Environment Configuration for Oracle Grid Infrastructure and Oracle RAC
Review "Creating Installation Groups and Users for Oracle Grid Infrastructure and Oracle RAC" for information about the users you need to create for your specific requirements. Oracle Installation users have different requirements from Oracle Home users. User names must use only ASCII characters.
|Create mount point paths for the software executable files||
Oracle recommends that you follow the guidelines for an Optimal Flexible Architecture configuration, as described in the appendix "Optimal Flexible Architecture," in Oracle Database Installation Guide for your platform.
|Ensure that the Grid home (the Oracle home path you select for Oracle Grid Infrastructure) uses only ASCII characters||
This restriction includes Oracle Installation user names, which are used as a default for some home paths, as well as other directory names you may select for paths.
|Unset Oracle software environment variables||
If you have set
If you have had an existing installation on your system, and you are using the same user account to install this installation, then unset the following environment variables:
Review all installations to ensure that you have the required hardware, names, and addresses for the cluster.
During installation, you designate interfaces for use as public, private, or Oracle ASM interfaces. You can also designate interfaces that are in use for other purposes, and not available for Oracle Grid Infrastructure use.
Table 1-3 Network Configuration Tasks for Oracle Grid Infrastructure and Oracle RAC
|Public Network Hardware||
|Private Network Hardware for the Interconnect||
|Perform Windows-specific network configuration tasks||
For more information about these tasks, refer to "Network Configuration Tasks for Windows Server Deployments".
|Cluster Names and Addresses||
Determine and configure the following names and addresses for the cluster:
|Standard Node Public, Private and Virtual IP names and Addresses||
If you are configuring a Standard cluster with Grid Naming Service (GNS), then OUI displays the public and virtual host name addresses labeled as "AUTO" because they are configured automatically. To use this option, you must have configured a subdomain on your DNS that is delegated to GNS for resolution, and you must have a fixed GNS VIP address where the delegated service requests can be routed.
If you are not using GNS, and you are configuring a Standard cluster, then configure the following for each node:
Review this upgrade checklist if you have an existing Oracle Grid Infrastructure or Oracle RAC installation. A cluster is being upgraded until all cluster member nodes run Oracle Grid Infrastructure 12c Release 1 (12.1), and the new clusterware becomes the active release.
Note:On the Windows platform, to upgrade Oracle Clusterware from releases 10.2.0.5 and 188.8.131.52 to release 12.1, you must perform an interim upgrade to 184.108.40.206 for Oracle Clusterware. After upgrading Oracle Clusterware to release 220.127.116.11, you must move the Oracle Cluster Registry (OCR) and voting disk (VDSK) to Oracle ASM. You must also move any files stored on OCFS on Windows or RAW devices to a supported storage mechanism. You can then upgrade Oracle Clusterware release 18.104.22.168 to 12c Release 1 (12.1).
If you intend to install Oracle RAC, then you must first complete the upgrade to Oracle Grid Infrastructure 12c Release 1 (12.1) on all cluster nodes before you install the Oracle Database 12c Release 1 (12.1) release of Oracle RAC.
Note:All Oracle Grid Infrastructure upgrades (upgrades of existing Oracle Clusterware and Oracle ASM installations) are out-of-place upgrades.
|Review Oracle Database Upgrade Guide||
Be familiar with the Oracle Database upgrade process.
|Install the latest available patchset release||
Upgrades from some earlier patchset releases might not be supported.
|Confirm that the Oracle Automatic Storage Management (Oracle ASM) instances use standard Oracle ASM instance names||
The default ASM SID for a single-instance database is
If you have nondefault Oracle ASM instance names, then before you upgrade your cluster, use your existing release
|Check Network Addresses for Standard Oracle Grid Infrastructure deployments||
Ensure the following IP addresses conditions for the public and private networks are met:
|Verify the current operating system is supported for the new release||
Confirm that you are using a supported operating system, patch release, and all required operating system packages for the new Oracle Grid Infrastructure installation.
Confirm Oracle Cluster Registry (OCR) file integrity. If this check fails, then repair the OCRs before proceeding.
|Review Oracle 12c Upgrade Companion (My Oracle Support Note 1462240.1)||
This document contains the most current information regarding other upgrade issues:
|Run the Oracle Database Pre-Upgrade utility||
The Pre-Upgrade utility is a SQL script located in the path
For more information, review My Oracle Support note 884522.1:
Review the following storage configuration task checklist for all installations:
Table 1-4 Oracle Grid Infrastructure Storage Configuration Checks
|Provide paths for Oracle Clusterware files||
During installation, you are asked to provide paths for the following Oracle Clusterware files. These files must be shared across all nodes of the cluster on Oracle ASM because the files created during installation must be available to all cluster member nodes.
Use the following checklist to complete pre-installation tasks.
|Check running Oracle processes, and shut down if necessary||
|Ensure scheduled tasks do not run during installation||
If the installer is running when daily scheduled tasks start, then you may encounter unexplained installation problems if your scheduled task is performing cleanup, and temporary files are deleted before the installation is finished. Oracle recommends that you complete installation before daily scheduled tasks are run, or disable daily scheduled tasks that perform file and directory cleanup until after the installation completes.
|Decide to install other languages||
During installation, you are asked if you want the user interface text translated into languages other than the default, which is English. If the language set for the operating system is not supported by the installer, then by default the installer runs in the English language.
Refer to Oracle Database Globalization Support Guide for detailed information about character sets and language configuration.
|Obtain proxy realm authentication information if you have a proxy realm on your network||
During installation, the installer attempts to download Oracle software updates. If you have a proxy realm configured, then you must provide the proxy realm information and user authentication information to access the Internet through the proxy service. If you do not have a proxy realm, then leave the proxy authentication fields blank.
|Install the Oracle Grid Infrastructure Management Repository||
When performing an Advanced installation of Oracle Grid Infrastructure 12c Release 22.214.171.124, select the option to install the Oracle Grid Infrastructure Management Repository to monitor and analyze cluster performance. For Oracle Grid Infrastructure 12c Release 126.96.36.199 and later the Oracle Grid Infrastructure Management Repository is installed automatically.
If you do not install the Oracle Grid Infrastructure Management Repository, then you permanently disable the following features for your installation:
If you decide later that you want to enable these features, then you must reinstall Oracle Grid Infrastructure with the Oracle Grid Infrastructure Management Repository.