EHP4 upgrade

[Former Member]

Dear all!

We are upgrading our ECC6 from EHP3 to EHP4, using SAPEHPI. on phase "Activates ABAP Dictionary customer objects" we get issue - it is more then 26 hours long yet. CPU usage now is 5-10%. Is it normaly?

sapehpi.log

-

---

CURRENTPHASE MAIN_SHDRUN/ACT_UPG

...started at 20090811155728

1. SPDD is not necessary in this system for phase ACT_UPG

2. Reading Parameter File "F:\EHPI\abap\bin\ACTUPG.TP0" at 20090811155729

3. Reading Parameter File "F:\EHPI\abap\bin\APPEND.APP" at 20090811155739

...begin processing at 20090811155739

#

1. ************************* SAPehpi started in UPGRADE mode *************************

2. This is SAPehpi version 7.10/2 patch level 26.001 compile time 01:10:01 Jul 21 2009.

3. This is UNICODE SAPehpi!

4. Running in graphics mode server.

5. GUI reports feature 'dialogue' as 'enabled' level 1, user said 'unknown'.

6. GUI reports feature 'html' as 'enabled' level 1, user said 'unknown'.

7. GUI reports feature 'console' as 'unknown' level 0, user said 'unknown'.

8. GUI reports feature 'progress' as 'enabled' level 1, user said 'unknown'.

9. GUI reports feature 'unitcontrol' as 'enabled' level 3, user said 'unknown'.

10. GUI reports feature 'remotecontrol' as 'enabled' level 1, user said 'unknown'.

11. GUI reports feature 'synchronization' as 'enabled' level 2, user said 'unknown'.

12. GUI reports feature 'mid' as 'enabled' level 2, user said 'unknown'.

13. GUI reports feature 'evaluation' as 'unknown' level 0, user said 'unknown'.

14. Reading Parameter File "F:\EHPI\abap\bin\DBSYNC.PAR" at 20090812102831

15. Reading Parameter File "F:\EHPI\abap\bin\TRATTR.LST" at 20090812102831

16. Reading Parameter File "F:\EHPI\abap\bin\TRGROUP.LST" at 20090812102831

17. DB-functions initialized for 'MSSQL'.

Current unit is 'PRE-EXECUTE', next unit is 'PRE-EXECUTE'.

-> decided to continue with unit PRE-EXECUTE.

1. Reading Parameter File "F:\EHPI\abap\bin\DBSWTC.PAR" at 20090812102835

...begin dialogue at 20090812102837

...end dialogue at 20090812102845

..answered at 20090812102845.

-> decided to try again.

Execution of MAIN module "Shadow System Operations: SPDD and Activation" begins at 20090812102846

CURRENTPHASE MAIN_SHDRUN/ACT_UPG

...started at 20090812102846

1. Reading Parameter File "F:\EHPI\abap\bin\ACTUPG.TPP" at 20090812102847

...begin processing at 20090812102847

-

---

[Former Member]

A better way to check is to check the logs. Sort them by date.

i've check logs and find next

>> 2009/08/11 15:57:28 START OF PHASE MAIN_SHDRUN/ACT_UPG

running F:\EHPI\abap\exe\tp.exe pf=F:\EHPI\abap\bin\SHADOW.TPP checkimpdp TPR
Collecting adjustments ...
Collection done - creating cofile ...
running F:\EHPI\abap\exe\tp.exe pf=F:\EHPI\abap\bin\ACTUPG.TPP put TPR


>> Current module status: stopped in MAIN_SHDRUN/ACT_UPG
>> Waiting for request handler...
>> Received 'next' action for unit 'PRE-EXECUTE'.
>>>> Repeat Phase <<<<


RESTART: Stopped in phase MAIN_SHDRUN/ACT_UPG


01)  *  Repeat phase ACT_UPG to continue at the point it stopped
02)  -  Initialize phase ACT_UPG to restart it from the beginning
03)  -  Exit this program
Choose action: Repeat phase ACT_UPG to continue at the point it stopped

Execution of MAIN module "Shadow System Operations: SPDD and Activation" begins at 20090812102846


>> 2009/08/12 10:28:47  START OF PHASE MAIN_SHDRUN/ACT_UPG

running F:\EHPI\abap\exe\tp.exe pf=F:\EHPI\abap\bin\ACTUPG.TPP put TPR

Yes today in the morning we need to restart our server, but when i start EHPI again after restarting i've choose

Repeat phase ACT_UPG to continue at the point it stopped

[markus_doehr2]

> Yes today in the morning we need to restart our server, but when i start EHPI again after restarting i've choose

> Repeat phase ACT_UPG to continue at the point it stopped

It's a very bad idea to restart a system that is in the middle of an upgrade; the syste may be left in an inconsistent state...

You check SAPehpiConsole.log - right - so the phase is still running.

Check the tmp and log directory again, you will most likely find a big file with SAPK-.....AAAA.<SID>

Markus

[Former Member]

Yes, you right, I check SAPehpiConsole.log and in tmp directory there is the large file "SAPA-701DDINSAPBASIS.TPR"

Edited by: Aleksey Dobrynin on Aug 12, 2009 12:35 PM

[markus_doehr2]

> Yes, you right, I check SAPehpiConsole.log and in tmp directory there is the large file "SAPA-701DDINSAPBASIS.TPR"

Check that file - it should be updated more or less regularly. As long as this happens is the upgrade still running.

Markus

[Former Member]

The last time that file was updated is 07-58 am, but i restart the upgraiding process at 10-35 am. Is It means that upgaiding not still running?

[markus_doehr2]

are other files updated (in tmp or log)?

Markus

[Former Member]

There are no files theese files in tmp directory. In log directory the last modify date of files is 10-38am.

[Former Member]

Hi

Just some input to this Thread.

I have experienced runtimes of between 12-36 hours for the phase ACT_UPG. The manual selection of parallel processing does have a positive influence on this phase but no way is it a defined solution to the enormous runtimes that one experiences during the EHP4 upgrade. Its a painfully slow and time consuming task.

Regards

Deena Naidoo

[Former Member]

i've just log on to shadow system and executed transaction sm37. i have only one active job "RDDMASGL", but duration of this job is 77.937sec

[markus_doehr2]

Yes.

As I wrote, the process is subsequently repeated.

A better way to check is to check the logs. Sort them by date.

Markus

[Former Member]

Thanks, Markus

but may be the phase "Activates ABAP Dictionary customer objects" is halted? or in this case i'll get error message form ehpi?

[markus_doehr2]

> but may be the phase "Activates ABAP Dictionary customer objects" is halted? or in this case i'll get error message form ehpi?

To seeif it's still running check the logfiles (EHPI\abap\log and EHPI\abap\tmp)

If it would have stopped, you'd have got an information through EHPI.

ACT_UPG runs in the shadow instances, it activates all objects that were freshly imported. If you used the standard configuration you have three batch processes doing that. Because there exist dependencies and some hundred thousand objects have to be activated in a specific sequence, it takes quite a lot of time.

Markus

[markus_doehr2]

> We are upgrading our ECC6 from EHP3 to EHP4, using SAPEHPI. on phase "Activates ABAP Dictionary customer objects" we get issue - it is more then 26 hours long yet. CPU usage now is 5-10%. Is it normaly?

If you chose the default settings - yes (they are very low).

Markus