Developer ToolsFree generatorPDF, Excel, Word exportOracle Database

Oracle Database 19c AutoUpgrade Config File Generator

This generator writes an AutoUpgrade configuration file for upgrading an Oracle 12c database to 19c, with the guaranteed restore point, time zone upgrade and optional non-CDB to PDB conversion settings, and the commands to run analyze, fixups and deploy. Fill in your homes and SID and copy the result.

Fill in

Log directory

Source Oracle home

Target Oracle home (19c, latest RU applied)

Database SID

Start time

NOW, a delay such as +1h30m, or a date in dd/mm/yyyy hh:mm:ss format.

Create guaranteed restore point

Upgrade time zone file

Target CDB for non-CDB to PDB conversion (optional)

Config file name

Generated code

Download:

Config file (up.cfg)

# AutoUpgrade configuration for ERPPRD
global.autoupg_log_dir=/u01/app/oracle/autoupgrade

upg1.source_home=/u01/app/oracle/product/12.2.0/dbhome_1
upg1.target_home=/u01/app/oracle/product/19.0.0/dbhome_1
upg1.sid=ERPPRD
upg1.start_time=NOW
upg1.log_dir=/u01/app/oracle/autoupgrade
upg1.upgrade_node=localhost
upg1.restoration=yes
upg1.timezone_upg=yes

# Non-CDB to PDB conversion: remove the # to plug ERPPRD into an existing 19c CDB
#upg1.target_cdb=CDB1

Run sequence

# Use the Java in the 19c target home and the latest autoupgrade.jar from My Oracle Support
export ORACLE_HOME=/u01/app/oracle/product/19.0.0/dbhome_1
$ORACLE_HOME/jdk/bin/java -jar autoupgrade.jar -version

# 1. Analyze only: no changes to the database
$ORACLE_HOME/jdk/bin/java -jar autoupgrade.jar -config up.cfg -mode analyze

# 2. Run pre-upgrade fixups (still no upgrade)
$ORACLE_HOME/jdk/bin/java -jar autoupgrade.jar -config up.cfg -mode fixups

# 3. Full run: analyze, fixups, upgrade, post-upgrade fixups
$ORACLE_HOME/jdk/bin/java -jar autoupgrade.jar -config up.cfg -mode deploy

Console commands while a job runs

upg> lsj                 # list jobs and their stage
upg> status -job 100     # detail for one job (first job number is usually 100)
upg> resume -job 100     # resume after fixing a stopped job
upg> abort -job 100      # stop a job
upg> exit

Where the logs are

/u01/app/oracle/autoupgrade/cfgtoollogs/upgrade/auto/       # global AutoUpgrade logs and status
/u01/app/oracle/autoupgrade/ERPPRD/<jobid>/prechecks/      # ERPPRD_preupgrade.html and .log from analyze
/u01/app/oracle/autoupgrade/ERPPRD/<jobid>/prefixups/      # pre-upgrade fixup results
/u01/app/oracle/autoupgrade/ERPPRD/<jobid>/dbupgrade/      # catupgrd logs from the upgrade itself
/u01/app/oracle/autoupgrade/ERPPRD/<jobid>/postfixups/     # post-upgrade fixup results
/u01/app/oracle/autoupgrade/ERPPRD/temp/                   # generated scripts and temporary files

Always download the latest autoupgrade.jar from My Oracle Support; the copy in a 19c home is often old. Check parameter names against the AutoUpgrade documentation for your jar version (java -jar autoupgrade.jar -create_sample_file config writes a current sample). restoration=yes needs archivelog mode, a fast recovery area with space and Enterprise Edition (Flashback Database is not available on SE2). Non-CDB to PDB conversion is one way: the guaranteed restore point cannot roll back the plug in. For Oracle E-Business Suite, follow the EBS interoperability note for Database 19c, which defines the supported upgrade method and extra EBS steps; for JD Edwards and PeopleSoft, confirm 19c certification for your tools release first.

Get your preupgrade report reviewed

Send us the preupgrade HTML report from AutoUpgrade analyze and we will mark which findings block your ERP upgrade and which are informational.

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

Was this tool useful?

How to use it

Install the 19c software into a new home and apply the latest Release Update before upgrading, so you only take one outage. Enter the log directory, the source 12c home, the target 19c home, the SID and a start time. Keep restoration=yes on Enterprise Edition so AutoUpgrade creates a guaranteed restore point you can flash back to. Leave timezone_upg=yes unless an application vendor requires a fixed time zone file version. Only uncomment target_cdb if you are converting a non-CDB into a PDB of an existing 19c CDB. Save the config as up.cfg next to autoupgrade.jar and run analyze first.

analyze: read-only checks, writes the preupgrade HTML report.
fixups: runs the pre-upgrade fixups the analysis found.
deploy: the full upgrade, including post-upgrade fixups.
upgrade mode exists for when the database is already started in the new home.

Supported paths and the non-CDB decision

Direct upgrade to 19c is supported from 11.2.0.4, 12.1.0.2, 12.2.0.1 and 18c. 19c still supports the non-CDB architecture, which was deprecated in 12.1.0.2 and is desupported from 21c, so many teams stay non-CDB for the 19c upgrade and convert later. From 19c you can run up to three user PDBs per CDB without the Multitenant option, so a single ERP PDB needs no extra licence. Converting with target_cdb moves the database into a PDB in one AutoUpgrade run, but it cannot be undone with the restore point; take an RMAN backup first.

AutoUpgrade and DBUA

Oracle recommends AutoUpgrade as the preferred upgrade method for 19c. The Database Upgrade Assistant (DBUA) is still documented in the 19c Upgrade Guide, but Oracle lists DBUA and manual upgrades as deprecated in later releases. AutoUpgrade can upgrade many databases from one config file, resume after a failure, run unattended at a start time and produce consistent logs, which is what most ERP teams need for rehearsals. Manual upgrade with dbupgrade remains possible when an ERP note requires it.

Checking the result

After deploy, lsj should show the job as FINISHED. Then check SELECT comp_id, version, status FROM dba_registry for VALID components at 19, SELECT * FROM v$timezone_file for the new time zone version, and DBA_REGISTRY_SQLPATCH for the RU of the target home. Count invalid objects against the baseline you took before the upgrade. Keep COMPATIBLE at the old value until the ERP has run a full business cycle, because raising it removes the option to flash back to the restore point. Drop the guaranteed restore point once you are committed, or the fast recovery area fills.

Frequently Asked Questions

Where is the Oracle database upgrade log location with AutoUpgrade?

Under the log directory in the config. Global logs are in <autoupg_log_dir>/cfgtoollogs/upgrade/auto. Each database job has <log_dir>/<sid>/<jobid>/ with prechecks, prefixups, dbupgrade (the catupgrd logs) and postfixups subfolders. The prechecks folder holds the <sid>_preupgrade.html report from analyze.

What are the steps to upgrade Oracle 12c to 19c with AutoUpgrade?

Install 19c in a new home and apply the latest RU, download the latest autoupgrade.jar, write the config file, run -mode analyze and review the preupgrade report, fix the issues it reports, take a backup, then run -mode deploy in the outage window and validate the registry, time zone, patch level and application.

Is DBUA still supported for 19c?

DBUA is documented and usable for 19c upgrades, but Oracle recommends AutoUpgrade and has deprecated DBUA and manual upgrade in later releases. For new upgrade projects, and especially for repeatable rehearsals across test and production, AutoUpgrade is the better fit.

Can I roll back an AutoUpgrade upgrade?

With restoration=yes on Enterprise Edition, AutoUpgrade creates a guaranteed restore point and you can restore to it while COMPATIBLE is still at the old value and no non-CDB to PDB conversion happened. On SE2, or after a conversion, rollback means an RMAN restore of the pre-upgrade backup.

If you want your DBAs to ask upgrade logs and preupgrade reports questions in plain English across all your databases on your own servers, we can set that up.

Talk to an Expert Explore More Free Tools