EHP4 ACT_UPG Error

[Former Member]

Hi,

i have a Probelm during the Upgrade ERP 6.0 to EHP4 in phase ACT_UPG.

This errors comming up.

~~ DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60007INECCDIMP.O61

~~ 1 ETP111 exit code : "8"

~~ DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60007INERECRUIT.O61

~~ 1 ETP111 exit code : "8"

~~ DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60007INFICA.O61

~~ 1 ETP111 exit code : "8"

~~ DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60007INFICAX.O61

~~ 1 ETP111 exit code : "8"

~~ DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60007ININSURANC.O61

~~ 1 ETP111 exit code : "8"

~~ DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60007INISCWM.O61

~~ 1 ETP111 exit code : "8"

~~ DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60007INISH.O61

~~ 1 ETP111 exit code : "8"

~~ DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-60007INISM.O61

~~ 1 ETP111 exit code : "8"

Many People say "choosing the option "Accept non- severe errors and repeat phase ACT_UPG" and Problems solved !

But how can i find out, if these are fatal errors ?

best regards

Steven

[sunny_pahuja2 · Accepted solution]

Hi Steven,

> Many People say "choosing the option "Accept non- severe errors and repeat phase ACT_UPG" and Problems solved !

> But how can i find out, if these are fatal errors ?

>

Yes, people are right. In case these errors are fatal errors then EHPI would not allow you to go to next phase.

So, you can choose option accept non-severe errors.

Thanks

Sunny

[markus_doehr2 · Accepted solution]

> > Many People say "choosing the option "Accept non- severe errors and repeat phase ACT_UPG" and Problems solved !

> > But how can i find out, if these are fatal errors ?

> >

> Yes, people are right. In case these errors are fatal errors then EHPI would not allow you to go to next phase.

>

> So, you can choose option accept non-severe errors.

yes - but I would not do that without checking what is wrong. One may need to execute XPRAs manually and maybe other things would need to be done. So I would never blindly move on without knowing what's wrong. I would also not move on if the problem occuring is not documented.

Markus

[Former Member]

Go to the upgrade log directory and search the activation log for lines with "E" in column two. On UNIX this would be:

grep '^.E' SAPA*.$SAPSYSTEMNAME

These are the objects that failed activation. You should research objects in the SAP name space. Standard advise is to repeat the activation phase until the number stops decreasing. Upgrade analysis counts each activation failure plus each package return code higher than 4.... but the way activation works since 4.x, each package gets the same RC (and in ECC 6 and above there can be hundreds of packages) and one activation error causes RC 8. In a development system there are always customer objects that fail to activate. Note these and report to the development team. Expect OSS notes that cover SAP objects and follow advise of these notes, then repeat activation and choose repair severe errors as others have suggested. There is a "severe" error option for the XPRAS* phase too. Use it. The idea is to get the upgrade in as fast as possible then fix it later when you have a fully functioning SAP environment.

Ken Chamberlain

the basis team at

University of Toronto

[Former Member]

Go to the upgrade log directory and search the activation log for lines with "E" in column two. On UNIX this would be:

grep '^.E' SAPA*.$SAPSYSTEMNAME

These are the objects that failed activation. You should research objects in the SAP name space. Standard advise is to repeat the activation phase until the number stops decreasing. Upgrade analysis counts each activation failure plus each package return code higher than 4.... but the way activation works since 4.x, each package gets the same RC and in ECC 6 and above there can be hundreds of packages. In a development system there are always customer objects that fail to activate. Note these and report to the development team. Expect OSS notes that cover SAP objects and follow advise of these notes, then repeat activation and choose repair severe errors as others have suggested. There is a "severe" error option for the XPRAS* phase too. Use it. The idea is to get the upgrade in as fast as possible then fix it later when you have a fully functioning SAP environment.

Ken Chamberlain

the basis team at

University of Toronto