Migrating to different endianness

I recently moved a 2TB database from Linux, Oracle 11.1 to AIX, Oracle 11.2 using impdp with network_link and parallel options. The data was imported in about two hours and the indexes took another 7 hours. There was no downtime but we kept the users off the system while this was happening.

Here is the command I used on the new server:

nohup impdp system/secret NETWORK_LINK=olddb FULL=y  PARALLEL=25 &
Then you can run this to see which parallel process is importing which table:
impdp system attach
Import> status
Import> parallel=30 << this will increase the parallel processes if you want
I had created all the datafiles in the new database and created a db link named olddb beforehand. The servers were on the same local area network and the network was the bottleneck.


8 thoughts on “Migrating to different endianness

  1. Pingback: Migrating a 2TB database to a new operating system with different endianness – All Things Oracle

  2. The target hardware was a IBM P-Series virtual system with 48GB memory, (8) 6400MHz CPUs, (4) virtual Fibre Channel adapters, (1) 10Gb Ethernet port, with ASM on EMC Symmetrix VMAX. The source hardware was an Intel 32 core system with 16GB memory.


  3. Thanks for this overview…I’m trying to migrate from aix to Windows. I noticed that you created all the datafiles in the new database. Does the import map the source datafiles to the locations you created? In my case, would I need to do this also?


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 )

Google photo

You are commenting using your Google 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 )

Connecting to %s