Hello Friend's,
In this post we will see the new
features of Autoupgrade 21c
So Let’s Get Started.
What is AutoUpgrade :
Oracle has given us some help with at least the
upgrade process itself us the AutoUpgrade Utility. The AutoUpgrade can
handle the upgrade of multiple databases in an environment within a single
execution. This greatly simplifies the upgrade process in environments where
multiple databases exist and need to be upgraded.
Download Autoupgrade : 20210721
Supported Version :
- Oracle Database 21c (21.3 and newer)
- Oracle Database 19c (19.3 and newer)
- Oracle Database 18c (18.5 and newer)
- Oracle Database 12c Release 2 (12.2 + DBJAN2019RU and newer)
Ø Non-CDB to PDB
Upgrades
o AutoUpgrade can
upgrade and convert a non-CDB to a PDB in a new CDB in a single operation, or
upgrade and then convert a Non-CDB database to a PDB in a pre-existing CDB
o Support for RAC and
SI databases
Ø Unplug-plug upgrade
o AutoUpgrade can
perform an unplug of a pluggable database (PDB) from an earlier release source
container database (CDB), plug it into a later release target CDB, and then
complete all the steps required to upgrade the PDB to the target CDB release
Ø Supports RAC upgrades
(Only for Linux or Unix-based systems)
o Configuration of the
RAC management system in the source and target home is automated
o Supports native file
systems, ASM and ACFS
o Oracle Restart
o Pluggable databases
are supported in a RAC environment
Ø Ability to pass
catctl_options (via config file)
o This enables the DBA
to control the level of parallelism for a specific upgrade.
Ø Restore capability
o AutoUpgrade restore
job option allows the DBA to restore database back to source home if upgrade
failed or succeeded
Ø Clear the recovery
for a specific job by adding clear_recovery_data on the command line and use
jobs parameter to specific exactly which jobs recovery data must be cleared.
Ø Upgrades on Data
Guard environments
o AutoUpgrade can
detect Oracle Data Guard configurations, and defer shipping logs to standby
databases configured for the primary database. It will also detect and defer
shipping logs to standby database if the deployment is configured manually.
Upon a successfully upgrade of the primary database, upgrades to the standby
database must be performed and monitored by the DBA.
Ø AutoUpgrade
performance improvements
o utlrp compilations
moved out of upgrade into a post fixup
o Improved resume
operations: AutoUpgrade keeps track and skips over PDBs databases that have
been upgraded successfully
o Replay support was
added for upgrades 21 or higher
Ø AutoUpgrade supports
upgrade on CDBs with proxy pdbs
Ø AutoUpgrade supports
upgrade on CDB’s with application containers
Ø Added additional JSON
status information
Ø Integrated classic
pre-upgrade functionality
o The -preupgrade
clause of AutoUpgrade replaces the functions previously performed by the manual
Pre-Upgrade Information Tool (preupgrade.jar) in previous releases The -mode
clause takes one of three values:
§ analyze: Check your
system for readiness to upgrade
§ fixups: Perform
fixups as needed on your source Oracle Database release in preparation for
upgrade
§ postfixups: Perform
fixups on your target Oracle Database release after upgrade is completed.
§ Reports are identical
to what the preupgrade.jar originally produced.
Ø Starting Oracle
Release 21c, Enterprise Manager, DBUA and ORAchk use AutoUpgrade to perform database
upgrade readiness.
Ø Starting Oracle
Release 21c, FPP performs database upgrades using AutoUpgrade
Ø Enhanced management
of databases using Transparent Data Encryption (TDE)
ConversionConversion EmoticonEmoticon