Skip to Content

I have encountered many errors/issues during my first EhP4 upgrade project on ERP6.0 landscape and spent lots of hours to resolve the issues. I just wanted to share those errors with solutions with my Basis friends for quick reference and to save the valuable time.

Note: When you are stopped in the middle of upgrade with any error, please look at the respective log first for the possible reasons. If you find the same symptom in the logs as I got, you can safely implement the solutions as listed below.

</p><p>Error#1: Upgrade failed during CHECKS phase with the following error message.</p><p>“There are dependencies between packages included into the procedure and the target release kernel. The release of tool disp+work needs to be at least 701”</p><p> </p><p>Solution:*

Take the backup of …/EHPI/abap/exe and exenew and unchar the latest target 7.01 release into ../EHPI/abap/exenew and repeat the phase where it stopped.

 

Error#2: Upgrade stopped at phase ACT_UPG with the following error message.

“Checks after phase MAIN_SHDRUN/ACT_UPG were negative!

Latest error code set: Unresolved requests in buffer <SID> Check logfiles ‘ACTUPG.ELG’ and ‘/usr/sap/<SID>/EHPI/abap/log/SAPehpi.ECO’”

</p><p>Solution:* ./stopsap_shd -t R3 -i DVEBMGS<XX> -r /usr/sap/<SID>/EHPI/abap -u SAPDCHSHD

./startsap_shd -t R3 -i DVEBMGS<XX> -r /usr/sap/<SID>/EHPI/abap -u SAPDCHSHD

 

Error#3: Upgrade stopped at phase ACT_UPG with the following error message.

“Checks after phase MAIN_SHDRUN/ACT_UPG were negative!

Latest error code set: Check logfiles ‘ACTUPG.ELG’ and /usr/sap/<SID>/EHPI/abap/log/SAPehpi.ECO’”

</p><p>Solution:* 1EEDO519X”Table” “BWCO_MD_CCTR” could not be activated

1EEDO519 “Table Type” “PUR_ORD_ERPPR_SPEC_ELM” could not be activated

2WEDO517 “Domain” “EBELN” was activated (error in the dependencies)

2WEDO517 “Domain” “EBELP” was activated (error in the dependencies)

2WEDO517 “Table” “AUFK” was activated (error in the dependencies)

2WEDO517 “Table” “PRPS” was activated (error in the dependencies)

2WEDO517 “Table” “T5ITCN” was activated (error in the dependencies)

As per note 1328978, we have ignored the error and resumed upgrade by choosing option “Accept non-severe errors and repeat phase ACT_UPG”.

 

Error#4: Upgrade failed at phase XPRAS_UPG during downtime with the following error message.

“Checks after phase MAIN_NEWBAS/XPRAS_UPG were negative!

Last error code set: Check logfiles ‘XPRASUPG.ELG’ and /usr/sap/<SID>/EHPI/abap/log/SAPehpi.ECO’”

</p><p>Solution:*

As per notes 1245473 and 1301695, we have resumed upgrade by choosing option “Accept non-severe errors and repeat phase XPRAS_UPG”.

 

Error5: Upgrade stopped in phase TABIM_POST.

</p><p>Solution:</p><p>We have reviewed the log LONGPOST.LOG and found that few BADIs are not activated during the process. We had them activated by ABAP team.</p><p> </p><p>Error#6: Upgrade failed in Pre-processing phase with the following error message.</p><p>“ERROR: Unexpected message (s) of “tp gettrbatent”.</p><p>                TRBAT entry indicates a finished batch job.”</p><p> </p><p>Solution:*

Run the following command from /usr/sap/trans/bin directory with SIDADM.

tp getprots <SID> pf=TP_DOMAIN_<SID>.PFL

</p><p>Error#7: Phase MAIN_NEWBAST/TABIM_POST during downtime has been running from long time which is abnormal.</p><p> </p><p>Solution:*

We have verified the system logs (SM21) and found that Central Instance was not assigned to default batch group SAP_DEFAULT_BTC in SM61. As soon as we added CI to the default group, this phase has finished successfully in very few minutes.

 

Error#8: Upgrade failed at phase MAIN_SHDRUN/ACT_UPG during preprocessing with the following error message:

Checks after phase MAIN_SHDRUN/ACT_UPG were negative!

Last error code set: File ‘/usr/sap/<SID>/EHPI/abap/bin/ABCK_700.BUF’ does not exist. No such file or directory Check logfiles ‘ACTUPG.ELG’ and ‘/usr/sap/<SID>/EHPI/abap/log/SAPehpi.ECO’.

 

Solution:

Executed the following command with SIDADM and repeated the phase.

chmod 777 /usr/sap/<SID>/EHPI/abap/bin/ABCK_700.BUF</p>

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply