X

News, tips and technical guidance to help you run Oracle E-Business Suite on Oracle Cloud.

Upgrading Your EBS Database from 11g to 19c on VM DB Systems

Terri Noyes
Product Management Director

We are pleased to be able to share newly available Oracle Database 19c migration and upgrade procedures for Oracle E-Business Suite (EBS) customers running on Oracle Cloud Infrastructure (OCI) with Oracle Database 11g (11.2.0.4) on a 1-Node or 2-Node VM DB System.

Procedures for the Oracle Database 12.1.0.2 upgrade to 19c for EBS on VM DB Systems were announced previously.

Migration and Upgrade Process

The key steps in the EBS database migration and upgrade from 11.2.0.4 to 19c are as follows:

  1. Create a new 19c Oracle VM DB System with an Oracle 19c Container Database.
  2. Back up the source database using RMAN and the Oracle Database Cloud Backup Module.
  3. Restore the database from Oracle Cloud Storage to the target 19c system.
  4. Upgrade the restored Oracle E-Business Suite non-CDB database to Oracle Database 19c non-CDB.
  5. Convert the database to a PDB by plugging-in the upgraded Oracle Database 19c non-CDB database to the CDB.
  6. Run AutoConfig on all the database tier nodes.
  7. Run AutoConfig on all the application tier nodes.

Migration and Upgrade Documents

The procedure you will use for the database migration and upgrade is specific to the EBS release version you are starting from. Choose whichever of these documents applies to you:

Using EBS Cloud Manager After Migrating and Upgrading

If you use EBS Cloud Manager to manage your environments, as part of planning your database upgrade to 19c, you should refer to Section 4.5.6, "Upgrading to Oracle Database 19c" in Getting Started with Oracle E-Business Suite on Oracle Cloud Infrastructure (MOS Note 2517025.1) for important information about the use of Cloud Manager after the upgrade.

References

Related Articles

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.