# Oracle Database 12c to 19c Upgrade Checklist for ERP Databases > Source: https://netray.co/tools/oracle-database-12c-to-19c-erp-upgrade-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A 41 item checklist for upgrading a JD Edwards, E-Business Suite or PeopleSoft database from 12c to 19c, with the critical steps marked. ## Category oracle ## Erp Oracle Database ## Audience - Oracle DBA - ERP administrator - ERP project manager ## Tool **Kind:** checklist **Groups:** #### Certification **Items:** **Text:** Confirm the ERP application release is certified on Database 19c in the My Oracle Support Certifications tab **Critical:** true JD Edwards: confirm the Tools release supports 19c and check the Minimum Technical Requirements for the database and client **Text:** E-Business Suite: follow the EBS interoperability note for Database 19c, including the required multitenant (CDB with PDB) architecture **Critical:** true PeopleSoft: confirm the PeopleTools release and patch level certified with 19c Upgrade Oracle clients and drivers on application, batch and reporting servers to a 19c certified version Check third party tools (backup agents, monitoring, ETL, reporting) for 19c support #### Pre-upgrade **Items:** **Text:** Install 19c into a new Oracle home and apply the latest Release Update and ERP required one-off patches **Critical:** true **Text:** Run AutoUpgrade in analyze mode and review the preupgrade report **Critical:** true Gather dictionary statistics with DBMS_STATS.GATHER_DICTIONARY_STATS shortly before the upgrade Purge the recycle bin with PURGE DBA_RECYCLEBIN Record a baseline of invalid objects by owner and object type Check DBA_REGISTRY: all components VALID before you start Record the current time zone file version from V$TIMEZONE_FILE and plan the time zone upgrade Plan the COMPATIBLE parameter: keep the 12c value during and after the upgrade until stable Remove or replace deprecated and desupported init parameters listed in the preupgrade report Capture AWR baselines and a SQL Tuning Set of key ERP SQL from 12c for later comparison #### Backup and fallback **Items:** **Text:** Take a full RMAN backup and test that it restores **Critical:** true Create a guaranteed restore point (AutoUpgrade restoration=yes on Enterprise Edition) Confirm the fast recovery area has space for flashback logs during the upgrade Document the fallback decision point and who makes the call Keep the 12c home intact until the upgrade is signed off #### Upgrade **Items:** **Text:** Rehearse the full upgrade on a clone of production and record timings **Critical:** true Decide non-CDB versus CDB: 19c allows up to three user PDBs without the Multitenant option Stop ERP application servers, batch schedulers and integrations before the window Run AutoUpgrade in deploy mode, or the manual dbupgrade method if the ERP note requires it Monitor the job with lsj and status, and keep the logs from each run Upgrade the time zone file if planned (timezone_upg=yes) Update oratab, listener, environment scripts and ERP connection definitions to the new home #### Post-upgrade **Items:** **Text:** Run utlrp.sql and compare invalid objects with the baseline **Critical:** true Confirm datapatch ran: DBA_REGISTRY_SQLPATCH shows the target RU with SUCCESS Confirm DBA_REGISTRY components are VALID at version 19 Gather fixed object statistics after a representative workload has run Use SQL Plan Management baselines from the 12c SQL Tuning Set to protect key ERP SQL from plan regressions Keep OPTIMIZER_FEATURES_ENABLE at the 19c default and use it only as a short term fallback for regressions **Text:** Raise COMPATIBLE to 19.0.0 only after sign off, knowing it removes the flashback option **Critical:** true Drop the guaranteed restore point once you are committed #### ERP validation **Items:** **Text:** Run key batch jobs and compare run times with the 12c baseline **Critical:** true Test every interface and integration end to end, including EDI and reporting extracts Run user acceptance scripts for order to cash, procure to pay and period close Verify RMAN backups and archivelog deletion jobs run against the new home Review the alert log and AWR for the first week after go live **Scoring Note:** Critical items are the ones that, if skipped, either leave no way back or cause an unsupported ERP configuration. Treat them as go or no-go gates. ## Content **Intro:** This checklist covers an Oracle Database 12c to 19c upgrade for an ERP database, from vendor certification through AutoUpgrade to post-upgrade validation of batch and integrations. It is written for JD Edwards, E-Business Suite and PeopleSoft databases but applies to any ERP running on Oracle. **Sections:** #### How to use it **Body:** Work through the groups in order on your rehearsal clone first, then again for production. Tick each item as it is done and export the list as evidence for change control. The critical items are gates: do not start the production window until certification, the tested backup and the rehearsal are complete. Record timings from the rehearsal against each item in the Upgrade group, so the production window is based on measured numbers, and attach the AutoUpgrade logs to the change record. **Bullets:** - Rehearse on a full size clone, not a subset. - Keep the 12c home and backup until sign off. - Agree the fallback decision point in advance. #### What changes from 12c to 19c **Body:** 19c is the long term release of the 12.2 family, with the longest support window, so most ERP vendors certify it as their main database target. Practical differences for an ERP DBA include automatic indexing, real time statistics and SQL Quarantine (all three limited to Exadata in 19c), and up to three user PDBs without the Multitenant option. The non-CDB architecture still works in 19c but is desupported from 21c. Optimizer changes are the main risk: each release can produce different plans for the same ERP SQL, which is why the checklist captures SQL Tuning Sets and uses SQL Plan Management. #### ERP specific notes **Body:** E-Business Suite on 19c requires the multitenant architecture, a CDB with the EBS database as a PDB, and has its own interoperability note with required steps, patches and scripts; follow it instead of a generic upgrade guide. JD Edwards certification depends on the Tools release, and the database client on the Enterprise Server and HTML servers must be upgraded too. PeopleSoft certification depends on PeopleTools. Check all of these in the My Oracle Support Certifications tab before you schedule anything. #### Common mistakes **Body:** Raising COMPATIBLE in the same window as the upgrade removes the easiest fallback. Skipping dictionary statistics makes the upgrade slower. Forgetting client upgrades on batch and reporting servers causes connection errors that look like database problems. Comparing batch run times without a 12c baseline turns every slow job into an argument. Finally, leaving the guaranteed restore point in place for weeks fills the fast recovery area and can stop the database. **Cta:** If you want your team to ask the upgraded database, its AWR history and the ERP batch logs questions in plain English on your own servers, we can set that up. **Faq:** #### What are the steps to upgrade Oracle 12c to 19c? **Answer:** Confirm ERP certification, install 19c in a new home with the latest RU, run AutoUpgrade analyze, fix the findings, take and test a full backup, create a restore point, rehearse on a clone, run the upgrade with AutoUpgrade deploy, then run utlrp, confirm datapatch and registry status, gather statistics and validate ERP batch and integrations. #### What is the difference between Oracle 12c and 19c? **Answer:** 19c is the terminal, long term support release of the 12.2 family. It adds features such as three free user PDBs per CDB, plus automatic indexing, real time statistics and SQL Quarantine (those three on Exadata only in 19c), and carries a longer support window than 12.2. For ERP it is the database release most vendors certify, which is the main reason to upgrade. #### Can I upgrade directly from 12.1 to 19c? **Answer:** Yes. Direct upgrade to 19c is supported from 11.2.0.4, 12.1.0.2, 12.2.0.1 and 18c. Older releases must first be upgraded to one of those. The preupgrade report from AutoUpgrade analyze confirms whether your source is eligible. #### How do I stop SQL plan regressions after the upgrade? **Answer:** Capture key ERP SQL into a SQL Tuning Set on 12c, load those plans as SQL plan baselines in 19c with DBMS_SPM, and compare performance with SQL Performance Analyzer if licensed. Use OPTIMIZER_FEATURES_ENABLE set to the old version only as a temporary fallback while you fix specific statements. ## Search terms oracle 12c to 19c upgrade steps, oracle database upgrade 12c to 19c steps, database upgrade best practice or guidance, upgrading oracle db steps by step guide, difference between oracle 12c and 19c, oracle 19c upgrade checklist, erp database upgrade 19c --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json