3 Upgrading Databases with Oracle Data Guard Standbys

When you upgrade a database to a new release, you upgrade the primary, and then replicate transactions transactions to the standby using the archive logs from the primary.

This scenario assumes you are using Oracle Data Guard broker.

• Preparing for Upgrades of Databases Using Oracle Data Guard
  In this scenario, you perform your upgrade using Oracle Data Guard with Data Guard broker, and move the Data Guard broker configuration files before starting your upgrade.
• Manual Non-CDB to PDB Conversion and Upgrade with Data Guard Standby
  Upgrades with Oracle Data Guard where you want to uprade a non-CDB to a PDB, and reuse the non-CDB stadnby datafiles require a special procedure.
• Before You Patch or Upgrade the Oracle Database Software
  Before you patch or upgrade your Oracle Database software, review the prerequisites for different use case scenarios.
• Recovering After the NOLOGGING Clause Is Specified
  Some SQL statements allow you to specify a NOLOGGING clause so that the operation is not logged in the online redo log file.
• Enable an Appropriate Logging Mode
  As part of preparing the primary database for standby database creation, you must enable a logging mode appropriate to the way you plan to use the Oracle Data Guard configuration.
• Upgrading Oracle Database with a Physical Standby Database in Place
  These steps show how to upgrade to Oracle Database when a physical standby database is present in the configuration.