Restarting the Upgrade from a Specific Phase that Failed Using -p
Use this option to complete an upgrade after fixing errors.
You can run the Parallel Upgrade Utility (catctl.pl
, or the shell scripts dbupgrade
or dbupgrade.cmd
) with the -p
option to rerun an upgrade and skip upgrade phases that already have run successfully. You can also rerun the upgrade on one phase to test the fix for failed phases.
To determine the phase number to restart, examine the upgrade log to identify where the first error occurred, and in what phase. You can then fix the cause of the error, and test the fix or rerun the upgrade to completion.
- Reviewing CDB Log Files for Failed Phases
Identify your log file location, and review the CDB and PDB log files. - Reviewing Non-CDB Log Files for Failed Phases
Identify your log file location, and review the Non-CDB log files. - Procedure for Finding and Restarting Multitenant Upgrades from a Failed Phase
To restart a multitenant upgrade from a failed phase, first identify which PDB created the error and then search its appropriate log file for the error.
Parent topic: Upgrading Oracle Database
Reviewing CDB Log Files for Failed Phases
Identify your log file location, and review the CDB and PDB log files.
The location of the Automatic Diagnostic Repository (ADR) and the diagnostic log files created by the upgrade scripts can vary, depending on your environment variables and parameter settings.
You can set log file paths when you run the Parallel Upgrade Utility (catctl
) by setting the -l
option to define a log file path.
Log files for CDB$ROOT (CDBs) can span from catupgrd0...catupgrd7.log
. Log files for pluggable databases (PDBs) are identified by the PDB container name (dbname
), and span from catupgrdpdbname0...catupgrdpdbname7.log
.
Reviewing Non-CDB Log Files for Failed Phases
Identify your log file location, and review the Non-CDB log files.
The location of the Automatic Diagnostic Repository (ADR) and the diagnostic log files created by the upgrade scripts can vary, depending on your environment variables and parameter settings.
You can set log file paths when you run the Parallel Upgrade Utility (catctl
) by setting the -l option to define a log file path.
Note:
Starting with Oracle Database 12c, release 1 (12.1), non-CDB architecture is deprecated. It can be desupported in a future release.
Log files can span from catupgrd0...catupgrd7.log
.
Procedure for Finding and Restarting Multitenant Upgrades from a Failed Phase
To restart a multitenant upgrade from a failed phase, first identify which PDB created the error and then search its appropriate log file for the error.