Select the following software installation paths
Specify an Oracle base location that is owned by the user performing the installation. You can choose a location with an existing Oracle home, or choose another directory location that does not have the structure for an Oracle base directory.
Using the Oracle base directory path helps to facilitate the organization of Oracle installations, and helps to ensure that installations of multiple databases maintain an Optimal Flexible Architecture (OFA) configuration.
Even if you do not use the same software owner to install Oracle Clusterware and ASM, and to install Oracle Database, be aware that running the root.sh script during the Oracle Grid Infrastructure installation changes ownership of the home directory where Oracle Clusterware binaries are placed to root. For this reason, the Oracle Grid Infrastructure for a cluster home cannot be in the same location as other Oracle software. However, Oracle Grid Infrastructure for a standalone database--Oracle Restart--can be in the same location as other Oracle software.
If you have created a path for Oracle base that is compliant with Oracle Optimal Flexible Architecture (OFA) guidelines for Oracle software paths, then Oracle Universal Installer provides this path as the default Oracle base path. For OUI to recognize the path as an Oracle software path, it must be in the form /u0[1-9]/app, and it must be writable by any member of the Oracle Inventory (oraInventory) group. Oracle recommends that you create an Oracle base path manually. The Optimal Flexible Architecture path for the Oracle Base is /u01/app/user, where user is the name of the user account that you want to own the Oracle Database software.
Specify a location for the Oracle Clusterware and Automatic Storage Management (Oracle ASM) software binaries. Ensure that the directory path you provide meets the following requirements:
It should be created in a path outside existing Oracle homes.
It should not be located in a user home directory.
It should be created either as a subdirectory in a path where all files can be owned by root, or in a unique path.
Before installation, it should be owned by the installation owner (typically oracle for a single installation owner for all Oracle software, or grid for role-based Oracle installation owners), and set to 750 permissions.
For installations with Oracle Clusterware and ASM only, Oracle recommends that you create a path compliant with Oracle Optimal Flexible Architecture (OFA) guidelines, so that Oracle Universal Installer (OUI) can select that directory during installation. For OUI to recognize the path as an Oracle software path, it must be in the form u0[1-9]/app.
When OUI finds an OFA-compliant path, it creates the software home and Oracle central inventory (oraInventory) directories for you.
If you created an OFA-compliant path for Oracle base, then it automatically creates an OFA-compliant path for the software home derived from the Oracle base path. The Optimal Flexible Architecture path for Oracle Base is /u01/app/user, where user is the name of the user account that you want to own the Oracle Database software.
Select the type of storage on which you want to store the Oracle Cluster Registry. You can select either Oracle Automatic Storage Management (Oracle ASM) or a file system.
If you choose to place your Oracle Cluster Registry (OCR) files on a shared file system, then Oracle recommends that one of the following is true:
The disks used for the file system are on a highly available storage device, (for example, a RAID device).
At least two file systems are mounted, and use the features of Oracle Clusterware 11g release 2 (11.2) to provide redundancy for the OCR.
The Oracle Cluster Registry (OCR) is used to manage the cluster. It must be located on a shared storage device. Oracle recommends that you have redundancy for this file.
Specify the OCR location, and how you are providing a redundant copy of the OCR.
Provide a password for the SYSASM privilege. The SYSASM privilege provides administrator system privileges for the Oracle Automatic Storage Management (Oracle ASM) instances.
Members of the OSASM for ASM group are granted administrator system privileges (SYSASM) for Oracle ASM instances. These privileges are equivalent to the SYSDBA database administrator privileges granted by membership in the OSDBA Group.
Members of the OSASM for ASM group can use SQL to connect to an ASM instance as SYSASM using operating system authentication. The SYSASM privileges permit mounting and dismounting disk groups, and other storage administration tasks. SYSASM privileges provide no access privileges on an Oracle Database instance.
You can choose to set up separate operating system role-based administrative privileges groups, or use the same group to grant administrative privileges. Provide an operating system group using one of the following options:
If you intend to install Oracle Database, and you want to have one operating system group whose members have administrative privileges for both the ASM instances and the Oracle Database instances, then select the same group for the OSASM group that you intend to use for the OSDBA group.
If you want role-allocation of privileges using separate groups to grant privileges on the ASM storage tier and the database tier, then select a group whose members will be only storage tier administrators.
If you have created groups using the default names for the role-allocated groups, then the installer uses these group names as the default options.
OSASM group: Default name: asmadmin.
OSDBA for ASM group: Default name asmdba
OSOPER for ASM group: Default name asmoper