Pitfall

OJVM patching fails with ORA-1403 in 19.30 if JAVAVM is not installed

Thanks to all the people (Jeff, Daniele, Lothar and others) who alerted me about this topic. Some of you had even created their own fix already. So, this is about an issue which happens only if you have no JAVAVM installed in your database or PDB but you still apply the OJVM Bundle on to of the Oracle Database 19.30 Release Update. You may find then: OJVM patching fails with ORA-1403 in 19.30 if JAVAVM is not installed.

OJVM patching fails with ORA-1403 in 19.30 if JVM is not installed

Photo by Michiel Leunens on Unsplash

When does this happen?

This issue happens when you apply the OJVM bundle together with …

ORA-13516 “CATPROC not valid” during datapatch or autoupgrade to 19.18.0

Posted on February 24, 2023 by Mike.Dietrich Flaws and Pitfalls Patch Recommendation 18

I thought I could relax this week using my leftover vacation days from 2022. But this issue is triggering me since some of you mailed me already. Maybe this blog post can prevent others from being trapped by this issue: ORA-13516 “CATPROC not valid” during datapatch or autoupgrade to 19.18.0. And as a prolog, you will NOT see the below issue when you started your database in NORMAL mode for the execution of datapatch.

ORA-13516 "CATPROC not valid" during datapatch or autoupgrade to 19.18.0

Photo by Greg Rosenke on Unsplash

What is the symptom?

Regardless of whether you patch to Oracle Database RU 19.18.0 manually or with …

Pitfall: Upgrade to 21c fails when ORDIM is present but no SDO

Posted on August 25, 2021 by Mike.Dietrich Flaws and Pitfalls Oracle Database 21c Upgrade / Migration 4

You may have read my previous blog post about Upgrading a non-CDB to Oracle Database 21c. And I referred to a potential Pitfall: Upgrade to 21c fails when ORDIM is present but no SDO. In this blog post I would like to explain how to avoid this pitfall beforehand and explain what needs to be done.

Pitfall: Upgrade to 21c fails when ORDIM is present but no SDO

Photo by Sara Codair on Unsplash

What’s the problem?

In my previous blog post I showed you the ideal and normal way. But during my tests I came across an issue I was not aware of – and I simply had no …

AutoUpgrade and the Partial Offline Backup Strategy

Posted on August 18, 2020 by Mike.Dietrich AutoUpgrade Flaws and Pitfalls 3

In our Fallback talk we promote a backup strategy for large DWHs and database which are on purpose in NOARCHIVELOG mode. But last week I learned that there is something important to know about AutoUpgrade and the Partial Offline Backup Strategy. Otherwise you may hit a

AutoUpgrade and the Partial Offline Backup Strategy

Photo by Esri Esri on Unsplash

pitfall.

Partial Offline Backup Strategy?

I won’t explain in all details what this is. If you’d like to read more, please find all the necessary information on my blog post from July 17, 2018:

Fallback Strategy: Partial Offline Backup

with graphics included. In brief, you take …

Oracle Multitenant: Be aware of the silent COMPATIBLE change

Posted on February 7, 2020 by Mike.Dietrich Single-/Multitenant 5

This topic is included in our Multitenant slides for a long time. But whenever I want to point somebody to the blog post, I realize that it’s not on the blog yet. Actually I discussed this topic recently during a customer visit again. It’s time to put it on the blog. When you use Oracle Multitenant: Be aware of the silent COMPATIBLE change.

Oracle Multitenant: Be aware of the silent COMPATIBLE change

Photo by Clint Patterson on Unsplash

Mixed version environments

When you work with Oracle Multitenant, the sooner or later you will have mixed version environments. This may be CDBs with Oracle 12.1.0.2 or Oracle 12.2.0.1 together with …

AutoUpgrade may fail when patch ID column is NULL

Posted on November 25, 2019 by Mike.Dietrich AutoUpgrade 39

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 …

RMAN backup generates traces in Oracle 12.2.0.1

Posted on May 24, 2018 by Mike.Dietrich Flaws and Pitfalls 5

RMAN backup generates traces in Oracle 12.2.0.1 Oracle 12.2.0.1 seems to be the “tracing” release without further patch or parameter treatments. After posting about MMON unconditional traces in Oracle 12.2.0.1 a day ago, I received a couple of comments either on the blog, via LinkedIn or Twitter regarding other trace facilities in Oracle Database 12.2.0.1. One of them is the case that RMAN backup generates traces in Oracle 12.2.0.1.

And please, very important upfront:
Oracle Database 12.2.0.1 is a very stable and reliable release based on all the customer feedback Roy and I received so far. For instance, when we check for optimizer issues …

Upgrade to Oracle 12.2.0.1: Check your DEFAULT temporary tablespaces

Posted on March 22, 2018 by Mike.Dietrich Flaws and Pitfalls 18

One of the reasons why I have this blog is simply to stay in touch with smart people using Oracle and telling me about issues I haven’t seen before. Thanks to Tyler Van Vierzen I learned that an upgrade to Oracle 12.2.0.1 may alter the default local temporary tablespace.

Upgrade to Oracle 12.2.0.1: Check your DEFAULT temporary tablespaces

Tyler did contact me on Twitter:

“Curious if you’ve seen this… Seeing new “local temp tablespace” set to SYSTEM for some users after 12.2 upgrade. But not all. No discernable pattern. Some null (so default to their temp tablespace), some set equal …

Optimizer Issue in Oracle 12.0.1.2: “Reduce Group By”

Posted on July 28, 2015 by Mike.Dietrich Flaws and Pitfalls Optimizer Oracle Database 12c Parameters 4

DBAs biggest fears I’d guess are Optimizer Wrong Query Results bugs as usually the optimizer does not write a message into the alert.log saying “Sorry, I was in a bad mood today …”.

The Oracle Database Optimizer is a complex piece – and in Oracle 12c it delivers great performance results. Plus (my personal experience when you know what to do) it is more predictable which I like a lot when changing databases from one to another release. But due to its complexity sometimes we see issues – and sometimes it is necessary to switch off tiny little pieces …

Pitfall

OJVM patching fails with ORA-1403 in 19.30 if JAVAVM is not installed

When does this happen?

ORA-13516 “CATPROC not valid” during datapatch or autoupgrade to 19.18.0

What is the symptom?

Pitfall: Upgrade to 21c fails when ORDIM is present but no SDO

What’s the problem?

AutoUpgrade and the Partial Offline Backup Strategy

Partial Offline Backup Strategy?

Oracle Multitenant: Be aware of the silent COMPATIBLE change

Mixed version environments

AutoUpgrade may fail when patch ID column is NULL

What is happening?

RMAN backup generates traces in Oracle 12.2.0.1

Upgrade to Oracle 12.2.0.1: Check your DEFAULT temporary tablespaces

Upgrade to Oracle 12.2.0.1: Check your DEFAULT temporary tablespaces

Optimizer Issue in Oracle 12.0.1.2: “Reduce Group By”

Archives

Categories

Upgrade @YouTube

RSS Feed for Upgrade your Database – NOW!

Subscribe via Email

Recent Posts