Skip to Content
avatar image
Former Member

Migration from HP-UX to Linux

Dear Community members,

                                            We are doing POC for migration of ECC from HP-UX  ( Code page ---> 4102 =  Big Endian) to Linux   ( Code page --> 4103 = Little Endian) platform with no DB change ( Oracle).My question is , although ECC on source system is Unicode, does this migration still be considered as Code Page conversion ? ( I am thinking code page conversion for H/W is happening in this case)  If so, Do I have to unload the cluster tables in sorted order always during code page conversion ?

954268 - Optimization of export: Unsorted unloading

  • Code page conversion
    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) ------> My scenario
  • Unicode (little endian) --> Unicode (big endian)

  Caution: For a code page conversion, the conversion must be carried out during the export to ensure that cluster tables are always exported immediately.

I have read the below thing in one of the document.

Note: If a code page conversion is performed, table clusters must be unloaded sorted. As of R3load 6.40 patch level 55 (compile date February 10, 2006) and R3load 7.00 patch level 10 (compile date February 10, 2006), R3load automatically ensures that table clusters are exported in sorted order during a code page conversion.

I request you  guys to shed some light on this topic.



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Oct 20, 2015 at 11:04 PM

    Hi Hari,

    This means you need to do a Heterogeneous System copy (to change the endianess), but you do not need to do a unicode conversion.

    Not sure if thats the answer that you needed.

    Regards, Juan

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hello Hari,

      The key warning you are zooming in on is "without ORDER BY PRIMARY KEY" ....... unusable for "some" databases. Bear in mind it's just a warning.

      As you are coming from and going to Oracle this is not a problem.

      DDLORA_LRG.TPL as you have seen will unload data *unsorted*. That said (and the note is correct), cluster tables will always be unloaded *sorted*. It's hard coded.

      So to summarise, even if you choose a unsorted unload, cluster tables will always be unloaded sorted.

      If you're a curious cat then check your active sessions during the export (CDCLS, EDI40 etc ....) and you'll see the "order by" statement in the active SQL.

      I hope I've cleared up some slightly muddy waters.

      ps: Please keep in mind that for your production run the migration has to be done by a certified OSDB consultant.