Site Preparation
Set kernel parameters and user groups according to the Oracle manual and installation guide. It is necessary to set a logical IP address for RAC on each node.
If you create a DBA (Database Administrator) user to install Oracle, start, or stop Oracle operation, make sure that user ID and group ID are identical on all the nodes.
For semopm, specify a value of 4 or more.
Oracle Clusterware installation
Install Oracle Clusterware by referring to the Oracle manual and installation guide.
Note
The PRIMECLUSTER Wizard for Oracle determines a directory where to install Oracle Clusterware with the “$ORA_CRS_HOME” environment variable. Set an installation directory of Oracle Clusterware for the “$ORA_CRS_HOME” environment variable of an Oracle DBA user.
Example
See the following setup example:
ORA_CRS_HOME=/opt/oracle/product/10.1.0/crs; export ORA_CRS_HOME
Oracle RAC installation
Install Oracle RAC by referring to the Oracle manual and installation guide.
Note
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.
PRIMECLUSTER Wizard for Oracle controls Oracle as the Oracle DBA user. Be sure to include $ORACLE_HOME/bin and $ORA_CRS_HOME/bin in the PATH environment variable of the Oracle DBA user.
See the following setup example:
ORACLE_HOME=/opt/oracle/product/10.2.0/db; export ORACLE_HOME ORA_CRS_HOME=/opt/oracle/product/10.2.0/crs; export ORA_CRS_HOME PATH= $ORACLE_HOME/bin: $ORA_CRS_HOME/bin; export PATH
Database creating and settings
Create a database by referring to the Oracle manual and installation guide.
Information
In scalable operation with Oracle RAC 10g or later, the RMS resource name is generated based on the resource name of Oracle RAC as follows:
Oracle RAC instance resource
<SubApplicationName>_<inst_name>.i
Oracle listener resource
<SubApplicationName>_<lsnr_name>.l
The default value of <lsnr_name> is “LISTENER_<node name>”.
Oracle Clusterware resource
<SubApplicationName>_Clusterware
The resource name begins with “<SubApplicationName>_” instead of “ora” of the resource name displayed with the crs_stat command of Oracle RAC.
<ApplicationName> must be up to 39 characters.
For information on how to set up <ApplicationName>, see “2.3.4 userApplication with Oracle Clusterware” and “2.3.5 userApplication with Oracle RAC Instances and Listeners”.
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:
# /etc/init.d/init.crs disable
Note
This setup is required when the Oracle Clusterware is registered in an RMS resource.
Disabling automatic startup of CRS resource
Disable automatic startup of Oracle RAC instance (inst) by setting “never” to AUTO_START attribute.
This is because the Oracle RAC instance is registered as an RMS resource and its startup is controlled by userApplication, not Oracle Clusterware.
See
For detail of editing AUTO_START, refer to Oracle manuals.
Operation check
Check if Oracle instances and listeners are properly operating. Also, check if the crs_stat command can be executed using the Oracle DBA user.
Example
The following example shows the operation results:
% crs_stat -t Name Type Target State Host ------------------------------------------------------------ ora....T2.lsnr application ONLINE ONLINE node2 ora.node2.gsd application ONLINE ONLINE node2 ora.node2.ons application ONLINE ONLINE node2 ora.node2.vip application ONLINE ONLINE node2 ora....T1.lsnr application ONLINE ONLINE node1 ora.node1.gsd application ONLINE ONLINE node1 ora.node1.ons application ONLINE ONLINE node1 ora.node1.vip application ONLINE ONLINE node1 ora.rac.db application ONLINE ONLINE node1 ora.rac.pcl.cs application ONLINE ONLINE node1 ora....ac1.srv application ONLINE ONLINE node1 ora....ac2.srv application ONLINE ONLINE node2 ora....c1.inst application ONLINE ONLINE node1 ora....c2.inst application ONLINE ONLINE node2
