sapnote_0001012486

8/8/2019 sapnote_0001012486

http://slidepdf.com/reader/full/sapnote0001012486 1/3

05.12.2010 Page 1 of 3

SAP Note 1012486 - Important Information on upgrading SAPSystems in HA-Setups

Note Language: English Version: 5 Validity: Valid Since 10.03.2008

Summary

Symptom

You consider upgrading an SAP system, which has been configured to run

inside a highly available (switch over) hardware environment. This note

contains important additional information on how to plan the upgrade in

such an environment.

Other terms

hardware cluster, HA, High Availability, ERP2005, ECC 6.0, mySAP ERP

Reason and Prerequisites

Your SAP system is installed in an HA environment using a failover hardware

cluster.

Solution

Upgrade Planning

o HA Solution Provider/Hardware Partner Involvement

Make sure to involve your hardware and HA solution provider in your

upgrade planning. You may need to update the cluster software or

cluster hardware so that it can support the new SAP release. Such

3rd party updates are not part of the upgrade paths described in

the SAP upgrade guides. Carefully plan the complete system upgrade

procedure with your HA solution provider and hardware partner

before starting the upgrade.

Involving the partners can dramatically shorten the support times

in case of an unexpected upgrade problem.

Recommended Upgrade Preparations

o Disabling/Enabling cluster failover capabilities

At the beginning of the upgrade downtime phases you will be

requested to disable the cluster failover capabilities. This is

required to allow the upgrade tools to stop and restart clustered

instances. Otherwise, the cluster software might detect the stop of

a clustered instance as an instance failure and will start it again

on the failover host.

Switching off the cluster failover capabilities should only disable

the automatic failover mechanism of your cluster solution, but

should not take the related ressources offline. For example, the

upgrade tool must still be able to start and stop the instances,

and the file systems assigned to the clustered instance must be

read/write accessible.

To reduce the overall system outage time, prepare the required

procedures to disable/enable cluster failover features before youstart the upgrade.

8/8/2019 sapnote_0001012486


05.12.2010 Page 2 of 3


o Creating an optimal upgrade starting point

To create a reliable starting point for the upgrade it is crucial

to implement an HA system configuration recommended by SAP. Below

you find a list of known problems with other configurations:

- If you have manually set up a standalone enqueue, you should

revert this configuration prior to the execution of the

downtime phases of the upgrade, latest prior to kernel switch

phase. The upgrade tool is unable to detect a manual set up of

standalone enqueue servers and, therefore, cannot update them.

This might cause problems when the system is started for the

first time after the kernel switch. This only applies to

standalone enqueue servers (separately started enserver

process), NOT to officially supported (A)SCS instances.

- Clean up the profile directory. Remove any old, unused profiles

and backup copies. The directory should only contain activeprofile files. Also links to local profiles with different

names should be avoided. Only files are expected.

o Removing Java 6.30 Add-In from 6.20 ABAP instances

Remove Add-in installations of SAP Web AS Java 6.30 from the SAP

Web AS ABAP 6.20 instances. These Java Add-Ins cannot be updated.

You can re-install the Add-In after the upgrade has succeeded.

Perform Standard Upgrade

o Perform the standard upgrade process as described in the respective

SAP software upgrade guide and the related central SAP Note for the

upgrade.

Post-Upgrade Activities

o Installing Enqueue Replication Server (ERS) instances

If you are running an ASCS or SCS setup, make sure to have an

Enqueue Replication Server (ERS) installed. More information on how

to set up an ERS with your cluster failover software can beprovided by your HA solution implementation partner.

Header Data

Release Status: Released for Customer

Released on: 25.03.2008 08:33:52

Master Language: English

Priority: Recommendations/additional info

Category: Upgrade informationPrimary Component: BC-UPG Upgrade - general

8/8/2019 sapnote_0001012486


05.12.2010 Page 3 of 3


Valid Releases

Software Component Release From

Release

To

Release

and

Subsequent

SAP_APPL 600 600 600 XSAP-JEE 60 6.40 6.40

SAP-JEE 7.00 7.00 7.01

SAP_BASIS 60 620 640



Related Notes

Number Short Text

1061649 Upgrade to SAP NetWeaver Process Integration 7.1

Documents

sapnote_0001012486