Data export and import

[Former Member]

Hi all,

We are upgrading our system from 4.6 (non-unicode) to ECC 6.0(unicode). while upgrading we have to export some tables to new system. We try to transport table using by Oracle tools but we couldn't success because of some characteristics which are non-unicode. Some characters couldn't be seen as we wait to see in unicode system. If we use R3trans, system automatically convert non-unicode characteristics to unicode characteristic but it takes a long time that we can't afford. Could you please tell me how I can export the tables which have 650 gb data from non-unicode system to unicode system.

Thanks in advance and best regards.

[Former Member]

Hi,

check out following link.

[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/82c445c2-0d01-0010-4ab2-fc7e1a25bea2]

Hope this helps.

Manoj

[stefan_koehler]

Hello Aykut,

the first and important thing is .. You need a SAP certified OS/DB migration expert to get support.

> We try to transport table using by Oracle tools but we couldn't success because of some characteristics which are non-unicode

That's not the way it works. You have to use R3load.

> If we use R3trans, system automatically convert non-unicode characteristics to unicode characteristic but it takes a long time that we can't afford

You mean R3load not R3trans. If you don't have the time you have to tune your export/import procedure. There are many ways howto do it (Distribution Monitor, Table Splliter, Define access pathes, direct load, etc.)

> Could you please tell me how I can export the tables which have 650 gb data from non-unicode system to unicode system.

Just one short answer: R3load

Regards

Stefan

[Former Member]

Hello,

We are not migrating our database. We installed a new system which is unicode. So we cannot export and

import all data from old system. We need just some big sized tables. Tables are big, so we cannot transport them. How can we use R3load for a scenerio like this? Is there a manual for R3load for export and import

of indiviual tables. We have to transport them very fastly because of downtime requirements.

Best Regards,

Ali AVCI

[markus_doehr2]

> We are not migrating our database. We installed a new system which is unicode. So we cannot export and

> import all data from old system. We need just some big sized tables. Tables are big, so we cannot transport them.

The only tool available that might to this conversion in one step is R3trans. R3trans can not run in parallel on the same table so you will have to wait until the export is finished.

R3load will do a complete conversion during export, it can run in parallel on the same table (if you used R3ta to split the table) but it can't run standalone since it requires other tables in the backend system do to that conversion. Basically R3load need to know for each word/character the codepage to convert correctly.

With a correct set up table splitting and parallel unload/load one can do a Unicode conversion for a big system in time, this requires however a good preparation.

What you are intending to do is no standard requirement and hence no standard tools exist for that.

Why are you going to import just a few tables for an "upgrade"?

Markus

[Former Member]

You cannot do that way. The correct way is to get the SAP migration kit, which use R3load program. It exports all data into filesystem and then loads it into new SAP unicode system