Downtime

Upgrade Testing with a Refreshable PDB – does this work?

Yesterday, Daniel pinged me to discuss an upgrade testing scenario I had evaluated briefly by myself a while ago. I can’t remember why I gave up. But Daniel had some great ideas and tried already a lot in our OCI cloud. We want to use a refreshable PDB. And keep it up to date, then upgrade it. The idea of this approach: Whereas a CLONE or RELOCATE uses the initial command as the marker, a REFRESH would allow me to be way more in synch. So the question is: Upgrade Testing with a Refreshable PDB – does this work?

Upgrade Testing with a Refreshable PDB - does this work?

Photo

Continue reading...

3 Live Webinars: Multitenant Webinar 3 Questions answered

This is the third and final QA blog post for the webinars we did in the last week of April 2020. Thank you for your attendance. I will publish the replay recordings as soon as they are available and link them as well. For now, please find here 3 Live Webinars: Multitenant Webinar 3 Questions answered.

3 Live Webinars: Multitenant Webinar 3 Questions answered

Photo by Holger Link on Unsplash

Your Questions, our Answers for Webinar 3: Multitenant

103 We are in the process of migrating to Oracle Cloud using the xtts method for cross platform migration and we seem to be encountering an issue with it
Continue reading...

Upgrade PDBs with RELOCATE – How does it work?

Today Roy and I received a question from a colleague about the RELOCATE feature in Multitenant. And I’d like to shed some light and this topic a bit more. Upgrade PDBs with RELOCATE – How does it work?

Upgrade PDBs with RELOCATE - How does it work?

Photo by Sebastian Pena Lambarri on Unsplash

RELOCATE and UPGRADE?

At first, it looks very promising to me. RELOCATE uses the HOT CLONE functionality of Multitenant but then relocates the PDB from one to another CDB. You need to fulfill a few important requirements, for instance:

  • Local Undo must be enabled in both CDBs
    • This limits the technique to at least Oracle
Continue reading...

Save Patching Downtime with Oracle Multitenant?

At OOW 2019 we announced that you can have up to 3 user-created pluggable databases (PDBs) per container database (CDB) without having a Multitenant license. And in this blog post I’d like to demonstrate how you can save patching downtime with Oracle Multitenant.

The Concept

The idea this entire process settles on is very simple. When you create a fresh container database in the target (already patched!) environment, you don’t have to patch this one. You only have to relocate the PDB from the source into the target CDB. In addition, only datapatch needs to be executed. As the …

Continue reading...

Database Migration from non-CDB to PDB – The Minimal Downtime Challenge

There are several pitfalls when you plugin a non-CDB into a CDB environment. I’d like to highlight some of them – and show you potential workarounds as well. This is part of a series of blog posts to make your migration from non-CDB to PDB a bit smoother.

Database Migration from non-CDB to PDB – The Minimal Downtime Challenge

Database Migration from non-CDB to PDB – The Minimal Downtime Challenge

When we start to look at a migration from non-CDB to PDB for an important system, regardless of migrating on-prem or to the cloud, reducing the downtime is very important. In this blog post I’d like to highlight the different aspects …

Continue reading...

The OJVM Patching Saga – and how to solve it – Part V

Related Posts on
The OJVM Patching Saga – and how to solve it“:

MOS Note released explaining patching without STARTUP UPGRADE mode

An important note regarding OJVM rolling patching has been published on MyOracle Support:

MOS Note: 2217053.1
RAC Rolling Install Process for the “Oracle JavaVM Component Database PSU” (OJVM PSU) Patches

“Beginning with the Jan2017 OJVM PSU patchset for 11.2.0.4 and

Continue reading...

The OJVM Patching Saga – and how to solve it – Part IV

Related Posts on
The OJVM Patching Saga – and how to solve it“:

What is missing with the “Mitigation Patch?

Michael, the team lead from a large Oracle customer mailed me the other day. He wanted to disable Java on all their +600 databases by using the Mitigation Patch for OJVM. But he received a strange error when trying to enable the …

Continue reading...

The OJVM Patching Saga – and how to solve it – Part III

Related Posts on
The OJVM Patching Saga – and how to solve it“:

What is the “Mitigation Patch?

In MOS Note:1929745.1 – Oracle JavaVM Component Database Patches there’s a section called What is the Mitigation Patch. It says:
For situations where the latest OJVM PSU cannot be installed immediately there is a “Mitigation Patch” that can be used. The “Mitigation

Continue reading...

The OJVM Patching Saga – and how to solve it – Part II

Related Posts on
The OJVM Patching Saga – and how to solve it“:

Important Notes

Continue reading...

The OJVM Patching Saga – and how to solve it – Part I

Related Posts on
The OJVM Patching Saga – and how to solve it“:

Who’s the Product Manager for Patching?

First of all, I’m neither a patching expert nor am I the Product Manager for Patching. There’s no such role as far as I know but there are people inside Oracle who have way more clue about this topic. There’s a group …

Continue reading...

Save Upgrade downtime: Upgrade APEX upfront

See also:


With almost every patch or release upgrade of the Oracle Database a new version of Oracle Application Express (APEX) will be installed. And as APEX is part of the database installation it will be upgraded as part of the component upgrades after the ORACLE SERVER component has been successfully upgraded to the new releases.

APEXBut the APEX upgrade can take a bit (several minutes or even more in some cases). Therefore it is a common advice to upgrade APEX upfront before upgrading the database as this can be done online while the …

Continue reading...