Problem in PARCONV_UPG phase

[Former Member]

Hello!

I'm stopped in PARCONV_UPG phase due to some errors in processes finished with RC=8. There are many logs to analyze, PARCONV.ELG, NCONVxx, PD...

Each file contains lot of errors... How can I analyze these files?

When I try to continue or retry this phase, a message is displayed as follow:

*****************************************************************************************

ERROR: 119 entries from aborted conversion found.

CAUTION: matchcode- and ICN-entries are not relevant!!!

The mass converter may be aborted (check with SM37), or some DB requests failed.

>>> DON'T DELETE THE ENTRIES IN TBATG !!! <<<

(entries are listed on the next page)

*****************************************************************************************

I saw SM37 but it don't have errors... Then, I think tables have problem...

Can anyone help me? Thank you in advance!

Best Regards,

André Koji Honma

[Former Member]

Hi Andre,

the other ones were easy, but this one cannot be solved without having a look into the corresponding files - I had these issues pretty often in the past - this always is specific and needs special treatment - mostly some tables were a bit inconsistent before the upgrade ...

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

[Former Member]

Hi Volker,

Yes, it means very critical, because I opened an OSS ticket from yesterday tomorrow and until now anyone couldn't found the root cause of this problem... :-((

Doesn't matter, I must waiting for a while... Thank you!

André

[Former Member]

Volker,

I can't believe!!! The issue was that user profile has not set a password...

I've restored user profiles from an entire system backup from an earlier i5/OS release, then, password was set to *NONE.

After setting a simple password on this USRPRF, SAPup run successfully the "problematic phase"... <:o)

Uffff!!! I'm relaxed now....... |:-D

Kind Regards,

André

[Former Member]

Just for all that need a help about this kind of error, see OSS note 576371.

Kind Regards,

André