2.3.2 Oracle Software Installation and Configuration

Site Preparation

Install Oracle Grid Infrastructure and Oracle Database referring to Oracle manuals and installation guides.

Kernel parameters
For semopm, specify a value of 4 or more.
Install Users
There are two methods to create install user for the Oracle Grid Infrastructure and the Oracle Database installations, creating separate users, or creating one user. (The method recommended by Oracle is creating separate users.)
PRIMECLUSTER Wizard for Oracle supports both of the methods.
Also, make sure that user ID and group ID are identical on all the nodes.
Note
This document is described for creating separate users. In the case of creating one user, it is necessary to replace “Grid user” with “Oracle user”.

Oracle Grid Infrastructure installation

Install Oracle Grid Infrastructure by referring to the Oracle manual and installation guide.

Note

Install Oracle Grid Infrastructure on a local disk of all nodes.
Check if root user access privileges can switch the user to the Grid user, using the su(1M) command.
```
# su - <Grid user>
```
A command (e.g. script) that has interactive mode should not be described in Grid user's profile. (e.g. /etc/profile, .bash_profile, .cshrc, .profile) It may cause failure of resource monitoring or userApplication startup or shutdown.
Environment that Grid user's home directory and profile are located on the shared disk is not supported. Grid user's home directory and profile must be located on the local disk of each node.

Oracle Database installation

Install Oracle Database by referring to the Oracle manual and installation guide.

Note

Install Oracle Database on a local disk of all nodes.
Check if root user access privileges can switch the user to the Oracle user, using the su(1M) command.
```
# su - <Oracle user>
```
A command (e.g. script) that has interactive mode should not be described in Oracle user's profile. (e.g. /etc/profile, .bash_profile, .cshrc, .profile) It may cause failure of resource monitoring or userApplication startup or shutdown.
Environment that Oracle user's home directory and profile are located on the shared disk is not supported. Oracle user's home directory and profile must be located on the local disk of each node.

Database creating and settings

Create a database by referring to the Oracle manual and installation guide.

Note

If multiple ORACLE_HOME are configured on one server, a different Oracle RAC instance name must be assigned.
If multiple ORACLE_HOME are configured on one server, a different listener name must be assigned.

Information

In scalable operation with Oracle RAC 11g R2, the RMS resource name is generated based on the resource name of Oracle RAC as follows:

Oracle RAC instance resource
```
<SubApplicationName>_<SID>.i
```
Oracle listener resource
```
<SubApplicationName>_<lsnr_name>.l
```
The default value of <lsnr_name> is “LISTENER”.
Oracle Clusterware resource
```
<SubApplicationName>_Clusterware
```
These resource names have the following convention and rules.
RMS resource name must be up to 39 characters.
For information on how to set up <SubApplicationName>, see “2.3.4 userApplication with Oracle Clusterware” and “2.3.5 userApplication with Oracle RAC Instances and Listeners”.

SYSTEM user password
PRIMECLUSTER Wizard for Oracle accesses and monitors Oracle as the Oracle SYSTEM user. Therefore, the SYSTEM user's password must be registered in PRIMECLUSTER Wizard for Oracle. See “4.3 clorapass - Register Password for Monitoring” to register the password.

Setting change

Disabling automatic startup of Oracle Clusterware
Disable automatic startup of Oracle Clusterware by executing the following command on each node with super user access privileges.
Example
See the following setup example:
```
# <ORACLE_HOME>/bin/crsctl disable crs
```
<ORACLE_HOME> is the directory path where the Oracle Grid Infrastructure was installed.
Note
This setup is required when the Oracle Clusterware is registered in an RMS resource (Configuration A or Configuration B).
Disabling automatic startup of CRS resource
Disable automatic startup of Oracle RAC instance.
This is because the Oracle RAC instance is registered as an RMS resource and its startup is controlled by userApplication, not Oracle Clusterware.
See the following setup example:
```
$ srvctl modify database -d $DB_NAME -y manual
```
Information
For detail of editing, refer to Oracle manuals.

Operation check

Check if Oracle RAC instances and listeners are properly operating. Also, check if crsctl status resource command can be executed by Grid user, and srvctl config database command can be executed by Oracle user.

Example

The following example shows the operation results:

# su - <Grid user>
$ crsctl status resource -t
-------------------------------------------------------------------
NAME           TARGET  STATE        SERVER          STATE_DETAILS
-------------------------------------------------------------------
Local Resources
-------------------------------------------------------------------
ora.DATA.dg
               ONLINE  ONLINE       node1
               ONLINE  ONLINE       node2
ora.LISTENER.lsnr
               ONLINE  ONLINE       node1
               ONLINE  ONLINE       node2
ora.asm
               ONLINE  ONLINE       node1
               ONLINE  ONLINE       node2
ora.eons
               ONLINE  ONLINE       node1
               ONLINE  ONLINE       node2
ora.gsd
               OFFLINE OFFLINE      node1
               OFFLINE OFFLINE      node2
ora.net1.network
               ONLINE  ONLINE       node1
               ONLINE  ONLINE       node2
ora.ons
               ONLINE  ONLINE       node1
               ONLINE  ONLINE       node2
-------------------------------------------------------------------
Cluster Resources
-------------------------------------------------------------------
ora.LISTENER_SCAN1.lsnr
      1        ONLINE  ONLINE       node1
ora.oc4j
      1        OFFLINE OFFLINE
ora.racdb.db
      1        ONLINE  ONLINE       node1         Open
      2        ONLINE  ONLINE       node2         Open
ora.scan1.vip
      1        ONLINE  ONLINE       node1
ora.node1.vip
      1        ONLINE  ONLINE       node1
ora.node2.vip
      1        ONLINE  ONLINE       node2
$

# su - <Oracle user>
$ srvctl config database
racdb
$

Define the full path of the log file

Define the full path of the alert log and the listener log in /opt/FJSVclora/etc/clgetoralog.conf. See the Note in “4.5 clgetoralog - Collect Troubleshooting Information" for details.