How Transportable Databases and Transportable Tablespaces handle endian formats

We're about to copy a database (Oracle 10g) from HP-UX to Linux. The database size is 1 TB.

I want to try this copy via Transportable Databases. However, the endian formats are different (HP-UX: big, Linux: little). According to the documentation this is not possible (not even with RMAN convert).

However in the documentation it is mentioned that Transportable Tablespaces with different endian formats can be used (while using RMAN convert). Is that true? Is there a difference in the way Transportable Databases and Transportable Tablespaces handle issues regarding different endian formats?

    Requires Free Membership to View

    Login

As you have stated, the endian-ness of the two systems are different. You can use RMAN to convert the tablespace to the appropriate endian-ness. Simply use the following RMAN commands:

RMAN TARGET /
RMAN > CONVERT TABLESPACE users
2> TO PLATFORM 'Linux IA (32-bit)'
3> FORMAT '/temp/%U';

The above assumes that a directory called /temp exists on your server. It is easiest to do this on your source server. The converted files will be transferred to your Linux system and can then be plugged into the tablespace there. For more details, see this document.

This was first published in February 2007

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.
    Back to top