Configure Sun Cluster HA for Oracle Under Sun Cluster 3.0

Configure Sun Cluster 3.0 HA for Oracle using the following procedure.

Perform Step 1 only once.

1. On one node, register the Oracle server and listener resource types using the following commands.

   # scrgadm -a -t SUNW.oracle_server # scrgadm -a -t SUNW.oracle_listener

   Run Step 2 through Step 5 for each Sun Cluster 2.2 HA for Oracle instance listed in the /var/opt/oracle/oratab file.

2. Determine the value of the ORACLE_HOME variable from the oratab file.

   For example, suppose the oratab file shows the following information.

   ora32:/oracle/816_32:N

   This information indicates that the ORACLE_HOME variable for the ORACLE_SID ora32 instance is the value /oracle/816_32.

3. Retrieve the parameter values from the ccd.database file for each Oracle instance.

   These parameters will map into Sun Cluster 3.0 parameters to scrgadm. You will use these parameters when configuring Sun Cluster HA for Oracle under Sun Cluster 3.0.

   # grep ^HAORACLE: /var/cluster/logs/install/preserve/2.2/SUNWcluster/conf/ccd.database

   Each Oracle instance in the ccd.database file uses the following format

   HAORACLE:on:ora32:boots-1:60:10:120:300:scott/tiger:/oracle/816_32/dbs/initora32.ora:ORA_LIST

   .

   These parameters map into the following Sun Cluster 3.0 format.

   HAORACLE:STATE:ORACLE_SID:LOGICAL_HOSTNAME_IP_Resource:THOROUGH_PROBE_INTERVAL:CONNECT_CYCLE:PROBE_TIMEOUT:RETRY_INTERVAL:CONNECT_STRING:PARAMETER_FILE:LISTENER_NAME

   The resource group name RG_NAME will be ${LOGICAL_HOSTNAME_IP_Resource}-lh. Note that the -lh will be automatically appended to the resource group name in Sun Cluster 3.0.

4. Locate the background_dump_dest value in the $PARAMETER_FILE variable, and set the ALERT_LOG_FILE variable to the following value.

   $background_dump_dest/alert_$ORACLE_SID.log

   For example, for ORACLE_SID=ora32, suppose that in the $PARAMETER_FILE file, background_dump_dest is the following value.

   /oracle/816_32/admin/ora32/bdump

   In this example, ALERT_LOG_FILE should be updated to the following value.

   /oracle/816_32/admin/ora32/bdump/alert_ora32.log

5. On one node, run the following commands to create Oracle resources and bring them online.

   # scrgadm -a -t SUNW.oracle_server -g $RG_NAME -j $ORACLE_SID-serv \ -x Oracle_sid=$ORACLE_SID -x Oracle_home=$ORACLE_HOME \ -y Thorough_probe_interval=$THOROUGH_PROBE_INTERVAL \ -x Connect_cycle=$CONNECT_CYCLE -x Probe_timeout=$PROBE_TIMEOUT \ -y Retry_interval=$RETRY_INTERVAL -x Connect_string=$CONNECT_STRING \ -x Parameter_file=$PARAMETER_FILE -x Alert_log_file=$ALERT_LOG_FILE # scrgadm -a -j $ORACLE_SID-list -t SUNW.oracle_listener -g $RG_name \ -x Oracle_home=$ORACLE_HOME -x Listener_name=$LISTENER_NAME# scswitch -e -j $ORACLE_SID-serv # scswitch -e -j $ORACLE_SID-list # scswitch -e -M -j $ORACLE_SID-serv # scswitch -e -M -j $ORACLE_SID-list

   For example, using the Oracle instance described in Step 2, Step 3, and Step 4, you would run the following commands.

   # scrgadm -a -t SUNW.oracle_server -g boots-1-lh -j ora32-serv \ -x Oracle_sid=ora32 -x Oracle_home=/oracle/816_32 \ -y Thorough_probe_interval=60 \ -x Connect_cycle=10 -x Probe_timeout=120 \ -y Retry_interval=300 -x Connect_string=scott/tiger \ -x Parameter_file=/oracle/816_32/dbs/initora32.ora \ -x Alert_log_file=/oracle/816_32/admin/ora32/bdump/alert_ora32.log # scrgadm -a -j ora32-list -t SUNW.oracle_listener -g boots-1-lh \ -x Oracle_home=/oracle/816_32 -x Listener_name=ORA_LIST # scswitch -e -j ora32-serv # scswitch -e -j ora32-list # scswitch -e -M -j ora32-serv # scswitch -e -M -j ora32-list