cancel
Showing results for 
Search instead for 
Did you mean: 

Unicode migration last step

Former Member
0 Kudos

Hi all,

I have performed a unicode migration, now SAPINST has to perform the 2 last steps ( run abap programs via RFC ).

Sapinst returns an error about failed rfc logon.

I tried to logon with GUI and I have these errors:

I receive the popup window with the license informations and the copyright info.

With this popup still open ( and it's not possible to close it ) on the gui it's shown this message:

"Status RGHT of the user interface SAPMSYST missing."

If I press enter I can see a compiling message for

CL_R3STANDARD_PERSISTENCE=====CP

and newly "Status RGHT of the user interface SAPMSYST missing.".

and now I'm in a loop.

In the work process log I can see these error messages:

"A *** ERROR => Syntax error in program CL_R3STANDARD_PERSISTENCE=====CP [abgen.c 1442]

A *** ERROR => > Include CL_ENH_UTILITIES==============CU line 32 [abgen.c 1444]

A *** ERROR => > The type "GBADI_IMPL_ACTIVE" is unknown. [abgen.c 1446]"

I have just updated DW to the last level, deleted sql packages and cleared abap load and screen load.

I remember something similiar during OS/DB migration from AS/400 to windows, but it was a 40B release and I remember that there was a parameter to tell system that cluster tables where in EBCDIC code before and about clear TCPDB table before starting the migrated system.

Now I have no other idea...

I have the system running and I can't log on !!

Please help me..

Thanks

Amilcare

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Michele,

I'm sure, that this has nothing to do with your migration on 4.0b, even parts of these tables are still in EBCDIC - even on Unicode.

You are having the issue, that a few tables are empty or not full enough in my eyes. At the current point, you should be able to logon to the system, because SAPinst does nothing else.

=> You need to make it happen to logon first !

What I see above, some status are missing (table D3456L ?) etc. So, I guess, that something bad happenend during export or import. I would check the logs for these kinds of tables (reposource, dynpsource, D34..., etc.)

Then, I'm pretty sure, you need SAP support ... or you do the stuff again ...

Regards

Volker Gueldenpfennig, consolut.gmbh

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