Failure

CDB upgrades – explaining catctl_options

When you upgrade your entire CDB with AutoUpgrade, there is a parameter which allows you some tuning or tweaking. And I often see some misunderstanding here. Therefore, for CDB upgrades – explaining catctl_options is my focus today.

CDB upgrades - explaining catctl_options

Photo by Arthur Mazi on Unsplash

 

catctl_options – what it is meant for

This AutoUpgrade config file parameter allows you to set specific settings, mostly for tuning, but also to override some defaults. In the documentation you will find the whole list of options. You can set it in your AutoUpgrade config file, e.g.:

upg1.catctl_options=-T

 

catctl_options in CDB upgrades

Here, …

Continue reading...

Datapatch return codes and helpful queries

The other week I was visiting a customer in Germany who had specific questions for datapatch. And luckily, Alejandro Diaz who is the Product Manager for Data Pump in our team has a history in datapatch.  He helped me with Datapatch return codes and helpful queries.

Datapatch return codes

Yes, datapatch generates various return codes you can use to verify the outcome in case you program or maintain an automation.

  • 0 for success
  • 1 for prereq failure
  • 2 for non-ignorable error during patch installation
  • 255 runtime error

I may …

Continue reading...

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.

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 
… Continue reading...

Windows Only: Upgrade to Oracle 18.10.0 fails with ORA-01722

Liron Amitzi reported this on his blog a few days ago already. And it is a very nasty tiny little issue happening with RUs where the second number of the release enters the two-digit-space, such as 18.10.0. At this point, on Windows Only: Upgrade to Oracle 18.10.0 fails with ORA-01722. This happens late in the upgrade phase.

What is the issue?

The problem here is a tiny little piece in %ORACLE_HOME\admin\catupstr.sql – a SUBSTR function is used in a way that it does not take into account a potential two-digit …

Continue reading...

OJVM datapatch fails with ORA-29532 – but the root cause is noncdb_to_pdb.sql

Kudos to Robert Ortel who brought this nice misbehavior to my attention. And even though it looks like this would be an OJVM issue, it is caused by noncdb_to_pdb,sql, the script which is used to convert a non-CDB to a PDB. When you apply an OJVM patch, OJVM datapatch fails with ORA-29532 – but the root cause is noncdb_to_pdb.sql.

OJVM datapatch fails with ORA-29532 - but the root cause is noncdb_to_pdb.sql

Photo by Alexandra Gorn on Unsplash

It’s a bit tricky

First things first. This is not a blog post to blame OJVM. The problem just happens because datapatch for an OJVM patch touches data in the dictionary which hasn’t …

Continue reading...

OPatch Alert: Be aware of cleanup issues – and the JDK version

This is just a quick alert blog post for Friday with an OPatch Alert: Be aware of cleanup issues – and the JDK version. And thanks to several people who either commented or mailed me directly and asked if I could alert others as well.

OPatch Alert: Be aware of cleanup issues - and the JDK version

Photo by Hugo Jehanne on Unsplash

OPatch cleanup issue

At first, you may have read earlier this week my article about patching my environments with the April 2020 bundle patches. For my patch activity, I’ve had to exchange my OPatch versions for 11.2.0.4, 12.2.0.1 and 19.7.0. And I guess, I would have had …

Continue reading...

Issue with 2k and 4k db_block_size – ORA-1450 when upgrading to Oracle 12.2.0.1

Recently we got alerted by a customer and a colleague from Italy about an issue with the upgrade from Oracle 12.1.0.x to Oracle 12.2.0.1 if – and only if – your database got created with 2k or 4k db block size.

Problem

If your database got created with 2k or 4k db block size, and you attempt an upgrade from any upgrade-supported Oracle version to Oracle Database 12.2.0.1 the upgrade – regardless of DBUA or catctl.pl – will fail with an ORA-1450: maximum key length (1478) exceeded.

Analysis

In the catupgrd0.log – regardless of using the DBUA or …

Continue reading...