Oracle 11g rac installation solaris guide

Depending on the components you want to use, you must ensure that the following software are installed:. However, these are not mandatory for the database installation. You do not require a web browser to install Oracle Database. However, browsers are required to access documentation, and if you intend to use Oracle Enterprise Manager Database Control and Oracle Application Express. Microsoft Internet Explorer The following or later patches are required for Oracle Database 11g Release 2 To determine whether an operating system patch is installed, enter a command similar to the following:.

For example, to determine if any version of the patch is installed, use the following command:. If an operating system patch is not installed, then download it from the My Oracle Support website and install it:.

The following local operating system groups and users are required if you are installing Oracle Database:. To determine whether these groups and users exist, and if necessary, to create them, follow these steps:. To determine whether the oinstall group exists, enter the following command:. If the output of this command shows the oinstall group name, then the group exists. If the oraInst. If the output from this commands shows the dba group name, then the group exists.

If necessary, enter the following commands to create the oinstall and dba groups:. To determine whether the oracle user exists and belongs to the correct groups, enter the following command:. If the oracle user exists, this command displays information about the groups to which the user belongs. The output should be similar to the following, indicating that oinstall is the primary group and dba is a secondary group:. If the oracle user exists, but its primary group is not oinstall or it is not a member of the dba group, then enter the following command:.

If the oracle user does not exist, enter the following command to create it:. This command creates the oracle user and specifies oinstall as the primary group and dba as the secondary group.

On Oracle Solaris 10, verify that the kernel parameters shown in the following table are set to values greater than or equal to the minimum value shown. The kernel parameter values shown in this section are minimum values only. For production database systems, Oracle recommends that you tune these values to optimize the performance of the system.

Refer to your operating system documentation for more information about tuning kernel parameters. Oracle Solaris 10 uses the resource control facility for its implementation. For further information, contact your vendor. The project. If applications, other than the Oracle instances are using the shared memory segment, then you must add that shared memory usage to the project.

For more information, see My Oracle Support Note Use the following procedure to view the current value specified for resource controls, and to change them if necessary:. Use the following procedure to modify the resource control project settings, so that they persist after a system restart:. By default, Oracle instances are run as the oracle user of the dba group. A project with the name group. Run the command id to verify the default project for the oracle user:.

Alternatively, add the resource control value project. To verify that the resource control is active, check process ownership, and run the commands id and prctl , as in the following example:. Oracle recommends that you set shell limits and system configuration parameters as described in this section. The ulimit settings determine process memory related resource limits. Verify that the shell limits displayed in the following table are set to the values shown:. Create directories with names similar to the following, and specify the correct owner, group, and permissions for them:.

Before you create an Oracle base directory, you must identify an appropriate file system with sufficient free disk space. From the display, identify either one or two file systems that meet the disk space requirements mentioned earlier in this section. You must specify the appropriate mount point directories for the file systems on your system. To create the required directories and specify the correct owner, group, and permissions for them:.

Enter the following command to create subdirectories in the mount point directory that you identified for the Oracle base directory:. Change the owner and group of the directories that you created to the oracle user and the oinstall group:. You run Oracle Universal Installer from the oracle account. However, before you start Oracle Universal Installer, you must configure the environment of the oracle user.

To configure the environment, you must:. Set the default file mode creation mask umask to in the shell startup file. If you are not logged in to the system where you want to install the software, then log in to that system as the oracle user. If you are not logged in as the oracle user, then switch user to oracle :. To determine the default shell for the oracle user, enter the following command:.

If you are not installing the software on the local computer, then run the following command on the remote system to set the DISPLAY variable:.

To verify that X applications display is set properly, run a X11 based program that comes with the operating system such as xclock :. If necessary, enter commands similar to the following to create a temporary directory on the file system that you identified, and set the appropriate permissions on the directory:. On most Oracle Solaris systems, the product disc mounts automatically when you insert it into the drive.

If the disc does not mount automatically, then follow these steps to mount it:. Specifies the full path of the user's home directory. You must specify the home directory that you created for the user in Step 3. Optionally specifies the full path name of the program that is to be used as the user's shell when the user logs in. If you specify the -s option, user-shell must specify a valid executable file. Specifies the user name of the user that you are adding.

You must specify the name of a potential user in the DBA group that you defined in Step 2. Specifies the user name of the user whose password you are setting. You must specify the name of a user in the DBA group that you added in Step 4. Specifies the user name of the user for whose home directory you are changing ownership. This example shows the sequence of commands for creating the DBA group dba , which is to contain the users root and oracle.

To enable the Oracle RAC software to run correctly, you must ensure that sufficient shared memory is available on all the cluster nodes. Perform this task on each cluster node.

This information is valid for Oracle Solaris Cluster 4. You must configure these parameters on the basis of the resources that are available in the cluster. However, the value of each parameter must be sufficient to enable the Oracle RAC software to create a shared memory segment that conforms to its configuration requirements. For more information, see your Oracle documentation.

Specifies the name of the group for which you are adding an entry. This group is normally named dba. Specifies a comma-separated list of the user names that are allowed in the group. Ensure that the list contains the names of all DBA users that are required.

Create the home directory of each potential user in the DBA group that you defined in Step 2. Add each potential user in the DBA group that you defined in Step 2 to the system. Use the useradd 1M command to add each user. Adding a user to the system adds an entry for the user to the following files:. Specifies the name of the user group of which the user is a member. You must specify the DBA group that you defined in Step 2. Specifies the full path of the user's home directory.

You must specify the home directory that you created for the user in Step 3. Optionally specifies the full path name of the program that is to be used as the user's shell when the user logs in. If you specify the -s option, user-shell must specify a valid executable file. Specifies the user name of the user that you are adding. You must specify the name of a potential user in the DBA group that you defined in Step 2.

Set the password of each user that you added in Step 4. Use the passwd 1 command to set the password of each user. Specifies the user name of the user whose password you are setting. You must specify the name of a user in the DBA group that you added in Step 4. Change the ownership of each home directory that you created in Step 3 as follows:. Group: the DBA group that you defined in Step 2.

Specifies the user name of the user for whose home directory you are changing ownership. Change the ownership of each directory that you created in Step 7 as follows:. This example shows the sequence of commands for creating the DBA group dba , which is to contain the users root and oracle. Perform this task only if you are using the Solaris 10 OS. To enable the Oracle RAC software to run correctly, you must ensure that sufficient shared memory is available on all the cluster nodes.

Perform this task on each cluster node. You must configure these parameters on the basis of the resources that are available in the cluster. However, the value of each parameter must be sufficient to enable the Oracle RAC software to create a shared memory segment that conforms to its configuration requirements. For the minimum required value of each parameter, see your Oracle documentation. Before you reboot, you must ensure that any volume manager software that is already installed is completely installed.

An incomplete installation of volume manager software causes a panic. If you use VxVM, also ensure that you have installed the software and that the license for the VxVM cluster feature is valid. Otherwise, a panic occurs when you reboot. To configure shared memory for the Oracle RAC software in a zone cluster, perform the following steps:. These steps do not affect the actual shared memory control for the zone cluster. You perform these steps to help Oracle dbca utility enables you to set the database memory allocation.

If the Oracle dbca utility is not used for RAC database creation, you can skip these steps in the zone cluster. Configure the capped-memory property attributes physical , swap , and locked by using the clzonecluster command. Specifies the limit of the shared memory segment size that the Oracle RAC database processes can request to lock in memory. All parameters for a single entry must be on the same line. The disks should now be visible and have the correct ownership using the following command.

If they are not visible, your UDEV configuration is incorrect and must be fixed before you proceed. Later versions of VirtualBox allow you to clone VMs, but these also attempt to clone the shared disks, which is not what we want. Instead we must manually clone the VM. Create the "olrac2" virtual machine in VirtualBox in the same way as you did for "olrac1", with the exception of using an existing "olrac2.

Remember to add the second network adaptor as you did on the "olrac1" VM. When the VM is created, attach the shared disks to this VM. Start the "olrac2" virtual machine by clicking the "Start" button on the toolbar. Ignore any network errors during the startup. Log in to the "olrac2" virtual machine as the "root" user so we can reconfigure the network settings to match the following. Check the MAC address of each of the available network connections. Don't worry that they are listed as "eth2" and "eth3".

These are dynamically created connections because the MAC address of the "eth0" and "eth1" connections is incorrect. If it is incorrect, amend it to match the settings described above. Restart the "olrac2" virtual machine and start the "olrac1" virtual machine. When both nodes have started, check they can both ping all the public and private IP addresses using the following commands.

Check the UDEV rules are working on both machines. For some reason, this doesn't seem to happen on my OL6. Prior to 11gR2 we would probably use the "runcluvfy.

If you are intending to configure SSH connectivity using the installer this check should be omitted as it will always fail. If you want to setup SSH connectivity manually , then once it is done you can run the "runcluvfy.

Before moving forward you should probably shut down your VMs and take snapshots of them. If any failures happen beyond this point it is probably better to switch back to those snapshots, clean up the shared drives and start the grid installation again.