Workaround

ORA-12850 when you run AutoUpgrade?

Nicola made a comment the other day informing me that they hit an issue on some of their databases when upgrading. But is there a general issue with ORA-12850 when you run AutoUpgrade? Or is this error just the reflection of another issue? Let’s see, I will explain this and include a workaround as well.

Photo by Jamie Street on Unsplash

What is the problem?

Nicola traced it down mostly already. During the upgrade of their CDBs, this error happened in some runs:

with segments as (select /*+ MATERIALIZE PARALLEL(2) */ tablespace_name, inuse from( select ds.tablespace_name, row_number() over (partition by

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

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 …

Upgrading a PDB with JVM may result in ORA-7445 joevm_invokevirtual

Posted on September 29, 2021 by Mike.Dietrich Flaws and Pitfalls JVM 3

As you know, this blog is also my brain dump about Oracle topics. Since this one happened yesterday, mostly at night with the help of my team mates and the Java team, I’d like to write it down into this blog post: Upgrading a PDB with Java may result in ORA-7445 joevm_invokevirtual() as it is still fresh and may affect you as well. If you don’t have PDBs, if you don’t have Java (or JVM) in it or if you upgraded already to Oracle Database 19c, you can stop reading now.

Upgrading a PDB with Java may result in ORA-7445 joevm_invokevirtual

Photo by Fahmi Fakhrudin on Unsplash

What

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 may run into a timeout when GI is lower than 19.10.0

Posted on June 21, 2021 by Mike.Dietrich ASM / RAC / GI Patch Recommendation 9

The other day I received a question from a colleague about the risk of having GI and database both not being on the same RU. And a long while ago I blogged about it. We recommend that you keep it in synch. But you don’t have to. At the same time I received a wish from Ernst Leber to post something on the blog he and his colleague had trouble with when upgrading to 19c in a RAC environment. AutoUpgrade hung. But he titled his email with “not an AutoUpgrade problem!”. Still I agree, it is worth to write …

Oracle 19c on Windows may flood your trace file directory

Posted on March 11, 2021 by Mike.Dietrich Flaws and Pitfalls Oracle Database 19c 21

Oh … it’s Windows week here. And all this even though since I didn’t install Oracle on Windows for quite a while. But of course I’m fully aware that many of you out there operate Oracle on Windows. In this particular case thanks to Joël for the pointer to this issue. Oracle 19c on Windows may flood your trace file directory.

Oracle 19c on Windows may flood your trace file directory

Photo by Daniel von Appen on Unsplash

What happens?

In every release of Oracle 19c, at least until 19.10.0 BP, you may find out that every few minutes a trace file gets written into the %ORACLE_BASE%\diag\..\..\trace directory. And all …

Workaround for sdoloadj.sql errors with Datapatch in 19.9.0 and 19.10.0

Posted on March 2, 2021 by Mike.Dietrich Flaws and Pitfalls 6

The other week a customer from my hometown alerted me about an issue they saw when applying the 19.9.0 RU. A long sequence of errors in the datapatch run, all of them signaled from sdoloadj.sql. They opened an SR. And Support had an – understandable – recommendation the customer didn’t want to implement: Install JAVAVM. But thanks to my PM mate, Hans Viehmann (Mr Spatial), here is a simple Workaround for sdoloadj.sql errors with Datapatch in 19.9.0 and 19.10.0. And it may even apply to later releases, too.

Workaround for sdoloadj.sql errors with Datapatch in 19.9.0 and 19.10.0

Photo by Mael BALLAND on Unsplash

What happens?

Take …

Virtual Classroom Episode 8: Upgrade Internals and so much more

Posted on February 9, 2021 by Mike.Dietrich Workshop 2

This is your final chance to sign up within the next hours to our Virtual Classroom Episode 8: Upgrade Internals and so much more We will run this session on Wednesday Feb 10 at 10:00h CET tomorrow. And in case you don’t know yet what to do on a ice-cold winter Wednesday morning, this is what you should do.

Everything You Always Wanted to Know About Upgrades (But Were Afraid to Ask)

Virtual Classroom Episode 8: Upgrade Internals and so much more

You see the agenda in the picture above. We will cover not only internals but also diagnosability, monitoring, troubleshooting, tipps, tricks, secrets, workarounds, gothas, dos and don’ts – …

ORA-1555 won’t get reported into alert.log anymore since 19.4.0

Posted on September 10, 2020 by Mike.Dietrich Behavior Change 8

Many thanks to a German customer for showing me this tiny behavior change with Oracle Database RU 19.4.0. From this RU on the well known ORA-1555 won’t get reported into alert.log anymore since 19.4.0. But if you still like to see the “snapshot too old” error, then you can use a workaround.

ORA-1555 won't get reported into alert.log anymore since 19.4.0

Photo by Dariusz Sankowski on Unsplash

Why has this been changed?

Actually this is something I don’t understand completely. It may be just a side effect. Unpublished fix bug 29424999 – DUMP MINIMAL DIAGNOSTICS BY DEFAULT IN CASE OF ORA-01555 IN ADW/ATP ENV has been …

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 …

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 Catalog Upgrade fails – ORA-02296 – error creating modify_ts_pdbinc_key_not_null

Posted on April 19, 2016 by Mike.Dietrich Flaws and Pitfalls RMAN 4

This issue got raised to my via a customer I know for quite a while – all credits go to Andy Kielhorn for digging down into that issue and solving it.

Failed RMAN Catalog Upgrade from 11.2.0.4 to 12.1.0.2

The RMAN catalog upgrade:

SQL> @?/rdbms/admin/dbmsrmansys.sql

$ rman CATALOG rman/xxx@rman01

RMAN> UPGRADE CATALOG; 

RMAN> UPGRADE CATALOG;

failed with the following sequence of error messages:

error creating modify_ts_pdbinc_key_not_null
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06004: ORACLE error from recovery catalog database: ORA-02296: cannot enable (RMAN.) - null values found

error creating modify_tsatt_pdbinc_key_not_null
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR

GC Freelist Session Waits causing slowness and hangs

Posted on March 22, 2016 by Mike.Dietrich Behavior Change Flaws and Pitfalls Oracle Database 12c Parameters Patch Recommendation 0

One of the best things in my job:
I learn from you folks out there. Everyday.

Credits here go to Maciej Tokar who did explain the below topic to me via LinkedIn – thanks a lot, Maciej!

Locks are not being closed fast enough, resulting in gc freelist waits

You can find a reference for Global Cache Freelist in the Oracle Documentation. This issue here can or will lead to database being slow, up to complete hangs. Based on my research it looks as the issue is not related to RAC only but a general thing. In your session …

Parameter Recommendations for Oracle Database 12c – Part II

Posted on March 8, 2016 by Mike.Dietrich Behavior Change Oracle Database 12c Parameters Patch Recommendation 6

Preface

Again, please be advised – the following parameter list is mostly based on personal experience only. Some of them are officially recommended by Oracle

Workaround

ORA-12850 when you run AutoUpgrade?

What is the problem?

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

What is the symptom?

Upgrading a PDB with JVM may result in ORA-7445 joevm_invokevirtual

What

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

What’s the problem?

AutoUpgrade may run into a timeout when GI is lower than 19.10.0

Oracle 19c on Windows may flood your trace file directory

What happens?

Workaround for sdoloadj.sql errors with Datapatch in 19.9.0 and 19.10.0

What happens?

Virtual Classroom Episode 8: Upgrade Internals and so much more

Everything You Always Wanted to Know About Upgrades (But Were Afraid to Ask)

ORA-1555 won’t get reported into alert.log anymore since 19.4.0

Why has this been changed?

AutoUpgrade and the Partial Offline Backup Strategy

Partial Offline Backup Strategy?

AutoUpgrade may fail when patch ID column is NULL

What is happening?

RMAN Catalog Upgrade fails – ORA-02296 – error creating modify_ts_pdbinc_key_not_null

Failed RMAN Catalog Upgrade from 11.2.0.4 to 12.1.0.2

GC Freelist Session Waits causing slowness and hangs

Locks are not being closed fast enough, resulting in gc freelist waits

Parameter Recommendations for Oracle Database 12c – Part II

Preface

Archives

Categories

Upgrade @YouTube

RSS Feed for Upgrade your Database – NOW!

Subscribe via Email

Recent Posts