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.
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.
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 …Continue reading...
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 …Continue reading...
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.
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 …Continue reading...
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.
Take …Continue reading...
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)
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 – …Continue reading...
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.
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 …Continue reading...
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
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:
with graphics included. In brief, you take …Continue reading...
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
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 …Continue reading...
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 22.214.171.124 to 126.96.36.199
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… Continue reading...
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 …Continue reading...
Time for a new round on Parameter Recommendations for Oracle Database 188.8.131.52. The focus of this blog post settles on very well known parameters with interesting behavior. This can be a behavior change or simply something we’d like to point out. And even if you still work on Oracle Database 11g some of the below recommendations may apply to your environment as well.
Again, please be advised – the following parameter list is mostly based on personal experience only. Some of them are officially recommended by Oracle