If you experience problems with a new release of Oracle Database after go-live – downgrade might be the answer.
Data Guard and downgrade works fine together if you follow the right procedure. Here’s how to do it.
You should always have a fallback plan. If you need to upgrade the time zone file, can you rely on Flashback Database?
If you need to fallback a failed upgrade, you can use Flashback Database. You can even do it without compromising your Data Guard if you follow the procedure.
You can upgrade your Oracle Database to a new release and keep the Data Guard setup intact. There is no need to rebuild the standby database after the upgrade.
When Data Pump creates constraints during import, they will be created in the same way as they were exported. Validated constraints must be validated again which can take quite some time.
Working with a customer learned us about the importance of gathering statistics as part of a migration.
No, you don’t. But it might be a good idea.
In a CDB the encryption keys goes into a united keystore. You can now isolate the PDBs even more by using a separate keystore for each PDB.
Avoid typing TDE keystore password at all! Secure External Password Store and AutoUpgrade in combination enables complete automation of your Oracle Database upgrade and PDB conversion.
AutoUpgrade can automate the entire upgrade and PDB conversion process. With just one command.
Latest version of AutoUpgrade now enables you to upgrade encrypted PDBs.
Upgrading an encrypted database is easy. You just need an auto-login keystore.
Introduction blog post on how to use AutoUpgrade on encrypted databases.
Get the know the details of Full Transportable Export/Import. What is included, and what is not included.
The easiest way to migrate with XTTS is to use version 4 of the Perl script and Full Transportable Export Import. Can you meet the requirements?
A collection of nuggets that I gathered while writing the blog post series on XTTS.
To make your migration with transportable tablespace faster, there are a few knobs you can turn.
ASM aliases are very useful during the migration. But it is highly recommended to get rid of the aliases immediately after the migration.
You can perform multiple tests of migrations using transportable tablespaces. If you keep the tablespaces in read-only mode, you can avoid restoring the data files every time.
You should test your migration procedure. You can do that without interrupting your primary database by using a temporarily activated standby database.
Ensure that your target database is protected by Data Guard as soon as the migration completes.
Bigfile tablespaces are often used in very large databases. Do they have an impact on your migration with transportable tablespaces and incremental backups?
Offload the backups from the primary database when doing cross platform migrations with transportable tablespaces and incremental backups.
When migrating a database to a host over a slow network, it might pay off to compress the backup files.
To use transportable tablespaces you must have a set of self-contained tablespaces. What does self-contained mean and what happens when you try to export anyway?
Upgrade your Oracle Database on ExaCS with very little downtime using DBMS_ROLLING
Get started with AutoUpgrade and learn how to use our Hands-On Lab to sharpen your skills.
We are planning more webinars filled with great tech content. Sign up before your colleague.
Logical offline approach requires downtime. Here is a few tricks to make the downtime as short as possible.
Your encrypted Oracle Database can now be upgraded and converted to a PDB using AutoUpgrade
Oracle Database 21c is now available on more platforms. Here’s my take on it.
If your database is sensitive to downtime, you can use the fast deploy mode to run some tasks while the database is still online.
GoldenGate does not replicate changes to sequences, which is why you must handle them as part of your migration.
Logical Migration does not transfer your optimizer statistics. It is crucial that you get statistics into your target database before starting production
Be sure to test your OCI database before going live. With Logical Online migration you have several options with Flashback Database being the preferred option.
Like huge container ships need a pilot, your huge database might also need a helping hand to navigate successfully to OCI using physical online migration in ZDM.
Migrating very large databases using ZDM and the logical online method might require special considerations. This post discusses the crucial aspects of migrating with Data Pump and Oracle GoldenGate.
One of the really cool features of ZDM is that you can use a standby database for testing in OCI – before you decide to do the switchover.
It is also easy to migrate to ExaCS. But there are a few other things to be aware of. This post will give you a head start on your ExaCS migration.
Learn how to migrate a database to OCI using Zero Downtime Migration. This procedure uses the physical online method to migrate using Data Guard.
Get to know the pros and cons of using the physical online method in ZDM. This method uses Data Guard to migrate your database to OCI.
These extra tasks will help you avoid any performance issues after the migration. If a problem arise anyway, you are better off if you followed these recommendations.
Step-by-step instructions on how to migrate your database into OCI using Data Pump and GoldenGate.
Step-by-step instructions on how to migrate your data into an Autonomous Database using ZDM and the “logical offline” method.
When migrating with Oracle GoldenGate you can easily use the console to monitor the replication and resolve errors
You can migrate into OCI with very little downtime using the Logical Online method. It uses a combination of Data Pump and Oracle GoldenGate.
To migrate an Oracle Database with ZDM using the Logical Online method, you need an Oracle GoldenGate Hub. It is easily deployed from the OCI marketplace.
To save resources on your primary database when doing Data Pump exports and to avoid ORA-01555, you can use a snapshot standby database.
When you upgrade an encrypted database to Oracle Database 19c you configure AutoUpgrade to change the keystore definition from sqlnet.ora to the new recommended parameter – WALLET_ROOT.
Slides from talk to Danish Oracle User Group.
Here is a sneak peek into our upcoming webinar.
AutoUpgrade allows you to fine-tune the parallel options of a database upgrade.
Follow-up on our Cool Features webinar with answers to the questions that we couldn’t answer live. Thanks for attending.
You can specify all input to AutoUpgrade in a single command – without using a config file. Ideal for scripting and automation.
You can use AutoUpgrade to perform unplug-plug upgrade of your PDB. It is faster, but there are some things you must be aware of.
It is easier to upgrade a Data Guard setup when using AutoUpgrade.
Learn all the details about the automated upgrade in OCI. In addition, you can find answers to the most common questions.
A new of AutoUpgrade is out and it contains several cool features like unplug/plug upgrade and better handling of data guard.
It is now possible to upgrade your database in OCI to Database 19c with just a few clicks.
Yes, it is. You can resume a terminated or lost session. AutoUpgrade will automatically pick up from where it left.
Even huge, TB-sized, databases can be migrated with very little downtime by using incremental backups. Now with step-by-step instructions.
You can upgrade and convert your database to a PDB without comprising your standby database. And you don’t even need the TDE keystore password.
Learn how to upgrade your database and keep the data guard setup intact.
Come join my talk on upgrading to Oracle Database 19c.
XTTS: Introduction – Minimal Downtime Migration with Full Transportable Export Import and Incremental Backups
Even huge databases can be migrated to the cloud with little downtime – even if you go across endian format. And you can even implicitly upgrade the database and convert to a PDB.
If you store the keystore password in the Secure External Password Store, you don’t have to type it in cleartext ever again.
You get much more functionality when using Local Undo in your CDB. Let AutoUpgrade enable it for you!
Get the slides from the webinar “Move to the Cloud – not only for techies”. Also, you can find the missing part on transportable tablespaces, and information about a recording.
We did a webinar today on Migration Strategies – Tips and Tricks and Insights and Secrets. Here is a wrap-up and link to the slides.
In mid-October you can join our two webinars on database migration. One of them is exclusively about cloud migration – for techies only.
If you are using the classic Preupgrade tool (preupgrade.jar) be sure to put it in the right place.
TDE Tablespace Encryption is a must-have in the cloud and something that most of us have to learn. I recently gave a presentation on the basics and what you will need to learn to survive in the cloud.
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.
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.
The third post in the series shows you how to install and configure the ZDM service host
Zero Downtime Migration is a cool and free tool that you can use to migrate into OCI. This blog post introduces the tool and gives you a good overview of the process and all the details.
SQLcl is the modern CLI for Oracle Database and it offers a ton of cool features and productivity boosts. Yet, still a lot of users are stuck in the last millennium aka SQL*Plus.
What will you do if things go south? On a VM DB System in OCI you can’t do a database downgrade unless you make special preparations in the new release CDB. In this post I will discuss why it is so, and what you can do to have the option of downgrading.
In this blog post I will show you how to upgrade a 18.104.22.168 PDB to 19c when it is running in a VM DB System. I have a PDB called SALES and it is running Standard Edition 2 (yes, this procedure works for Standard Edition 2 as well). In a previous blog post I went over the restrictions that apply to VM DB System and having those in mind I can create a high-level plan for the upgrade
This is the first post in a series on the entry-level database system in OCI – being Virtual Machine DB System (VM DB System). You don’t get the same specs as with Exadata DB Systems and Bare Metal DB Systems, but it is much more affordable and still a very good platform. There is good tooling that allows most operations to be fully automated. But there are some limitations that you must be aware of that makes upgrading slightly different.