Oracle EBS 12.2 on-prem is now certified with Oracle 19c – and will become a PDB

Great news – and I’m just putting the pieces together. Oracle EBS 12.2 on-prem is now certified with Oracle 19c.

Photo by Charles Forerunner on Unsplash

Plan your upgrade(s)

You can plan your EBS and database upgrades now. I know from discussions at conferences and workshops, that customers felt locked in on older databases releases. As a result, we waived the Extended Support for the database for those who still are on Oracle 11.2.0.4 and 12.1.0.2 as database for an EBS installation.

Please be aware that the certification as of now includes only Linux and SPARC Solaris platforms. The other OS ports will follow later.

You can find all the announcement details in this Oracle blog post:

• https://blogs.oracle.com/ebstech/oracle-database-193-now-certified-with-ebs-122

EBS will become a PDB in Oracle 19c

And the most interesting news here are:

When upgrading your Oracle E-Business Suite to Oracle Database 19c, the database will be converted to single-tenant, i.e. a CDB with one PDB. No extra Multitenant license is required. But please read the Interoperability note carefully. There are a lot of tasks to do.

• MOS Note 2552181.1 – Interoperability Notes: Oracle E-Business Suite Release 12.2 with Oracle Database 19c

More information

• MOS Note 2552181.1 – Interoperability Notes: Oracle E-Business Suite Release 12.2 with Oracle Database 19c
• MOS Note 2525754.1 – Using UTL_FILE_DIR or Database Directories for PL/SQL File I/O in Oracle E-Business Suite Releases 12.1 and 12.2
• Extended Support Fee Waived for EBS for Oracle Customers with Oracle 12.1 and 11.2
• MOS Note 396009.1 – Database Initialization Parameter Settings for Oracle E-Business Suite Release 12 

Database Migration from non-CDB to PDB

• Overview
• Upgrade, plug in, convert (noncdb_to_pdb.sql) – 11.2.0.4 and higher
• Plugin, upgrade, convert (noncdb_to_pdb.sql) – 12.2.0.1 and higher
• Clone via NON$CDB, upgrade, convert – 12.1.0.2 and higher

Things to know

In addition to these scenarios, I’d like to highlight also the special cases such as:

• Typical Plugin Issues and Workarounds
• The Compatible Pitfall
• The Time Zone Pitfall
• The Component Pitfall
• The Patch Level Pitfall
• Various Pitfalls
• The Fallback Challenge
• The Minimal Downtime Challenge

–Mike