cancel
Showing results for 
Search instead for 
Did you mean: 

Unicode conversion WAS 6.20 ABAP+JAVA question.

Former Member
0 Kudos

Hello gurus,

We have planned to make an unicode conversión of our CRM System.

It is WAS 6.20 SP 58 ABAP+JAVA in single code page and i would like to know if it is possible to make the conversion just in the abap schema (java is unicode!).

I do not know if at the moment of the uninstall of the instance and database, is possible to uninstall only the abap schema and not the Java schema.

Is it possible?? How would be the procedure in order to make the unicode conversion in the case of abap+java??

Many thanks and best regards,

Gonzalo.

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi,

Ideally the way you want it to be done is definitely not a SAP Best Practice and may jeopardize your system.

It is always better to do a UNICODE Conversion i.e a export using (R3load + Jload) on the source the UNICODE Converion takes place during the export. And, then import it using (R3load+Jload) in the target. You will also have to follow certain pre-/post- steps before and after a UNICODE Conversion. Although JAVA is always UNICODE, Jload takes care of it.

However, if you want to really test out a strategy to do a export/import of the ABAP only part. Test this strategy out before implementing it.

1. Do a hmogeneous system copy of your source system - try to use file system copy as for the JAVA part in WAS 6.20 a lot of SDM data exists in the file system.

2. Once copied and SAP is up and running. Drop the ABAP schema of the database - the ABAP and JAVA schemas have different names form WAS 6.20 onwards, the ABAP schema has a name SAP<SID> and the JAVA schema has a name SAP<SID>DB.

3.Now take an ABAP export of your source system and import it into the target system.

Once again, rigorously test this strategy out before you implement it.

Please award points if this was useful.

Thanks, Dibya

Former Member
0 Kudos

Hello,

Unfortunately you cannot really seperate the two, you must export the system in its entirety, but as you have pointed our java is already unicode. Sapinst will simply export this and not perform any conversion on it.

If you are considering just trying to copy the Java Schema to a new Unicode System this will not work, Java expecially needs an export and a migration controller has to run to allow the Engine to function on new hardware.

Regards,

David

Former Member
0 Kudos

Hi!

Basically it is possible to just drop all the tables belonging to the abap schema user. But this might only make sense for complete (inplace) reorganisation of the abap part. In terms of a unicode migration the database codepage will change. So this procedure is not a valid path. At least not if you use the same database for Abap and Java.

You should follow the Unicode Conversion/System Copy Guide to perform the migration.

Just have SAPInst to export the Java part, export the Abap part, create the unicode target system, import abap part, import java part.

/cheers

Edit: old message... nvm

Edited by: Christian Kaunzner on Jun 27, 2008 11:15 AM

Former Member
0 Kudos

can you help me please?

Many thanks,

Gonzalo