OracleFree checklistPDF, Excel, Word exportOracle E-Business SuiteAll Oracle E-Business Suite tools

Oracle EBS 12.2 Database Upgrade to 19c Checklist

This checklist structures the Oracle E-Business Suite 12.2 (and 12.1.3) database upgrade to Oracle Database 19c around Oracle's interoperability notes, the multitenant requirement and the UTL_FILE_DIR change. It does not replace the note; it helps you plan, rehearse and sign off each phase.

0%

0 of 29 items complete

8 critical items still open - these are the highest-risk gaps.

Download checklist:

1. Prerequisites and planning

2. Architecture decisions

3. Install the 19c Oracle Home

4. Pre-upgrade on the source database

5. Upgrade and convert

6. Apps tier and validation

Always follow the current revision of the interoperability note; it changes as new Release Updates are certified.

Get your 19c run book reviewed

Send your current database version, ETCC output and timings from a rehearsal, and we will review the plan and outage estimate.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

How to use it

Open the interoperability note for your release next to this list: Doc ID 2552181.1 for EBS 12.2 and Doc ID 2580629.1 for 12.1.3. Work the groups in order on a clone first and record elapsed time for each step, because the production outage is the upgrade, the PDB conversion and the AutoConfig runs back to back. Mark items that fail or that you skip on purpose, and export the list as the run book appendix for change approval.

  • Rehearse at least once on a full-size clone
  • Record step timings to size the outage
  • Keep ETCC output before and after

The multitenant requirement

The biggest structural change is that EBS on 19c runs in a multitenant architecture: one container database holding a single EBS pluggable database. If you are coming from 11.2.0.4 or a non-CDB 12.1.0.2, the upgrade includes converting the database into a PDB. That affects service names, listener configuration, backup scripts, Data Guard and every integration that connects by SID. Inventory those connections early. The note's helper scripts, such as txkPostPDBCreationTasks.pl, handle EBS-specific configuration after the PDB is created, so run them exactly as documented rather than doing the conversion with generic multitenant steps alone.

UTL_FILE_DIR and init parameters

Database 19c desupports the UTL_FILE_DIR initialization parameter. EBS code that writes files through UTL_FILE, including concurrent programs and custom PL/SQL, must use database directory objects instead. Doc ID 2525754.1 describes the txkCfgUtlfileDir.pl utility that captures the current values and creates the directory objects. Check custom code for hard-coded paths too. Separately, compare your init.ora against Doc ID 396009.1 and remove parameters marked obsolete or removed for 19c; leaving them causes startup warnings at best and plan changes at worst.

How to check the result

After the upgrade, query v$instance and v$pdbs to confirm the version and that the EBS PDB is open read write, check dba_registry for valid components, and compare invalid object counts with your baseline. On the apps tier, AutoConfig logs must finish without errors on every node. Then run the business smoke tests and compare AWR reports for your heaviest concurrent programs; 19c optimizer changes can shift plans, and the fix may be statistics, a SQL plan baseline or a patch from the note.

Frequently Asked Questions

Which note covers the EBS 12.2 upgrade to 19c?

Interoperability Notes: Oracle E-Business Suite Release 12.2 with Oracle Database 19c, Doc ID 2552181.1. EBS 12.1.3 has its own note, Doc ID 2580629.1. Always use the latest revision, because the certified Release Update levels and required one-off patches are updated over time.

Does EBS on 19c have to use a CDB and PDB?

Yes. Oracle certifies EBS with Database 19c in a multitenant configuration, with the EBS database as a pluggable database in a container database. If your current database is non-CDB, plan the conversion as part of the upgrade and update service names, backups and integrations accordingly.

What happens to UTL_FILE_DIR when upgrading EBS to 19c?

UTL_FILE_DIR is desupported in 19c. EBS file I/O moves to database directory objects, configured with the txkCfgUtlfileDir.pl utility described in Doc ID 2525754.1. Review custom PL/SQL that writes files so it uses the new directory objects instead of literal paths.

Can I upgrade directly from 12c to 19c for EBS?

Yes, the interoperability note covers upgrading from supported earlier releases, including 12.1.0.2 and 11.2.0.4, to 19c. The path still includes installing the 19c home with the certified patches, the pre-upgrade steps, the upgrade itself and conversion to a PDB if the source is non-CDB.

Once your EBS database is on 19c, we can add a read-only, on-prem AI layer over it so planners and finance can ask questions in plain English without new reports.

ArchRay builder
Design the on-prem AI stack for Oracle E-Business Suite: model, GPUs, RAG pipeline, guardrails
See memory, speed and cost as you swap parts, then export the diagram. Free, in your browser.
Open the builder

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

AI on your ERP

Integrations

Software