Skip to Content
avatar image
Former Member

What is the best senario for upgrading SAP ECC6 EHP0 to EHP8 in replicated systems?

Hi Guys

We are performing an Upgrade of SAP ERP 6.0 EHP 0 to EHP 8 based in AIX and Oracle 12c.

This is a productive database so its replicated to another server using Dataguard.

My main questions are:

-What is the best senario for this upgrade without or with minimum downtime?

-If i did the upgrade on DR server to be EHP 8 the changes in data that happened on the main server on EHP 0 will replicated to DR server correctly?

-Is the oracle dataguard tool can replicate two systems with different EHP version?



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Jul 10, 2017 at 08:56 PM

    Hi Karem,

    First EhP0 to EhP8 is a two step upgrade, you cannot upgrade it directly in one step.

    Data guard can support such scenario Ex: If you upgrade your primary system then all changes will get replicated to secondary but still you need to perform few manual steps at application level (Like Kernel, Profile parameters etc.) BUT if you perform the upgrade by following this scenario, how can you manage your primary with archive logs ON during the upgrade ? It generates tons of archive logs which need to be shipped and applied on DR database. Other challenge is if you are following this scenario, how can you use your DR as fall back solution if your upgrade goes into trouble ? Versions of Oracle on primary and target (of EhP8) also plays a role here.

    To avoid these issues, perform upgrade on Primary (Disconnect Data guard just before the downtime so that it can be used as fall back solution if your primary is not usable) and do a backup restore and Data guard enablement after the upgrade.


    Harish Karra

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member


      Upgrade is an uptime+downtime activity. Most of the activities are done during uptime in a shadow system and those will get replicated in original system during it's downtime.

      Downtime is very minimum (again depends on system performance and other factors) but downtime is mandatory.


      Harish Karra

  • Jul 12, 2017 at 09:08 AM

    A direct update to EHP8 is possible if the conditions are met.

    Download the SUM Central note and check the upgrade paths provided there.

    2371752 - Central Note - Software Update Manager 1.0 SP20 [lmt_006]

    As the source system is ERP 6.0 you need to check the note 2187353 for the minimum SP requirement.

    2187353 - SP Equivalence for update/upgrade to SAP NW 7.5

    First you need to make sure you have supported OS and DB for the EHP8 update. Check PAM. In previous releases of SUM there used to be an option to disable archiving at the database level which will switch the database into no-archive log mode. I am not sure about this in the newer versions of SUM but you need to make sure this is not enabled. As long as the archive logs are generated the standby database will get updated. All modifications is done at the database level so Oracle will replicate all the changes from the source to the target using the archive logs. You need to make sure there is sufficient space at the file-system at both sites. The EHP8 update should be done on the main instance. As the target system is based on EHP8, during the update the system will be modifying the profiles as there is no longer START profiles. So you need to make sure the DR site is updated with the new profiles, kernel and other things.

    If there is enough resources at the OS level then increasing the number of processes for the uptime and downtime tasks can help. As a starting step download and read the upgrade guide.

    Add comment
    10|10000 characters needed characters exceeded