Session ID: 1105
Migrating to a newer Oracle Database Version doesn't have to be confined to a single outage period. Several interim steps can be done ahead to certain compatible components saving valuable time. In a general sense Oracle is backwards compatible for making that transition from an earlier version to a later one. This session will cover components that are backwards compatible along with tips and techniques associated with patching, upgrades or migrations. An Oracle DBA needs to apply security patches on a quarterly basis which calls for organizing your methods, improving naming standards while reducing errors and off-hours work. This session also covers the differences in patch types as well as migration methods for DataGuard and standby databases - both logical and physical. Specifics for upgrading or migrating to Oracle Database 12.2.x will be covered including the upgrade paths and the various upgrade types (CDB vs PDB, Manual vs DBUA, Transportable Tablespaces and Standbys). There are new features for reducing downtime in the Oracle Database 12.2 Upgrade (off-line schema tablespaces) that will be covered with a case study of how they performed in our latest production upgrade. This session will cover all of the steps that are part of a manual upgrade to make sure the audience understands what is actually occurring even if they only use the Database Upgrade Assistant. Tips for gathering/saving statistics (both system and schema statistics) before and after upgrades will be provided.
Objective 1: Narrow the amount/time of outage needed for Oracle Database Upgrades or Patching
Objective 2: Learn what Oracle Database components are backwards compatible.
Objective 3: Patching, upgrades and migrations – Tips and Techniques.