Transportable Database 11gR2 Certified with E-Business Suite 11i, 12.0, 12.1

Screenshot of cover page for MAA whitepaper on platform migration maapaper.png
Platform migration is the process of moving a database from one operating system platform to a different operating system platform. You might wish to migrate your E-Business Suite database to create testing instances, experiment with new architectures, perform benchmarks, or prepare for actual platform changes in your production environment.

Database migration across platforms of the same "endian" format (byte ordering) using the Transportable Database (TDB) process is now certified with Oracle Database 11gR2 ( for:
  • Oracle E-Business Suite Releases 11i (
  • Oracle E-Business Suite Release 12.0.4 or higher
  • Oracle E-Business Suite Release 12.1.1 or higher
This EBS database migration process was previously certified only for 10gR2 and 11gR1.

Comparing Export/Import to Transportable Database

The supported way to accomplish this in prior releases of the Oracle database has been to export the data from the database on the old platform, create a new database on the new platform, and import the data into the new database. This process could take a number of days for a large database.

Transportable Database can be used to reduce the amount of time required to migrate a database between platforms that share the same "endian" format. Note that if the endian format is different between the source and target platforms, then Transportable Database cannot be used. For generic databases, a different method, such as Streams, Data Pump, or Cross-Platform Transportable Tablespaces must be used instead.  For E-Business Suite databases, only the Export/Import option is a viable fallback if the Transportable Database feature can't be used for your source and target platforms.

The reductions in migration times can be significant. For example, a test database within the Maximum Availability Architecture (MAA) High Availability Lab was migrated to a new platform using Data Pump export and import in 74 minutes. The same database was migrated using Transportable Database in 37 minutes, a 50% reduction in migration time.

What platforms are support for Transportable Databases?

Suitable target platforms can be verified by querying the view V$DB_TRANSPORTABLE_PLATFORM using sqlplus (connected as sysdba) on the source platform:
SQL> select platform_name from v$db_transportable_platform;
If the intended target platform appears in the output, Transportable Database can then be used to migrate the database to this target. Otherwise, an alternative such as export/import should be used instead.

Cross-Platform Transportable Tablespaces (XTTS) not certified yet

Please note that an alternative database technology known as Cross-Platform Transportable Tablespaces (XTTS) to migrate data between platforms of different endian formats is not yet certified with Oracle E-Business Suite.

Oracle's Revenue Recognition rules prohibit us from discussing certification and release dates, but you're welcome to monitor or subscribe to this blog for updates, which I'll post as soon as soon as they're available.   

Related Articles


While reading: Comparing Export/Import to Transportable Database

"Note that if the endian format is different between the source and target platforms, then Transportable Database cannot be used. For generic databases, a different method, such as Streams, Data Pump, or Cross-Platform Transportable Tablespaces must be used instead. For E-Business Suite databases, only the Export/Import option is a viable fallback if the Transportable Database feature can't be used for your source and target platforms"

The last sentence "For E-Business..." what about 'Transportable Tablespaces Certified for EBS 11i'?

This confuse me, on this post "Transportable Database 11gR2 Certified with E-Business Suite" tells me if the target and source are different endian, my only choice will be to use export/import, while on the post titled "Transportable Tablespaces Certified for EBS 11i" specify "Database migration across platforms of different "endian" (byte ordering) formats using the Cross Platform Transportable Tablespaces (XTTS) process is now certified for Oracle E-Business Suite Release 11i ( with Oracle Database 10g Release 2. This process is sometimes also referred to as transportable tablespaces (TTS)."...and "Moving data using transportable tablespaces can be much faster than performing either an export/import or unload/load of the same data."

Which post is correct, if I can not use the Transportable Database, because the target/source have different endian, then I should only use export/import, or use TTS as the second post implies?

Any help will be really appreciated.

Regards, CRJ.

Posted by Carlos Raul Jimenez on September 29, 2010 at 01:05 AM PDT #


You should consider this blog to be like a newspaper, with information in older articles being superceded by later articles. This later article about XTTS takes precedence; the latter is certified and supported now.


Posted by Steven Chan on October 01, 2010 at 06:36 AM PDT #


We are running our R12.1.2 production Instance on Windows 2003 32 bit and migrating to Linux 5 using Transportable database.

After Migration OLAP objects got INVALID. How can i determine in Source Instance all OLAP objects were dropped before
migration? I am suspecting that there would left over objects due to this OLAP reinstall failing on LINUX.

Please advise

Dba_registry status:-
OLAP Analytic Workspace REMOVING(why it is showing REMOVING, It suppose to be REMOVED)

Invalid Objects:-



Posted by Praveena on December 22, 2010 at 02:31 AM PST #

Do we need to de-install OLAP from source instance(R12.1.2 with 11gR1) for Migration from windows to linux using Transportable database.

We dont have any User defined OLAP Anlaytical Workspaces, We have System AWS in the system.

I have 2 SRS with oracle. One analyst says you dont need to delete and other says you need to.

Please advise

Posted by Praveena on December 23, 2010 at 02:49 AM PST #


I'm sorry to hear that you're encountering issues with Transportable Database. Please drop me an email (or post a comment here) with your two Service Request numbers. I'll ask someone from our Platforms Engineering team follow up with the Support engineers assigned to your SRs to straighten this out.


Posted by Steven Chan on December 27, 2010 at 04:53 AM PST #

Thanks Steve. I have sent an email with SR numbers.

Posted by Praveena on December 27, 2010 at 10:29 PM PST #

We successfully migrated R12.1.2 application from Windows to Linux using TDB.

Thanks for all your help..!!!

Praveena Jasti

Posted by Praveena on January 21, 2011 at 02:18 AM PST #


Congratulations! Glad to hear it went well.


Posted by Steven Chan on January 21, 2011 at 07:41 AM PST #

We need migrate Oracle E-Business Suite Release 12 (12.0.6) using Oracle Database 10g Release 2 ( from Solaris SPARC to Linux RHEL 64 x86. These plataforms has different endianness.
Is this case already certified?
If no, is export/import the only method?
My Oracle Database has 1,5TB and downtime will be very large using export/import.
Any ideas, please?
Thank you.

Posted by Edson on February 01, 2011 at 07:20 PM PST #

Hi Edson -
Since you will be going to a platform of a different endian format and you're on R12/10gR2, the only currently certified methodology for migrating your EBS database is to use export/import (datapump). The transportable tablespaces (XTTS) process for migrating across endian formats is only certified for migrations.
We are also planning an XTTS certification of EBS R12 with 11gR2, and the certification effort is in progress. We cannot share expected dates due to our Revenue Recognition policies, but please continue to monitor this blog site or feel free to touch bases with me periodically on this effort.

Posted by John Abraham on February 07, 2011 at 02:56 AM PST #

Hi, can you let us know if using XTTS for EBS 11i with 11gR2 is certified now?


Posted by Kiran on June 27, 2011 at 12:39 AM PDT #

Hello Kiran -
No, it's not currently certified - the certification of DB features such as XTTS is reflected in our My Oracle Support certification matrix (by selecting EBS 11.5.x against a DB release or feature). This currently only shows certified with DB 10gR2 Transportable Tablespaces.
We do have plans for an 11i certification with 11gR2 in the future - please stay tuned to entries in this blog or send me your details and I will notify you as to when it's available.
Have you tried export/import (datapump), and how long does that take?

Posted by John Abraham on June 27, 2011 at 04:14 AM PDT #

Hi, we are in the process of migrating our ebs11i database( from hpux to linux (Using Transportable Tablespaces for EBS 11i Using Database 11gR2 [ID 1366265.1]). The migration was succesfull without any major issues, but, the data pump export of "transportable table set" alone took 8 hours which is incredibly long. Is this an expected behavior? This is actually offsetting the advantage of using this method.. The same tts set using a normal exp took around 90mins. Any thoughts/inputs on this will be greatly appreciated.


Posted by guest on January 19, 2012 at 10:44 AM PST #

hi Kiran -
This is unexpected and has not been our experience while testing XTTS - it could be dependent on the particular data you have in your environment.
My advice is to file a Support Service Request against the DB export/import team and follow up with them to file an appropriate bug for ST development to take a look at.
Note that the traditional export/import is not supported with 11g except for specific cases as noted in the TTS doc (for global temporary tables) and the DB doument:

Posted by John Abraham on January 20, 2012 at 03:21 AM PST #

John, appreciae your response. i opened an SR with the export/import team and provided them with trace files of the export session. They indicated it could be becuase of a possible bug (12728995) and are filing for a patch since there is none available right now for hpux.
i will update the blog if the patch helped to resolve the issue.


Posted by guest on January 20, 2012 at 04:37 AM PST #

Hi, the patch for bg 12728995 didnt help to resolve the issue. we tried patch 9625849 which didnt help either. Now support is looking at Bug 12701533.

While running the xport, we did a trace and found that it spends majority(90%) of the time at the below stage.

Any help would be appreciated.

*** 2012-01-29 09:17:36.872
rowtag: ROW objnum_count: 0 callout: 1 Bind count: 0 Bind values:
META:15:28:45.531: get_xml_inputs TRANSPORTABLE_EXPORT/PLUGTS_BLK:


Posted by guest on January 31, 2012 at 06:53 AM PST #


I'm sorry to hear that you've encountered an issue with this.

We can provide general conceptual guidance here, but I'm afraid that this blog isn't the best place to get technical support for specific issues like the one that you're working through.

Please feel free to forward your Service Request number to me if it gets stuck in the support process for some reason.


Posted by Steven Chan on January 31, 2012 at 11:40 AM PST #

We currently have an EBS R12.1.3 with database on HP-Itanium(64-bit) servers and we are planning to migrate to EBS R12.1.3 with database on Linux 64-bit(RHEL 6.5) servers.

As part of that, we would like to know the best and certified method of migrating the EBS database( from HP-Itanium ( RAW devices) to on Linux 64-bit (ASM).

I came across the below methods,
1) Full Transportable Tablespaces (export/import)
2) Cross platform Transportable Tablespaces (with Cross platform Incremental backups)

but cannot see anywhere whether either of the above methods are certified for EBS R12.1

Can someone please throw some light on this?

Posted by guest on November 07, 2014 at 05:36 AM PST #

Hello guest -
It appears that there are two options for the database migration open to you:
1) Migrate using export/import (datapump) following the MOS Note 1585256.1, to export from the HP 11gR2 source and import into the Linux 12c target DB.
2) For very large databases (~1TB+), Transportable Tablespaces (TTS) may be the better option as you wouldn't be doing a logical migration of all data (only the metadata). Unfortunately TTS is not yet certified for migrations to a 12c target DB, though this is planned for the future. What you can do is migrate with TTS to a 11gR2 DB on the Linux target platform (MOS Note 1311487.1), and then upgrade to 12c following the 12c upgrade MOS Note 1524398.1.

Posted by John Abraham on November 12, 2014 at 10:03 AM PST #

Thanks a lot John for your response.

I appreciate the fact that TTS is not yet certified for migrations into 12c DB.

Does that mean "Full Transportable Tablespace" migration is same as "Transportable Tablespace (TTS)" migration?

The reason I ask is "Full Transportable Tablespace" is a feature in 12c and my concern was that I couldn't see anywhere to say its certified with EBS R12.1

The SR I raised came back saying it's not..yet. Can you please confirm that?


Posted by sree on November 13, 2014 at 01:24 AM PST #

Hi Sree -
They are different - Full Transportable export/import migration is a new feature in 12c designed to work with Pluggable databases as a migration destination. See:
We have not fully explored this migration technology, and are not yet able to say if can proceed with a certification exercise. Also, it should be noted that EBS is not yet certified with the multi-tenant option of EBS 12c.

Posted by John Abraham on November 17, 2014 at 02:46 PM PST #

Thanks John,

Yes, I reviewed that document and I was tempted to use the FTTS method based on the below line from that document.

"Note that, while this white paper focuses on
the use of full transportable export/import in a pluggable database environment, this feature
can be used generally for migrations to a Oracle Database 12c non-CDB database as well."

As the document highlights, FTTS uses the best features of Datapump and TTS together. Both the Datapump and TTS are certified methods for migrating an EBS database. Based on those facts, do you think its a good idea to take this approach over a conventional Datapump method?

I am not keen on the "upgrade_to_11gR2-migrate_from_HP-upgrade_to_12c" method as its appears very tedious and time consuming(downtime constraints).

This FTTS feature appears a perfect solution for our scenario but is a bit disappointing that we are unable to use it.

I just hope the certification for EBS with this feature of 12c comes out soon.


Posted by sree on November 17, 2014 at 04:59 PM PST #

Post a Comment:
Comments are closed for this entry.


« May 2016