CDB_REGISTRY

Database Migration from non-CDB to PDB – Various Pitfalls

Posted on August 2, 2019 by Flaws and Pitfalls Single-/Multitenant 20

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

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

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

Posted on July 31, 2019 by Flaws and Pitfalls Single-/Multitenant 4

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

What happens to components with OPTION OFF status during upgrade?

Posted on September 13, 2017 by Upgrade / Migration 4

What happens to components with OPTION OFF status during upgrade?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
… Continue reading...

Archives

Categories

Upgrade @YouTube

Blog Stats

  • 1,880,065 hits

Subscribe via Email

Join 3,788 other subscribers

Follow me on Twitter