Oracle is the most widely-used relational database in the world. This course will teach you how to evaluate the database for issues that might interfere with the upgrade, and methods to migrate your database in complex environments.
Many companies do not want to move, or cannot move to the cloud because of their complex business requirements, so they must upgrade to the latest database version in house. In this course, Oracle 12.2 Upgrade, you will learn the variety of methods and pitfalls to avoid while planning and performing your Oracle upgrade. First, you will learn the reasons Oracle 12 Release 2 upgrades are different than previous upgrades particularly when working with pluggable databases. Next, you will learn the basic upgrade methods utilizing tools such as the database upgrade assistant and the database parallel upgrade utility. Finally, you will learn the differences between an upgrade and a migration, and come away with tools to meet both challenges. When you're finished with this course, you will have skills and knowledge to upgrade and migrate your database to Oracle 12 release 2 even in the most complex environments.
As a teenager, Tim found a love for teaching, learning, writing, and computers. He believes that everyone should be a lifelong learner. Tim has been teaching for nearly 21 years, either full or part-time. Tim is an Oracle Database Administrator with over 17 years of experience. He works out of Pittsburgh PA and lives in West Virginia with his wife and kids.
Course Overview Hi everyone, my name is Tim Boles and welcome to my course Oracle 12. 2 Upgrade. I'm a senior manager at Hitachi Consulting with close to 20 years of Oracle database management experience. Did you know that Oracle Relational Database is the most popular database management system worldwide? With each version of the database Oracle, introduces new capabilities and some old ones are phased out. This course will help you plan and execute a successful upgrade to Oracle 12 Release Two. You'll be given direction on setting up your own test environment, guided through the pre-upgrade steps, provided direction and hands-on experience to determine which upgrade technique is best suited for your situation, and you'll be led in the post-upgrade tasks. By the end of this course, you'll know several different methods you can apply to your own environment to upgrade your databases to Oracle 12 Release Two. Before beginning the course, you should be familiar with managing any version of an Oracle database. From here you can continue learning about Oracle 12 with my OCP courses like OCP 12C DBA Enhancements, the OCP 12C Using New Security Features, or OCP 12C Performance Enhancements. I hope you'll join me on this journey to learn different paths of upgrading in the Oracle 12. 2 Upgrade Course at Pluralsight.
Preparing the Practice Field Hello and welcome to Pluralsight. My name is Tim Boles, and you're watching Oracle 12. 2 Upgrade. In this course, you will learn how to upgrade previous versions of the Oracle database to Oracle 12 Release 2. In this module, I will guide you in preparing a virtual environment to be used for demonstrations throughout the entire course in the learning path. The modules in this course will teach you the basic methods of upgrading previous Oracle databases. In order of appearance, our non-container databases, container databases, and pluggable databases. Then you'll dive into the more advance techniques of upgrading, like cross-platform migrations, using backup sets, and performing a manual upgrade for those of you who really like to know all the magic that goes along behind the GUI interfaces. The final module will provide some hints, tips, and guidance how to determine the upgrade path you will in your own environments.
Performing Manual Upgrades to Non-CDB Oracle 12.2 So far, you've learned about the core upgrade of a container database and a pluggable database. In this module, you'll learn the details of the steps surrounding the core upgrade progress. How complicated upgrading a database is depends on what is installed on the system and what features are being used. Some examples of things that could increase the time of an upgrade or require an additional steps include using a RAC system, having scheduled jobs, having Oracle Application Express installed, materialized view refreshes, or having custom DDL triggers, just to name a few. In this module, we'll not be able to cover all these, but we'll give you a good baseline example to help you design your own process. When you're upgrading a container database, you can follow this generic outline of steps. We've gone through many of the basic steps in previous sessions. In general, you'll perform some prep work on the system. Then, just before you upgrade, you'll do some final prep steps, such as purging the DBA recycle bin and backing up the database. All these things can be done no matter if you're manually upgrading the database or using the Database Upgrade Assistant. Finally, there'll be post checks and a baseline comparison of the new environment with the source environment. As a best practice, you should then back up the new database. We'll go over most of these steps in the module.
Determining Your Upgrade Path What we have seen so far are just examples of easy upgrades. Upgrades can get a lot more complicated depending on their architecture being used and the options being used. This session is designed to give you a starting point for choosing an upgrade path when things are a little bit more complicated. Often, upgrading and migrating are used interchangeably in relationship to moving to a new version of Oracle. However, they are different. An upgrade refers to modifying the data dictionary to a newer version. It may include the modification or creation of Oracle-provided packages and procedures and it may include some user maintenance and changes in security. It has nothing to do with the user data unless there are custom scripts that are executed during the process. And migration generally refers to changes in the architecture. Perhaps movement to a new server or to a VM, or adding partitioning to a schema. It could include change in the character set or the operating system. You might decide to utilize options such as encryption or compression. Migration could involve moving or modifying the user or application data. So, size would matter in that case. An upgrade and a migration may occur at the same time or they may be performed independently. Unless stated specifically, from here on out we'll be referring to both upgrading and migration even if we just use a single term like upgrade. This module is just the starting point in finding the upgrade path. When you've finished with this module, you'll understand the upgrade life cycle and have a greater knowledge of basic upgrade techniques. You'll have a good base knowledge of advanced techniques that can be used to reduce downtime to near zero. In the end, you'll have a technique to rate your upgrade options and you'll know where to look to find additional information.