CDB_REGISTRY

What does datapatch do when you have different components in PDBs?

Posted on February 9, 2022 by Mike.Dietrich Patch Recommendation 10

The last weeks, literally weeks, I have spent a lot of time with several patching topics. And in order to clean up my inbox a bit I will dump the learning into several blog posts. This one today will be about an interesting case I came across when a customer ran into problems with the runtime of datapatch in an ExaCC environment. Hence, today’s topic will be: What does datapatch do when you have different components in PDBs?

What does datapatch do when you have different components in PDBs?

Photo by Alexander Kirov on Unsplash

Annotation

If you are on 19.16.0 or higher, than you can safely ignore this blog post …

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.

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 …

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

Posted on August 1, 2019 by Mike.Dietrich Flaws and Pitfalls Single-/Multitenant 0

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 …

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

Posted on July 31, 2019 by Mike.Dietrich Flaws and Pitfalls Single-/Multitenant 6

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 …

What happens to components with OPTION OFF status during upgrade?

Posted on September 13, 2017 by Mike.Dietrich Upgrade / Migration 11

In the newer releases of Oracle database you may see components with status OPTION OFF in the database’s registry. But what happens to components with OPTION OFF status during upgrade? Will those stay on the old release?

What happens to components with OPTION OFF status during upgrade?

You may have a quick look into your DBA_REGISTRY (or CDB_REGISTRY). I used the check_components.sql script.

COMP_ID	COMP_NAME			   SCHEMA	STATUS	   VERSION
-------- ---------------------------------- ------------ ---------- ------------
CATALOG	Oracle Database Catalog Views	   SYS		VALID	   12.1.0.2.0
CATJAVA	Oracle Database Java Packages	   SYS		VALID	   12.1.0.2.0
CATPROC	Oracle Database Packages and Types SYS		VALID	   12.1.0.2.0
JAVAVM

CDB_REGISTRY

What does datapatch do when you have different components in PDBs?

Annotation

Database Migration from non-CDB to PDB – Various Pitfalls

Database Migration from non-CDB to PDB – Various Pitfalls

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

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

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

The Component Pitfall

What happens to components with OPTION OFF status during upgrade?

What happens to components with OPTION OFF status during upgrade?

Archives

Categories

Upgrade @YouTube

RSS Feed for Upgrade your Database – NOW!

Subscribe via Email

Follow me on Twitter

Recent Posts