2021-07-17: E-Business Suite Migration Strategy to OCI

This post is going to talk about migration strategy for E-Business Suite (EBS) to Oracle Cloud Infrastructure (OCI). I am trying to cover some basic strategies which can give you an idea and build a strategy for EBS migration.

Scenario 1: Application and Database – Lift & Shift

This is the most common scenario you will find. It should be picked if the sources are meeting below criteria:

  • The Source Operating system is of supported version of OCI i.e. Linux flavor or Windows.
  • The Source application version should be either 12.1.3 or 12.2.x
  • The Source database version should be 11.2.0.4 or above

The landing platform for EBS application and database can be:

  • Compute Instance
  • Database Cloud Service (DBCS) or Exadata Cloud Service (ExaCS)

I would recommend hosting the application on Compute Instance and Database on either DBCS or ExaCS.

For performing the migration, you can use EBS Cloud Migration Tool or you can do it manually. The EBS Cloud Migration Tool is GUI based web interface that can perform EBS deployment in OCI using the backup copied to Object Storage. This tool is useful when you can afford two to three days of downtime.

The alternative way is to perform the migration manually using ADCLONE utilities. While performing Production migration you can use DataGuard setup and create a Stand By Database in OCI. During the Cutover you perform Failover of Database and bring up your application. In this way, you will end up reducing the Cutover window.

Scenario 2: Application – Lift & Shift, Database – Upgrade

In this scenario, you will end up having a fair bit of downtime window, as you will have to upgrade the database. The scenario should be picked if the source is meeting the below criteria:

  • The Source Operating System is of supported version of OCI i.e. Linux flavor or Windows.
  • The Source application version should be either 12.1.3 or 12.2.x
  • The Source database version is either 11.2.0.4 or 12.1.0.2

The landing platform for the EBS application and database will be the same as scenario 1, except the database target version is 19c.

You will first start with Database upgrade and migration. To perform both tasks together, you can use Transportable Tablespace. This is supported by Oracle and is well documented in:

  • Oracle E-Business Suite 12.2 Platform Migration from On-Premises to Oracle Cloud Using Transportable Tablespaces with Oracle Database 19c (Doc ID 2725558.1)
  • Oracle E-Business Suite 12.1 Platform Migration from On-Premises to Oracle Cloud Using Transportable Tablespaces with Oracle Database 19c (Doc ID 2725557.1)

Follow the steps as per the above documents and you will be able to perform successful migration and upgrade of database to 19c.

Scenario 3: Application – Rehosting and database – Rehosting

Here, both the EBS application and database are hosted on a non-supported platform on-premise. In OCI you will have to host the application on Linux flavour operating system. The scenario should be picked if the source is meeting the below criteria:

  • The Source Operating System is of non-supported version of OCI i.e. Solaris or AIX
  • The Source application version should be either 12.1.3 or 12.2.x
  • The Source database version is 11.2.0.4 and above.

The EBS application and database landing platform will be the same as scenario 1, but for the database, the target version will be 19c.

Like scenario 2, here also you will first migrate the database to the latest version i.e. 19c. You can follow the mentioned documents in scenario 2. For application, you will have to perform cross-platform migration. The Application migration steps are list in Oracle Support Documents.

  • Application Tier Platform Migration with Oracle E-Business Suite Release 12 (Doc ID 438086.1)
  • Application Tier Platform Migration with Oracle E-Business Suite Release 12.2 (Doc ID 2048954.1)

Scenario 4: Application (11i) and Database – Lift and Shift

In this scenario, the operating system is at the supported level of EBS 11i, the same operating system version is not supported in OCI. The scenario is applicable if the source is meeting the below criteria:

  • Application version is 11i
  • Database version is 11g and above
  • Operating system is Linux or Windows flavor

Here the landing platform will be Oracle Cloud Vmware Service (OCVS), where you can host older versions of operating systems in OCI. The application and database VM will be getting migrated to OCVS using Vmware technology. But, it’s recommended to migrate Oracle Database to a VM or DBCS to save on licensing costs.

In Summary below can be the migration strategy:

Source EBS VersionSource DB VersionTarget EBS VersionTarget DB VersionTarget PlatformComplexity
12.1.3 or 12.2.x
(RHEL/OEL 6.x, 7x)
12.1.0.2 or 19c
(RHEL/OEL 6.x,7.x)
12.1.3 or 12.2.x
(RHEL/OEL 6.x, 7x)
12.1.0.2 or 19c
(OEL 7.x)
EBS – Compute Instance
DB – DBCS/ExaCS
Simple
12.1.3 or 12.2.x
(RHEL/OEL 6.x, 7x)
12.1.0.2 or 11.2.0.4
(RHEL/OEL 5.x)
12.1.3 or 12.2.x
(RHEL/OEL 6.x, 7x)
19c
(OEL 7.x)
EBS – Compute Instance
DB – DBCS/ExaCS
Medium
12.1.3 or 12.2.x
(AIX, Solaris)
12.1.0.2 or 19c
(RHEL/OEL 6.x,7.x)
12.1.3 or 12.2.x
(RHEL/OEL 6.x, 7x)
19c
(OEL 7.x)
EBS – Compute Instance
DB – DBCS/ExaCS
Complex
11.5.10.2
(RHEL/OEL 5.x)
12.1.0.2 or 11.2.0.4
(RHEL/OEL 5.x)
11.5.10.2
(RHEL/OEL 5.x)
12.1.0.2 or 11.2.0.4
(RHEL/OEL 7.x)
EBS – Vmware
DB – DBCS
High Complex

The database migration downtime can be reduced further by using replication tools like Golden Gate. But, we have to be careful with the certification matrix of Golden Gate.

There can be many more scenarios, do share your thought and if anything different scenarios you are looking for.