With AutoUpgrade it is easy to gather fixed objects statistics a number of days after the actual database upgrade. Just like it is recommended.
Often, re-gathering fixed objects statistics are one of those post-upgrade tasks that is forgotten – or completed in a wrong way. Here’s a quick way to avoid that.
If your 184.108.40.206 VM DB System is sensitive to downtime, you can use incremental backups to your advantage when you need to upgrade and convert to PDB.
Learn how to upgrade an 220.127.116.11 VM DB System to 19c. It also involves conversion from non-CDB architecture to a pluggable database. And it works for Standard Edition as well.
How fast can you transfer data between VM DB Systems? In some situations when upgrading on VM DB Systems you must move data between systems.
Using Zero Downtime Migration (ZDM) you can migrate from a regular system to Exadata DB System (ExaCS) and you can convert from single instance to RAC at the same time. And it is just as easy as any other ZDM migration.
The scripts glogin.sql and login.sql might kill your upgrade. Learn why and how to avoid.
It is a little mix and match of all my notes that didn’t make it into the previous blog posts, but are still too good to go.
Let the fun begin. It’s time to migrate a database using ZDM – with zero downtime, of course.
The third post in the series shows you how to install and configure the ZDM service host
Something went wrong. Please refresh the page and/or try again.