Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

unsorted unload for cluster tables for non-unicode migrations


This is a request to help clarify a statement in SAP note 954268.

the note makes the following statements regarding codepage conversions:

begin quote****

If you convert the codepage, you must always unload cluster tables as sorted. The codepage is converted for the following actions:

non-Unicode --> Unicode

MDMP --> Unicode

Unicode (big endian) --> Unicode (little endian)

Unicode (little endian) --> Unicode (big endian)


End quote *******

I am doing a OS/DB migration from R/3 4.7x200 HPUX/ORA9.2.0.8 to WIN2003/MSSQL2005 without a codepage conversoin. I am using the latest 6.40 R3ldctl and R3load and distribution monitor.

IMO, the above quote implies you can do an unsorted unload if you are not doing a codepage conversion.

1.) Is this a correct assumption?

2.) If so, how do I ensure the cluster tables are unloaded unsorted? I have set the parameter 'unsortedExport=all' in the distribution_monitor_cmd.propertes. (The source hardware is very old, I want the target target hardware to do the majority of the work.)

Thanks for any feedback.

Joe Wilson

Not what you were looking for? View more on this topic or Ask a question