Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), April 2009

• changing the SAP System ID
• changing the name of the SAP System Administrator
• migrating to another database vendor
• adding/deleting Dialog Instances
• changing an Instance Name
• changing an Instance Number
• changing the network name belonging to a relocatable address
• changing the name of a Serviceguard Extension for SAP on Linux package
• changing hostnames of hosts inside the cluster
• changing hostnames or IP addresses of hosts that run additional application servers
• changing the location of any SAP-specific directory in the file system
• changing the name of the ORACLE listener
After performing any of the above mentioned activities Serviceguard Extension for SAP on Linux failover has
to be tested again to confirm proper operation.
Figure 5-1 Serviceguard Extension for SAP on Linux cluster displayed in the HP Serviceguard Manager GUI
Upgrading SAP Software
Upgrading the SAP applications does not normally require changes to Serviceguard Extension for SAP on
Linux. Usually Serviceguard Extension for SAP on Linux detects the release of the application that is packaged
automatically and treats it as appropriate. Make sure that you have a valid Serviceguard Extension for SAP
on Linux version in place by issuing the command:
rpm -qa | grep -i sgesap
Review the release notes of the Serviceguard Extension for SAP on Linux version that gets reported by this
command and make sure that the target SAP application release is supported with the installed Serviceguard
Extension for SAP on Linux version. Should this not be the case, you should first update Serviceguard Extension
for SAP on Linux
For a clean Serviceguard Extension for SAP on Linux upgrade, Serviceguard Extension for SAP on Linux can
be switched off as described in the section below.
Perform failover tests for all potential failure scenarios before putting the system into production state.
122 Serviceguard Extension for SAP on Linux Cluster Administration