Copyright (c) 2019, Oracle. All rights reserved. Oracle Confidential.

Migrating an Oracle E-Business Suite Database to Oracle Exadata Database Machine (Doc ID
1133355.1)

In this Document

Abstract
History
Details
Determining the Source Platform Endian Format
List of Platform Endian Formats by Platform
Summary
History
References

APPLIES TO:

Oracle E-Business Suite Technology Stack - Version 11.5.10.2 to 12.2 [Release 11.5.10 to 12.2]
Information in this document applies to any platform.

ABSTRACT

There are various options for migrating to the Oracle Exadata Database Machine as outlined in the presentation at Best
Practices for Migrating to Exadata Database Machine. This note is intended to assist in determining the best option for
migrating your Oracle E-Business Suite 11i or Release 12 database to the Oracle Exadata Database Machine.

HISTORY

See the table at the end

DETAILS

The factors in determining what migration options can be used for migrating an Oracle E-Business Suite database to
Oracle Exadata Database Machine are:

Source Platform Operating System

Source Platform Endian format (see Determining the Source Platform Endian Format)
Source Database release
Source Oracle E-Business Suite release

The target system is Oracle Exadata Database Machine with RDBMS 11.2, Oracle Real Application Clusters (RAC),
Automatic Storage Management (ASM) and the platform is Linux x86-64, little endian.
The Oracle Exadata Database Machine Supported Oracle E-Business Suite releases are:

11.5.10.2 (11i)
12.0.4
12.1
12.2
For required EBS database patches on Exadata see Document 1392527.1

Ideally, the goal is to choose a migration method that supports Oracle Exadata Database Machine best practices for
minimal downtime but this depends on the required business service levels.
The migration options can be categorized into two high-level categories:

1. physical migration
2. logical migration
with the following characteristics:

Physical Migration Logical Migration

• Data remains in datafiles (block-for-block) Data unloaded from source, loaded into Exadata database with SQ
• Database extent sizes remain the same

• Most methods are whole database migration Easier to migrate subset

• Transportable Tablespaces can be partial
• Inherit legacy database configuration

Easier to implement structural best practices

• Generally more restrictive Generally less restrictive

• Platform and version changes are restricted

The following table summarizes physical options outlined in Best Practices for Migrating to Exadata Database Machine as
they pertain to Oracle E-Business Suite:

Physical When to use

Migration
Option

Data Guard
Physical Source platform must be Linux, Solaris x86 or Windows (see Document 413484.1) and source on 1
Standby 12.1
Source database in ARCHIVELOG mode
NOLOGGING operations to the database are not permitted, i.e. FORCE LOGGING is turned on at the
database level

Transportable
Database Source system must be 11.2.0.4 or 12.1 and little endian
Stricter service level requirements that obviate the required downtime with Oracle Data Pump

Transportable
Tablespaces Any source platform
EBS Release 12 with source database RDBMS release 10gR2 (10.2.0.5) or higher
EBS 11i with source database RDBMS release 11.2
Service levels cannot tolerate a significant outage. Using transportable tablespaces instead of Orac
Data Pump export/import can significantly reduce the outage time for large (> 300 GB) EBS databa
Thorough testing will determine the precise outage time.
For a point of reference, tests on an Oracle Exadata Database Machine quarter rack with the Rapid
Install Vision database (about 300 GB) took about 12 hours. This time should remain about the sam
regardless of the amount of data in the database. This is because the metadata creation takes the
longest time in the migration process and accounts for the bulk of time.

Oracle E- Source platform must be Linux x86-64

Business
Suite Rapid
Clone
The following table summarizes logical options outlined in Best Practices for Migrating to Exadata Database Machine as
they pertain to Oracle E-Business Suite:

Logical When to use Reference

Migration
Option

Oracle • Migrating Oracle E-Business

Data Pump Any source platform Suite to Sun Oracle Database
Source database is RDBMS release 10.2 or higher Machine Using Oracle Data Pump
To implement Oracle Exadata Database Machine best practices paper
on the target • Document 741818.1
Service levels can tolerate a significant outage. Export/Import Process for Oracle
For a point of reference, tests on an Oracle Exadata Database E-Business Suite Release 12
Machine quarter rack with the Rapid Install Vision database Database Instances Using Oracle
(about 300 GB) took about 24 hours (export - 7:42; import - Database 11g Release 1 or 11g
16:42) using Network Storage and no dump file copy (i.e. the Release 2
export dump storage was mounted on the source and the • Document 557738.1
target). Export/import notes on
Timings will vary depending on your system configuration and Applications 11i Database 11g
increase as the amount of data increases.

• Oracle Not applicable today for E-Business Suite but are generally applicable • Using Oracle GoldenGate with
Data to other Oracle Exadata Database Machine migrations.. Please check Oracle E-Business Suite
Guard back periodically for updates as these different options become
Logical certified.
Standby
• Oracle
Golden
Gate
• Oracle
Streams
• Create
Table As
Select
(CTAS) or
Insert As
Select
(IAS)

For Oracle E-Business Suite 11i customers using an RDBMS version less than 10.2 the recommended approach is to first
upgrade to a supported RDBMS release, minimally 10.2, before choosing one of the above migration options.

Determining the Source Platform Endian Format

Identify your source platform endian format by running the following query on your source platform:
SELECT ENDIAN_FORMAT FROM V$TRANSPORTABLE_PLATFORM VTP, V$DATABASE VDB
where vtp.platform_id=vdb.platform_id;

List of Platform Endian Formats by Platform

column platform_name format A35

SELECT * FROM V$TRANSPORTABLE_PLATFORM order by 3,2;
PLATFORM_ID PLATFORM_NAME ENDIAN_FORMAT
----------- ----------------------------------- --------------
6 AIX-Based Systems (64-bit) Big
16 Apple Mac OS Big
3 HP-UX (64-bit) Big
4 HP-UX IA (64-bit) Big
18 IBM Power Based Linux Big
9 IBM zSeries Based Linux Big
1 Solaris[tm] OE (32-bit) Big
2 Solaris[tm] OE (64-bit) Big
21 Apple Mac OS (x86-64) Little
19 HP IA Open VMS Little
15 HP Open VMS Little
5 HP Tru64 UNIX Little
10 Linux IA (32-bit) Little
11 Linux IA (64-bit) Little
13 Linux x86 64-bit Little
7 Microsoft Windows IA (32-bit) Little
8 Microsoft Windows IA (64-bit) Little
12 Microsoft Windows x86 64-bit Little
17 Solaris Operating System (x86) Little
20 Solaris Operating System (x86-64) Little

20 rows selected.

SUMMARY

Continue to check MAA Best Practices - Exadata Database Machine for new white papers and updates

History

Date Descrption

10/3/16
Minimal update to indicate EBS R12.2 is supported on Exadata. More updates needed.

10/21/13
Added the statement about supporting RapidClone physical migration option from single node to Exadata

8/1/13
The Transportable Tablespaces (TTS) process was originally certified for the migration of E-Business Suite R12
11gR1 or 11gR2 to a target of 11gR2. This requirement has now been expanded to include a source database
https://blogs.oracle.com/stevenChan/entry/new_source_database_added_for.

4/24/13
Added "Using transportable tablespaces instead of Oracle Data Pump export/import can significantly reduce the
databases." to the Transportable Tablespace "When to use" cell.

10/25/12
Added MOS reference notes for EBS Data Guard setup and RAC cloning

7/5/12 Added point of clarification to the Transportable Tablespace migration option to note that time for even a small
because the metadata creation takes the longest time in the migration process."

5/9/12 Added Solaris x86 to te Physical Standby migration option 'When to use' column.

4/27/12 Moved Change Log to this History section.

3/2/12 Added reference to external Golden Gate article

11/2/11 Added EBS 11i Transportable Tablespace reference and fixed external links

11/10/11 Added reference to EBS R12 - Using Transportable Tablespaces for EBS Release 12 Using Database 11gR2 [131
Tablespaces"
Didn't find what you are looking for?