upgrade

Video: Best Practices to Upgrade to Oracle Database 19c

This is a short “Black Friday” blog post. And just if you are tired already of hunting supposed-to-be-bargain-buys, you may need something to relax – and watch this Video: Best Practices to Upgrade to Oracle Database 19c.

Video: Best Practices to Upgrade to Oracle Database 19c

Roy recorded it as part of the Quest Experience Week. We’d like to share it with you here.

Just click on the picture below to open a new TAB and watch the 1 hour video:

 

If you are looking for the slide deck, you can download them from:

Thanks!

–Mike…

Continue reading...

AutoUpgrade Tips: Running two (or more) sessions in parallel

Our intention with the AutoUpgrade as the single tool to upgrade your databases was initially: You have one big config file for your databases. And you will use this file to upgrade your databases unattended. Ideally you run an “analyze” at first, then you schedule a “deploy” for overnight or the next weekend or whenever it is convenient for you. But sometimes people have different needs. In this particular case several people asked whether you can run multiple AutoUpgrade tools in parallel on the same server. Hence, I’d like to explain the first of more AutoUpgrade …

Continue reading...

AutoUpgrade may fail when patch ID column is NULL

Monday morning – it’s time to write a new blog post. And actually I will set priorities based on what you reported to me in the past week. This way it may prevent others from hitting the same pitfall. The AutoUpgrade may fail when patch ID column is NULL in REGISTRY$HISTORY.

AutoUpgrade may fail when patch ID column is NULL

Photo by Etienne Boulanger on Unsplash

What is happening?

You start a database upgrade with autoupgrade. But the initial check will fail with a message like this:

AutoUpgrade tool launched with default options
There was an error initializing the patching information for entry upg2

The AutoUpgrade won’t kick …

Continue reading...

New version of Upgrade / Migrate / Consolidate to Oracle 19c uploaded

Please apologize that it took me a bit longer to upload a new version of our comprehensive slide deck. You can download now a new version of “Upgrade / Migrate / Consolidate to Oracle 19c” via the blog’s download page.

New version of Upgrade / Migrate / Consolidate to Oracle 19c uploaded

Why is there a new version?

Since Oracle Open World 2019 we have a new corporate template. And while I like the graphics quite a bit, I’d say, the people who built it have a good sense for graphics. But they aren’t powerpoint experts. In fact, almost every slide had to be adjusted. This may not be a huge …

Continue reading...

Market Driven Support for Oracle Database 11.2.0.4

I know that some of you are still on Oracle 11.2.0.4. And I don’t want to argue, why. I’m pretty sure there’s a good reason that you haven’t upgraded yet. Just remember: You can upgrade directly from Oracle 11.2.0.4 to Oracle 19c. Just in case you plan to stay longer than end of 2020 on this ancient release, then you may want to read about the Market Driven Support for Oracle Database 11.2.0.4.

Market Driven Support for Oracle Database 11.2.0.4

Overview Support Periods Oracle 11g Release 2

First of all, let me give a quick overview on Oracle Database 11g Release 2 – usually …

Continue reading...

OOW 2019 – Database Upgrade Talks and Labs

Oh … time flies so fast. Just a few days until I will sit in a airplane to SFO. And on Monday at 7:00h the registration opens. As we have a lab at 8:30h already, just remembering the loooooong lines around the block last year, I will need to be there very early. It’s just a few days until OOW 2019 – Database Upgrade Talks and Labs information is here.

OOW – Oracle Open World 2019 in San Francisco

OOW 2019 - Database Upgrade Talks and Labs

Photo by Robert McLay on Unsplash

When? September 16-19, 2019

Where? San Francisco, USA

What? Find the session catalog here

Continue reading...

The September 2019 AutoUpgrade – and the AutoUpgrade Video

My team mates work really hard. And I’m really proud on all of them. We try to fix upcoming issues or requirements with the new AutoUpgrade tool as quickly as possible and still maintain very high quality standards. And here it is, the September 2019 AutoUpgrade – and the AutoUpgrade video as a bonus in addition. Just in case you haven’t seen it in action and can’t join us at OOW 2019.

The September 2019 AutoUpgrade - and the AutoUpgrade Video

Download the September 2019 AutoUpgrade Tool

You can simply download the tool from MOS Note: 2485457.1 – AutoUpgrade Tool.

MOS Note: 2485457.1 – AutoUpgrade Tool:

Watch the AutoUpgrade Video

I just uploaded …

Continue reading...

Exadata Upgrade to OL7 and to Oracle 19c

This is just a short blog post to ensure I will find the necessary information when somebody asks me again.. In case you plan to do an Exadata upgrade to OL7 and to Oracle 19c, the below links are the most important ones you should start with.

Exadata Upgrade to OL7 and to Oracle 19c

Exadata Upgrade to OL7 and to Oracle 19c

–Mike…

Continue reading...

Database Migration from non-CDB to PDB – Migration with Data Pump

You may have realized that there are a few techniques missing describing how to do a Database Migration from non-CDB to PDB – Migration with Data Pump is one of them. I will explain the most simple approach of going to Single- or Multitenant. It isn’t the coolest – and it isn’t very fast as soon as your database has a significant size. But it is not complex. And it allows you to move even from very old versions directly into an Oracle 19c PDB – regardless of patch levels or source and destination platform.

Database Migration from non-CDB to PDB – Migration with Data Pump

High Level Overview

Endianness change
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...

Database Migration from non-CDB to PDB – The Fallback 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 Fallback Challenge

Photo by Sebastian Grochowicz on Unsplash

Database Migration from non-CDB to PDB – The Fallback Challenge

As I work with customers on upgrades and migrations for a very long time, I know how important a proper fallback is.

When you attempt a migration from a non-CDB to PDB, you need to plan …

Continue reading...

Database Migration from non-CDB to PDB – Various Pitfalls

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 - Various Pitfalls

Photo by timJ on Unsplash

Database Migration from non-CDB to PDB – Various Pitfalls

In all the previous blog posts of this series I tried to explain specific pitfalls, and how you can workaround them. This article is meant to collect the “leftovers”, the minor issues and pitfalls which you may not …

Continue reading...

Database Migration from non-CDB to PDB – The Patch Level Pitfall

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 Patch Level Pitfall

Photo by Piron Guillaume on Unsplash

Database Migration from non-CDB to PDB – The Patch Level Pitfall

When you consolidate on a larger scale, it is very likely that you have different patch levels in your database environments. But when you attempt to plugin a non-CDB into a CDB, you may see …

Continue reading...

Database Migration from non-CDB to PDB – The Component Pitfall

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 Component Pitfall

Photo by Brett Jordan on Unsplash

The Component Pitfall

With component we mean the database component which you can find in DBA_REGISTRY – or CDB_REGISTRY. When Multitenant became available over 5 years ago, a decision had been made to make all options/components mandatory in a container database. This decision had to …

Continue reading...

Database Migration from non-CDB to PDB – The Time Zone Pitfall

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 Time Zone Pitfall

Photo by Allef Vinicius on Unsplash

Database Migration from non-CDB to PDB – The Time Zone Pitfall

Interestingly, there is no issue with different time zone settings within a single CDB. Your CDB$ROOT can be on DST V.32 whereas a PDB you plugin can be already on DST V.33. But only

Continue reading...

Database Migration from non-CDB to PDB – The COMPATIBLE pitfall

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 COMPATIBLE pitfall

Database Migration from non-CDB to PDB – The COMPATIBLE pitfall

When you migrate your non-CDB to PDB, in most cases the COMPATIBLE setting of the non-CDB will be lower than the setting of the receiving CDB. But still in this case you may see warnings. I will explain how to deal with …

Continue reading...

Database Migration from non-CDB to PDB – Typical Plugin Issues and Workarounds

In the previous blog posts I showed different approaches on how to migrate your database on a same Endianness platform into Multitenant. Whether you prefer to upgrade first or plugin first is up to you. I recommend upgrading first as this allows you a seamless fallback. But regardless of which approach you prefer, you may take care on potential pitfalls. Hence, this blog post is about Database Migration from non-CDB to PDB – Typical Plugin Issues and Workarounds. It may not be complete when I publish it and I may extend it later on. Let me know if you have …

Continue reading...

Database Migration from non-CDB to PDB – Clone via NON$CDB, upgrade, convert

The third option for plugging in a non-CDB is called Database Migration from non-CDB to PDB – Clone via NON$CDB, upgrade, convert. As I showed already in this blog post a while ago, your source must be at least an Oracle 12.1 database. And this technique can be used also only for same-Endianness migrations but does not apply if you’d like to migrate from Big to Little Endian. If your source database matches already the receiving CDB, no upgrade is necessary.

Database Migration from non-CDB to PDB – Clone via NON$CDB, upgrade, convert

Photo by Samuel Chan on Unsplash

High Level Overview

Endianness change possible:
No
Source database versions: Oracle 12.1.0.2
Continue reading...

Database Migration from non-CDB to PDB – Plug in, upgrade, convert

This is my next blog post about Database Migration from non-CDB to PDB – Plug in, upgrade, convert. But what is different from the previous one? And why is it necessary? Since Oracle Database 12.2.0.1 you can plugin a non-CDB at first, the upgrade and convert it. And I’ll show you this technique here.

Database Migration from non-CDB to PDB – Plug in, upgrade, convert

Photo by Dan Freeman on Unsplash

High Level Overview

Endianness change possible: No
Source database versions: Oracle 12.2.0.1 or newer (or 12.1.0.2 when CDB has shared UNDO)
Characteristic: Plugin into CDB first
Upgrade necessary: Yes, after plugin
Downtime: Plugin, copy (optional), upgrade and noncdb_to_pdb.sql
Minimal
Continue reading...

Database Migration from non-CDB to PDB – Upgrade, plug in, convert

As first blog post of this series about Database Migration from non-CDB to PDB – Upgrade, plug in, convert I will explain the most straight forward approach of going to Single- or Multitenant. But you have other options as well. which I’ll showcase in the other blog posts. I demonstrated this technique on the blog already a while ago. But since Oracle 12.2.0.1, there are a few other options available.

Database Migration from non-CDB to PDB - Upgrade, plug in, convert

High Level Overview

Endianness change possible: No
Source database versions: Oracle 11.2.0.4 or newer
Characteristic: Upgrade non-CDB first
Upgrade necessary: Yes, before plugin
Downtime:
Upgrade, plugin, copy (optional) and
Continue reading...

Database Migration from non-CDB to PDB – Overview

Today I’ll start a blog post series of several “how to” articles about database migration from non-CDB to PDB – Overiew. You’ll find a quick introduction below. And of course, the links to all the other related blog posts.

Database Migration from non-CDB to PDB – Overview

When you plan to move from non-CDB, the Oracle term for regular database deployments, to a Pluggable Database (PDB), you will migrate your database. It will become a PDB and run as part of a Container Database (CDB). This is a well known concept for several years now called Oracle Multitenant. If you …

Continue reading...

Please download the new July 2019 (20190715) AutoUpgrade

Since last night, the new version of the AutoUpgrade utility is available. Please download the new July 2019 (20190715) AutoUpgrade and exchange your previous version in your destination $ORACLE_HOME/rdbms/admin with this one.

Download

Please download the tool from: MOS Note: 2485457.1 – AutoUpgrade Tool

When you copied the new tool, call it for a version check to make sure you are using the most recent one:

$ java -jar $OH19/rdbms/admin/autoupgrade.jar -version
build.version 20190715
build.date 2019/07/15 12:45:48

Please notice that the tool allows you to upgrade to Oracle 12.2.0.1 and Oracle 18c as well:

 

Please download the new July 2019 (20190715) AutoUpgrade

The listed releases are the minimum …

Continue reading...

AutoUpgrade: Where do you find all the logfiles?

AutoUpgrade: Where do you find all the logfiles?In the previous blog posts you could read about how to create the configuration file, adjust it and tweak the init parameters for the AutoUpgrade tool. And then I described the different modes of it. In this blog post I’d like to give you some insights into AutoUpgrade: Where do you find all the logfiles?

AutoUpgrade: Where do you find all the logfiles?

AutoUpgrade – Step-by-step

  1. The new AutoUpgrade Utility – Download, documentation and supported versions
  2. Create and adjust the config file for AutoUpgrade
  3. Config file for AutoUpgrade – Advanced options
  4. Config file for AutoUpgrade – Tweaking init parameters
  5. AutoUpgrade: ANALYZE, FIXUPS, UPGRADE and DEPLOY modes
  6. AutoUpgrade:
Continue reading...

AutoUpgrade: ANALYZE, FIXUPS, UPGRADE and DEPLOY modes

AutoUpgrade: ANALYZE, FIXUPS, UPGRADE and DEPLOY modes

Photo by Debby Hudson on Unsplash

In the previous blog posts I explained mainly how to create, alter and tweak the configuration file for the AutoUpgrade tool. By now you should have your config file set up and adjusted for your environment(s). Let me go a step further and explain the different processing modes of AutoUpgrade: ANALYZE, FIXUPS, UPGRADE and DEPLOY modes. Then you’ll have a precise idea what the tool is actually doing, and how it operates.

AutoUpgrade – Step-by-step

  1. The new AutoUpgrade Utility – Download, documentation and supported versions
  2. Create and adjust the config file for
Continue reading...

The new Oracle 19c Hands-On Lab is available

Well, it’s been a while since we refreshed the lab being downloadable via this blog. But finally, the new Oracle 19c Hands-On Lab is available – you can download it as of now.

What’s new in the lab?

First of all, the biggest change you’ll see is that the operating system is now Oracle Linux 7. Well, to be honest, I’m not a die-hard Linux expert and you may find my setup a bit creepy. Feel free to exchange things or adjust them – or drop me a message if you think that adjustments should be made. And of …

Continue reading...