# Oracle EBS 12.2 Database Upgrade to 19c Checklist

> Source: https://netray.co/tools/oracle-ebs-database-19c-upgrade-checklist
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A step checklist for upgrading the Oracle E-Business Suite 12.2 database to 19c, organised around the interoperability note and the multitenant requirement.

## Category

oracle

## Erp

Oracle E-Business Suite

## Audience

- EBS DBA
- Apps DBA
- Infrastructure architect

## Tool

**Kind:** checklist

**Groups:**

#### 1. Prerequisites and planning

**Items:**

**Text:** Read the interoperability note for your release: EBS 12.2 with Database 19c (Doc ID 2552181.1) or EBS 12.1.3 with 19c (Doc ID 2580629.1), and follow its version of every step

**Critical:** true

**Text:** Apply the minimum AD and TXK Delta levels and EBS patches the note lists, on the apps tier, before the database upgrade

**Critical:** true

Run ETCC (checkDBpatch.sh on the database tier, checkMTpatch.sh on the middle tier, Doc ID 1594274.1) and record missing fixes

Confirm the target 19c Release Update is certified for EBS and get the matching one-off patch list

Full tested backup of the source database and application tier, and a timed rehearsal on a clone

#### 2. Architecture decisions

**Items:**

**Text:** EBS on 19c runs in a multitenant container database: one CDB holding the EBS PDB. Plan the non-CDB to PDB conversion if the source is non-CDB

**Critical:** true

Decide CDB and PDB names; the PDB name normally keeps the old database name so the EBS service name and TNS entries stay familiar

Check storage for the new Oracle Home, upgrade logs and any datafile copies if you do not convert in place

Plan RAC, Data Guard and backup tooling changes for a CDB (RMAN at CDB level, standby rebuild or upgrade path)

#### 3. Install the 19c Oracle Home

**Items:**

**Text:** Install 19c base (19.3) software and the Examples media into a new Oracle Home, as the note specifies

**Critical:** true

Apply the certified Release Update, then the EBS-required one-off patches listed in the note; rerun ETCC checkDBpatch.sh until clean

Create the CDB using the steps in the note (do not reuse a generic CDB without the EBS init parameters)

Copy the appsutil directory to the new Oracle Home by generating appsutil.zip on the apps tier with admkappsutil.pl

#### 4. Pre-upgrade on the source database

**Items:**

**Text:** UTL_FILE_DIR is desupported in 19c: move EBS file I/O to database directory objects using txkCfgUtlfileDir.pl as described in Doc ID 2525754.1

**Critical:** true

Remove obsolete and desupported init parameters and set the 19c values from Database Initialization Parameters for Oracle E-Business Suite Release 12 (Doc ID 396009.1)

Run the 19c pre-upgrade checks against the source and fix every error-level finding

Gather dictionary and fixed object statistics; purge recycle bin; record invalid object counts as a baseline

Take an AWR baseline for key batch jobs and screens to compare after the upgrade

#### 5. Upgrade and convert

**Items:**

**Text:** Upgrade the database with DBUA or the manual method, following the note's sequence

**Critical:** true

**Text:** Convert the upgraded non-CDB into a PDB in the new CDB, then run txkPostPDBCreationTasks.pl as instructed in the note

**Critical:** true

Run adgrants.sql from the new Oracle Home, then recompile invalid objects and compare with the baseline

Run AutoConfig on the database tier from the new Oracle Home

Confirm the listener serves the EBS PDB service and update tnsnames entries used by integrations and tools

#### 6. Apps tier and validation

**Items:**

**Text:** Update the apps tier context to the new database connection details and run AutoConfig on every application tier node

**Critical:** true

On 12.2, run adop phase=fs_clone if the note or your patching state requires the patch file system to be synchronised

Start services; check login, forms, OA Framework pages, workflow mailer and concurrent managers

Run sample transactions in each critical module (order entry, receiving, WIP completion, AP invoice, GL journal)

Compare AWR for key jobs against the pre-upgrade baseline and fix plan regressions before go-live

Reconfigure backups, monitoring and any external tools that connect directly to the database name

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

## Content

**Intro:** 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.

**Sections:**

#### How to use it

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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

**Body:** 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.

**Cta:** 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.

**Faq:**

#### Which note covers the EBS 12.2 upgrade to 19c?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

upgrade oracle ebs database 12c to 19c, oracle ebs 12.2 database upgrade to 19c, oracle ebs 12.2 interoperability with 19c, oracle ebs database upgrade from 12c to 19c, doc id 2552181.1, ebs 19c pdb conversion, ebs utl_file_dir 19c

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json