Sun Cluster HA for SAP Upgrade Issues

Before performing an upgrade to Sun Cluster 2.2 from Solstice HA 1.3 or Sun Cluster 2.1, note these SAP-related issues.

• On each node, if you customized hasap_start_all_instances or hasap_stop_all_instances scripts in Solstice HA 1.3 or Sun Cluster 2.1, save them to a safe location before beginning the upgrade to Sun Cluster 2.2. Restore the scripts after completing the upgrade. Do this to prevent loss of your customizations when Sun Cluster 2.2 removes the old scripts.

• The configuration parameters implemented in Sun Cluster 2.2 are different from those implemented in Solstice HA 1.3 and Sun Cluster 2.1. Therefore, after upgrading to Sun Cluster 2.2, you must reconfigure Sun Cluster HA for SAP by running the hadsconfig(1M) command.

  Before starting the upgrade, view the existing configuration and note the current configuration variables.

  • For Solstice HA 1.3, use the hainetconfig(1M) command to view the configuration.

  • For Sun Cluster 2.1, use the hadsconfig(1M) command to view the configuration.

  After upgrading to Sun Cluster 2.2, use the hadsconfig(1M) command to re-create the instance.

• In Sun Cluster 2.2, the hareg -n command shuts down the entire Sun Cluster HA for SAP data service, including all instances and fault monitors. In previous releases, the hareg -n command, when used with Sun Cluster HA for SAP, shuts down only the fault monitors.

  Additionally, before turning on the Sun Cluster HA for SAP data service using hareg -y, you must stop the SAP central instance. Otherwise, the Sun Cluster HA for SAP data service will not be able to start and monitor the instance properly.