why we should consider ENDIAN format while performing data migration across different platform


When copying a file between platforms you need to ensure that the Endian values match, big endian vs. little endian.

Windows and Linux x86 have the same Endian so need not to take care of this while performing data migration(data file)

Oracle RMAN also has a convert utility for changing Endian values.

just like below example

RUN {
CONVERT DATAFILE
‘/tmp/${DATABASE_NAME}system01.dbf’
FROM PLATFORM ‘Solaris[tm] OE (64-bit)’
FORMAT ‘/m001/oradata/${DATABASE_NAME}/${DATABASE_NAME}system01.dbf’;

CONVERT DATAFILE ‘/tmp/${DATABASE_NAME}undotbs01.dbf’
FROM PLATFORM ‘Solaris[tm] OE (64-bit)’
FORMAT ‘/m001/oradata/${DATABASE_NAME}/${DATABASE_NAME}undo01.dbf’;
}

when performing database migration we need to make sure that destination and source database has same endian type if not so then we use RMAN to convert our source files into destination endian file type.

endian type is nothing but just the way of storing bytes in multibyte data type.

Little and big endian are two ways of storing multibyte data-types ( int, float, etc). In little endian machines, last byte of binary representation of the multibyte data-type is stored first. On the other hand, in big endian machines, first byte of binary representation of the multibyte data-type is stored first.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s