Regarding the upgrading the ECC6.0 system to EHP7

[Former Member]

Hi All,

We have upgraded our ECC6.0 system to EHP7 but we have following questions before we can proceed to do it in our production system.

• During EHP7 upgrade going on production system whether we will be able to move the transport request into production? 

• As when we did the EHP7 upgrade testing during that time Initialization, Extraction, Configuration, Checks and Preprocessing taken 21days how we can reduce this as we have chosen standard installation and not advanced installation. As we don’t want to have business impact for performance during EHP7 upgrade going that’s why we have chosen standard installation so that it will utilize minimum resources. And also whether business will function as normal during EHP7 upgrade going during pre-processing phase?

• As we are taking daily production backups whether we will still be able to take the production backup during EHP7 upgrade is going on? If yes, then whether it will be possible we can restore this backup just in case if we have any problem during pre-processing going on. And we don’t want to have business data to be in risky situation without backups.

• And also we have DR for our production system whether we can still continue replicating the logs files on DR server during EHP7 upgrade going on? Or we will have to stop the DR during EHP7 upgrade started? Or we can stop DR only during actual downtime or execution phase when shadow instance will overwrite the actual system.

• And also just in case if something goes wrong during upgrade going as it is creating shadow instance and all the changes are in shadow instance is it possible to remove the shadow instance or undo the EHP7 upgrade?

• And also after upgrading our test system to EHP7 after running SGEN we got syntax error for 421 objects. Do we will have to fix this before we can release the system for functional team testing?

• And also we have 4 application servers configured for our ECC6.0 production system with MaxDB as database and we will like to run EHP7 upgrade only on CI system and not on application server. So whether there will be any problem if we don’t use application server during EHP7 upgrade going?

Thanks,

Narendra

[Reagan · Accepted solution]

>>During EHP7 upgrade going on production system whether we will be able to move the transport request into production?<<

After the lock development phase you will not be allowed to bring in transports until you complete the upgrade.

>>As when we did the EHP7 upgrade testing during that time Initialization, Extraction, Configuration, Checks and Preprocessing taken 21days how we can reduce this as we have chosen standard installation and not advanced installation. As we don’t want to have business impact for performance during EHP7 upgrade going that’s why we have chosen standard installation so that it will utilize minimum resources. And also whether business will function as normal during EHP7 upgrade going during pre-processing phase?<<

21 days to complete the EHP7 update is not acceptable and that with the standard mode. The standard mode will create a shadow system and does the update on that system. A system with a standard resources on standard mode will let you complete the EHP7 update in a week.

>>As we are taking daily production backups whether we will still be able to take the production backup during EHP7 upgrade is going on? If yes, then whether it will be possible we can restore this backup just in case if we have any problem during pre-processing going on. And we don’t want to have business data to be in risky situation without backups.<<

You can take a backup before you start the EHP7 update. You should take backup (DB and SUM directory) before you start the downtime phase and finally one after you complete the upgrade.

>>And also we have DR for our production system whether we can still continue replicating the logs files on DR server during EHP7 upgrade going on? Or we will have to stop the DR during EHP7 upgrade started? Or we can stop DR only during actual downtime or execution phase when shadow instance will overwrite the actual system.<<

If there is a standby database at the DR site then keep the DB replication ON to get the standby database at the DR site synchronized. You need to make sure the Archiving is kept ON during the whole procedure. Apart from that you will need to have the kernel copied to the DR site and the profiles adapted as there wont be start profiles anymore.

>>And also just in case if something goes wrong during upgrade going as it is creating shadow instance and all the changes are in shadow instance is it possible to remove the shadow instance or undo the EHP7 upgrade?<<

Download the SUM guide and read the section about "Resetting the Software Update Manager"

>>And also after upgrading our test system to EHP7 after running SGEN we got syntax error for 421 objects. Do we will have to fix this before we can release the system for functional team testing?<<

If the errors are coming after the upgrade and SGEN execution then you should investigate why it is happening.

>>And also we have 4 application servers configured for our ECC6.0 production system with MaxDB as database and we will like to run EHP7 upgrade only on CI system and not on application server. So whether there will be any problem if we don’t use application server during EHP7 upgrade going?<<

You can keep the application servers running until you reach the downtime phase. Before you start the downtime phase you need to stop all AS's and isolate the central instance. Make sure you mark the option "Update Dialog Instances" in SUM.

[Former Member · Accepted solution]

Hi Reagan Benjamin,

Really appreciated your reply…I have two more questions as below,

1. During upgrade going in standard mode does business will be able to continue the day to day activities like earlier or will have some impact?
2. As you said EHP7 upgrade should be over in a week. Please can you let us know if we can still continue daily production backup? So that just in case if we need to recover the database in case of hardware failure? Say for e.g. if we take backup before EHP7 upgrade starts and after 3 days we got hardware problem and need to restore the backup in that case we can’t restore the backup taken of system before EHP7 upgrade started because then we will lose 3 days of business data?

Thanks,

Narendra

[Reagan · Accepted solution]

1 - The system will allow users to bring in transport requests until the lock development phase.

Users will be able to access the SAP system until the downtime phase.

2 - You can take database backup whenever you want. As long as you have the log and data backups you will be able to do point-in-time recovery.

[ibrahim_yooseff · Accepted solution]

Hi Reagen,

I am new to SAP basis Just a quick question how many days will take to upgrade ECC6 EHP 4 to EHP 7

Regards,

Ibrahim

[former_member182657]

Hi Narendra,

As has already detailed your query nicely,so kindly close the thread if answered.

Regards,