Patch

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

Update (RU) 19.3.0 withdrawn and superseded with 19.3.1

Actually I really refused to blog about this for a few weeks now. But as I receive more questions and read more tweets, I think I need to shed some light and help avoiding confusion. And as readmes and MOS notes are not entirely in sync, you may get confused if you don’t read the “correct” document.

Update (RU) 19.3.0 withdrawn and superseded with 19.3.1

Photo by camilo jimenez on Unsplash

Oracle 19.3.0 Update (RU)

In April, Oracle released the 19.3.0 Release Update (RU) on Linux and Solaris only. As you can read in my blog post from April 25, 2019, this is a patch bundle meant for …

Continue reading...

Oracle Database 19c (19.3.0) for Linux is available for download

Oracle Database 19c (19.3.0) for Linux is available for download as of now from OTN and eDelivery. For those of you who started with Oracle Database 19.2 already, the Updates (RU) 19.3.0 for the database and GI are available as well for Linux and Solaris.

Oracle Database 19c on premises for Linux

You can download Oracle Database 19.3.0 on-prem for Linux now from the usual sources:

The download offering includes the zip, the RPM for the database, and Grid Infrastructure, the Client and more.

Oracle Database 19c (19.3.0) for Linux is available for download

The other ports will follow soon.

Oracle 19c Documentation

And of course …

Continue reading...

You MUST patch 12.1.0.1 and 11.2.0.3 and older databases before June 2019

First of all, this blog post is not new. I blogged about this SCN topic a while ago already. But some of you seem to operate still older databases for various reasons. And even if you think that you are safe, double check for any older databases in your environments. You MUST patch 12.1.0.1 and 11.2.0.3 and older databases before June 23, 2019. And just to be clear: June 23, 2019 is going to happen in less than 4 months.

You MUST patch 12.1.0.1 and 11.2.0.3 and older databases before June 2019

Photo by Dimitar Donovski on Unsplash

Who is NOT affected?

If you use the following Oracle database releases …

Continue reading...

In case you miss DBMS_OPTIM_BUNDLE in 12.2

Strange things happen sometimes. I got alerted by a customer before Christmas about package DBMS_OPTIM_BUNDLE missing after applying a Release Update. I’ve had a conversation with Nigel Bayliss, the Optimizer PM – but Nigel hasn’t heard of such things either. We both investigated but couldn’t reproduce the issue. But after the end-of-the-year holidays I received similar messages from other customers. In case you miss DBMS_OPTIM_BUNDLE in 12.2, then this blog post should help you.

In case you miss DBMS_OPTIM_BUNDLE in 12.2

Photo by Caleb Woods on Unsplash

What is DBMS_OPTIM_BUNDLE?

I blogged about this package in the past already several times:

Continue reading...

DST Time Zone Patch V.32 and V.33 for Oracle 18.5.0

If you’d ever attended one of Roy’s or my workshops, you know that we talk about time zone adjustments after the database upgrade. We explain why this is important. But as everything, it depends if you really need to apply and adjust. In our workshops we recommend one single note for time zone adjustments: MOS Note:412160.1 . This note has been updated and republished. It contains DST V.32 and DST V.33 links and references. Amit Grover from AWS contacted me and told me about a potential dependency of DST patches to the Oracle Update such as RU 18.4.0 or 18.5.0.…

Continue reading...

How to patch all PDBs with the a new time zone file?

Yesterday I wrote about how to adjust the time zone setting in the PDB$SEED as by default the time zone scripts won’t touch the PDB$SEED when you execute them. And in addition, MOS Note:1509653.1 tells you, that the PDB$SEED can’t be adjusted. But this leads to a weird mix of time zone settings across a Multitenant deployment. Which I’d guess is not desired. Following a tweet reply by Marco Mischke I realized: I explained how to patch the PDB$SEED – but I didn’t explain how to patch all PDBs with the a new time zone file?

How to patch all PDBs with the a new time zone file?

Photo by Laureen

Continue reading...

Does the PDB$SEED get “time zone” patched or not?

Today I received a question from a very experienced Oracle ACS engineer whether the PDB$SEED get time zone patched or not when a time zone patch gets applied. I’d say spontaneously “Of course, it does” but after thinking for a few seconds I started having doubts. Question is: Does the PDB$SEED get “time zone” patched or not?

Does the PDB$SEED get "time zone" patched or not?

Photo by Luis Cortes on Unsplash

Time zone scripts are in ?/rdbms/admin since Oracle 18c

First of all, since Oracle Database 18c the scripts to adjust time zone settings of the database are in ?/rdbms/admin. If you did our Hands-On Lab already …

Continue reading...

Does OJVM patching require a specific Database Release Update?

This question came up several times in the past days: Does OJVM patching require a specific Database Release Update? People mentioned that there’s a significant difference between the OJVM Patch Readme between Oracle 12.2.01 and Oracle 18.4.0.

Photo by Jimmy Ofisia on Unsplash

What’s the point?

In the OJVM (Oracle Java Virtual Machine) Patch Readme for Oracle Database 12.2.0.1 a sentence clarified that you can combine different states of OJVM and Database patch bundle with each other. Your database home could have been patched with the April 2018 Update, whereas you decided to apply the October 2018 OJVM patch.

The …

Continue reading...

Why Release Update Revisions (RUR) are tricky

A while ago we introduced Release Updates (RU) and Release Update Revisions (RUR). And despite the fact that not only we but also well known external experts such as Ludovico Caldara recommend to stay with Release Updates and simply ignore the Revisions, some people use them. There may be reasons for doing so. But in this blog post I will explain why Release Update Revisions (RUR) are tricky.

Photo by Michał Parzuchowski on Unsplash

Photo by Michał Parzuchowski on Unsplash

Differences between Updates and Revisions?

I tried to explain the differences between Updates and Revisions a while ago – and also compare them to PSUs and …

Continue reading...

Why is the October Patch Bundle from July?

Strange blog headline, isn’t it? Intentionally. Peter Lehmann mailed me a question – and asked more or less: Why is the October Patch Bundle from July? Sounds strange? It is strange …

Strange notation

Peter wanted to download the most recent patch bundle for Grid Infrastructure from October. And he found patch 28507693:

But he was wondering about the headline having the date of October 18, 2018 together with JUL 2018.

Why is the October Patch Bundle from July?

How does this make sense??

Flashback

When you flash back to the day when we introduced “Updates” (RU) and “Revisions” (RUR) you may remember that we release quarterly “Updates” …

Continue reading...

RMAN Backup Gives RMAN-06091: No Channel Allocated for Maintenance

RMAN Backup Gives RMAN-06091: No Channel Allocated for MaintenanceI really don’t want to turn this blog into an accumulation of issues and flaws. But as I explained many times before, the blog for me is also a way to dump information I likely will need the sooner or later again.

Recently I blogged about another RMAN issue in Oracle 12.2.0.1 with traces. This was fixed with the July 2018 RU for Oracle 12.2.0.1. But the issue below about which Piero Ferraz from Brazil alerted me (thanks!!!), happens in exactly this RU.

RMAN Backup Gives RMAN-06091: No Channel Allocated for Maintenance

This issue gets introduced with the July …

Continue reading...

Oracle 18.3.0 on premises includes 1.4GB patches?

Oracle Database 18.3.0 on premises is available for download on Linux since July 23, 2018. The other ports will follow soon. And via twitter I received a question why Oracle 18.3.0 on premises includes 1.4GB patches?

Oracle 18.3.0 on premises includes 1.4GB patches?

When you unzip the downloaded database image:

Oracle 18.3.0 on premises includes 1.4GB patches?

then you may discover the following folder .patch_storage of 1.4GB size:

[oracle@localhost .patch_storage]$ ls -lrt
total 40
drwxr-xr-x. 4 oracle dba 4096 Jul 18 19:39 28090523_Jul_14_2018_00_03_50
drwxr-xr-x. 4 oracle dba 4096 Jul 18 19:40 28090553_Jul_11_2018_19_20_31
drwxr-xr-x. 4 oracle dba 4096 Jul 18 19:41 27923415_Jul_15_2018_10_33_22
drwxr-xr-x. 8 oracle dba 4096 
Continue reading...

July 2018 Update, Revision, BPs, PSUs – delays and other issues

This is a Friday morning blog post. And actually I had no intention to write it. I don’t mean it offensive. But yesterday I received an interesting email from Frits Hoogland from Enkitec/Accenture. Frits asked me about the July RUR and some unlogic things on MOS. Once I had answered his email, the next question came in. Hence, I thought I need to write something about our July 2018 Update, Revision, BPs, PSUs – delays and other issues.
July 2018 Update, Revision, BPs, PSUs - delays and other issues

From being on stage at last year’s DOAG Conference for a “Patching Forum” I know that things aren’t as …

Continue reading...

Patching my databases with the July 2018 PSU, BP and RU

Patching my databases with the July 2018 PSU, BP and RUAs usual I download the patch bundles  and apply them to our Hands-On Lab environment as quickly as possible. First of all for the simple reason that I don’t want to trap into issues which are fixed already. Second for the reason that I always tell you: YOU MUST PATCH! But if I’m saying this over and over again, then I can’t have my own environments unpatched. And at third, because I want to learn if anything is not working correctly or has changed (see below).

Of course my tiny single instance environments are not comparable to your critical production …

Continue reading...

Data Pump 12.1.0.2 – Wrong Dump File Version – ORA-39142

Data Pump 12.1.0.2 - Wrong Dump File Version - ORA-39142Again I’ll have to thank my colleague Roland Gräff from the German ACS Support team in Stuttgart for bringing this into our radar. Roland alerted me a week ago about an issue with exports in Oracle 12.1.0.2 only when you are on a certain patch level. I summarize the issue here under Data Pump 12.1.0.2 – Wrong Dump File Version – ORA-39142.

In the below blog post you will learn about the actual issue, where it happens and when, and of course how to workaround it.

When does it happen?

The issue I will describe below happens only with

Continue reading...

Special characters show junk in CLOB columns after upgrade to Oracle 12.2.0.1 with JDBC

Special characters show junk in CLOB columns after upgrade to Oracle 12.2.0.1 with JDBCThanks to my support colleague Roland Graeff who told me about this issue at a customer today. And I consider this a pretty serious issue. It can happen that Special characters show junk in CLOB columns after upgrade to Oracle 12.2.0.1. with JDBC.

This is as bad as it sounds. Roland told me about a case where the application showed weird characters instead of German umlauts (ä, ö, ü, Ä, Ö, Ü) after an upgrade from Oracle Database 12.1.0.2 to 12.2.0.1.

Special characters show junk in CLOB columns after upgrade to Oracle 12.2.0.1 with JDBC

Roland explained to me that …

Continue reading...

Patching Oracle Database 18.1.0 to 18.2.0 on premises

In this part of my blog post series about upgrading from Oracle 12.2.0.1 to Oracle 18c I’d like to demonstrate patching Oracle Database 18.1.0 to 18.2.0 on premises.Patching Oracle Database 18.1.0 to 18.2.0 on premises

A while ago I showed also how to patch from Oracle 18.1.0 to 18.2.0 in the Oracle Cloud.

Find the related blog posts here:

Patching Oracle Database 18.1.0 to 18.2.0 on premises

Before I can start patching to the Release Update Oracle 18.2.0 I need to download the patch …

Continue reading...

ORAWORLD Mag: Oracle Database Patching – Tips & Tricks

Thanks to DOAG and the ORAWORLD Magazine, my article is released in the current September 2018 ORAWORLD Mag: Oracle Database Patching – Tips & Tricks

ORAWORLD Mag: Oracle Database Patching - Tips & Tricks

ORAWORLD Mag: Oracle Database Patching – Tips & Tricks

You’ll find my article about Database Patching – Tips & Tricks on page 28ff in the September 2018 issue if the ORAWORLD magazine. Please download it from here.

And of course, you will find other issues on the website of the ORAWORLD Magazine:

Further Information

Continue reading...