Upgrading Sun Cluster HA for Oracle from Sun Cluster 2.2 to Sun Cluster 3.0 Software

Perform these procedures while upgrading the Sun Cluster framework using the scinstall upgrade procedure.

Conditions and Restrictions

The following conditions and restrictions apply when upgrading Sun Cluster HA for Oracle from Sun Cluster 2.2 to Sun Cluster 3.0 software.

• Before upgrading Sun Cluster HA for Oracle, you must check that you have met all conditions described in the Sun Cluster 3.0 Installation Guide relating to upgrading the Sun Cluster framework from Sun Cluster 2.2.

• Sun Cluster HA for Oracle must be functioning normally on Sun Cluster 2.2 before you begin the upgrade.

How to Save the Sun Cluster HA for Oracle Configuration Files

Use the following procedure to save the configuration files from your Sun Cluster 2.2 configuration.

1. Follow the scinstall framework-upgrade procedure until you have completed the upgrade-begin steps (scinstall -F begin) on each node.

2. Run the following command on each node as superuser. This command will save a version of all files in the /var/opt/oracle directory.

   To ensure that this information does not get lost, back up the structure found in the /var/opt/oracle directory to an external device.

   # cp -r /var/opt/oracle /var/cluster/logs/install/preserve/2.2/SUNWscor

3. Complete the finish portion of the framework upgrade (scinstall -u finish).

   ---

   Note -

   Do not use the -s oracle option with the scinstall -u finish command. This option attempts an automated upgrade for Sun Cluster HA for Oracle, and the automated upgrade will fail. The only automated upgrade supported is for NFS.

   ---

After completing the framework upgrade, set up the Sun Cluster 3.0 environment. The following section, "Setting Up the Sun Cluster 3.0 Environment", describes this procedure.

Setting Up the Sun Cluster 3.0 Environment

Perform the following steps to set up your Sun Cluster 3.0 environment.

1. On one node, run the following command to verify that:

   • The framework upgrade has correctly set up a Sun Cluster 3.0 resource group that corresponds to each Sun Cluster 2.2 logical host.

   • The hostname network resource is in the resource group and is online.

   # scstat -g

2. On one node, run the following command to verify that the VERITAS disk group or Solstice DiskSuite diskset that held the Oracle database (and possibly the Oracle binaries) in Sun Cluster 2.2 is correctly mapped into a Sun Cluster 3.0 disk device group.

   # scstat -D

3. On each node, run the following command to verify that the required file systems for each Oracle instance are mounted.

   # mount

4. On each node, run the following commands to restore the saved version of the Oracle configuration files under the /var/opt directory.

   If you saved the files in the /var/opt/oracle directory earlier in the procedure, and the files are unchanged, you can skip this step.

   # cp -r /var/cluster/logs/install/preserve/2.2/SUNWscor/oracle /var/opt # chown -R oracle:dba /var/opt/oracle

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

Verify the Upgrade

To verify that the upgrade has completed successfully, perform the following steps.

1. Verify that the Oracle resources are online by using the following command

   # scstat -g

   .

2. Verify that you can switch over the resource group by using the following command.

   # scswitch -z -g resource-group -h node