Skip to Content
author's profile photo Former Member
Former Member

SAP ECC6.0 Upgrade to EhP5 or EhP6

Hi,

We need to upgrade our ECC6.0 to either EhP5 or EhP6. It's required for an add-on vistex. I have few questions:

1. Our ECC production is 5TB. Why do we need a full system copy on sandbox. Can we use TDMS to bring configuration and master data and do our first test upgrade? How can we make sure our timelines for production unless we have a full system copy? I believe we'll be refreshing our QA with full copy of production. If we do not get approval to go for full copy of prod on QA what are the consequences?

2. Since EhP5 is old shouldn't we go for EhP6?

Regards,

SJ


Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    Posted on Sep 03, 2015 at 12:44 PM

    Hi SJ

    2. Since EhP5 is old shouldn't we go for EhP6?

    1. You can upgrade the system from ECC 6 with NW 7.00 to ECC6 EHP6 With NW 7.3.(Not on EHP5)

    1. Our ECC production is 5TB. Why do we need a full system copy on sandbox. Can we use TDMS to bring configuration and master data and do our first test upgrade? How can we make sure our timelines for production unless we have a full system copy? I believe we'll be refreshing our QA with full copy of production. If we do not get approval to go for full copy of prod on QA what are the consequences?

    2. If your are creating the Sandbox system from Production you can calculate over all timing(Down time and upgrade process time since you db size 5 TB),

    what are the issues which you are going to face during the live landscape systems(DEV, QAS & PRD).

    Post upgrade issues and testing on other SAP modules

    3. Before that Kindly refer the SAP upgrade guide from below link. based on your OS / DB & SAP version

    SAP NetWeaver Guide Finder

    Regards

    SS

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      We can caluculate timings during our QA upgrade since that's a full copy of production. What's the reason we always recommend to go for a full copy and why can't we use TDMS to bring data and then do the upgrade. I need to prepare planning slides with pros and cons and that's why put up this question.

  • author's profile photo Former Member
    Former Member
    Posted on Sep 03, 2015 at 12:57 PM

    Hello SJ,

    TDMS should be considered when you have multiple landscape and it is centric to Quality,Dev and sandbox systems.

    For specific data if you have existing TDMS setup..then u could try or you will be loosing time configuring TDMS and Creating shells for specific data migration.

    5TB data..that pretty big one...untill unless you have better hardware such as good size of RAM and CPUs with multiple cores dynamic assignment options, you would need lot of time for each system upgrade.

    The SUM tool in order to avoid downtime creates a shadow system updates it first. then it switches to original system.

    You can opt for building a sandbox with backup and restore method from a backup of dev initially.

    Regards

    Anand

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi SJ,

      The shadow instance should take almost the same size of your primary instance . It doesnt matter how much Big your Database is . ie if your primary /usr/sap/<SID/<DVebmgs<Instance Number> is 10 GB , allocate the same space for the shadow instance .

      If You are concerned about the shadow schema , this would be automatically calculated by SUM during prerequisite check . and should be the same across your landscape ( ie DEV, PRD,QAS )

      Thanks ,

      Manu

  • Posted on Sep 15, 2015 at 04:40 PM

    As there is no indication as to what the underlying database is, I cannot be specific here. If you read the EHP installation / update guide it clearly says the filesystems requirements for the SUM tool and also a separate filesystem for all the patches and kernel to be kept. For an Oracle database there will be a new tablespace created so you need to have space in the sapdata filesystems. I would say approximately 120 GB should be enough.

    Add a comment
    10|10000 characters needed characters exceeded

    • You will need to make sure that you have enough space in the sapdata filesystems to create a tablespace called PSAPSR3731 for the upgrade. I believe the space would be in the range of 80 GB to 120 GB. Additionally, you also need to have a filesystem for the SUM and also for all the installation packages (SP's, Kernel etc). Something in the range of 100 GB to 150 GB. This would be temporary. Also, after the EHP update you will be dropping the old tablespace which I believe is PSAPSR3702 so you will get some free space in the sapdata as well.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.