APAC Groundbreakers: Cool Features not only for DBAs
Monday, Nov 29, 2021 – 10:00h CET
Yesterday at DOAG conference I announced it already in our Upgrade and Migration Round Table – and just a few hours later my team mates made the New AutoUpgrade version 20211115 (Nov 2021) available for download.
Just click on this link in the MOS Note:
A good number of issues being logged to us via blogs, tweets, SRs and eMails can be solved with the current …Continue reading...
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.
As I wrote before, the release you should upgrade to is clearly Oracle Database 19c. Unless you need to use one of the new features in Oracle 21c. But as you have seen in the past, some of them get backported to 19c as well. Still, in case you can’t resists or you love upgrades as much as we do, the question may be: Which releases allow you to upgrade to Oracle Database 21c?
The Database Upgrade Guide for Oracle 21c is your best friend here. Right at the beginning in the first chapter you will find this …Continue reading...
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.
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...
Yesterday I wrote about the installation of Oracle Database 21c on Linux. But today it is time for Upgrading to Oracle Database 21c with AutoUpgrade.
You may have heard it already from us and other colleagues, but we can’t repeat it often enough: There is only one recommended tool to upgrade your databases – and this is AutoUpgrade.
In my 21c home, I’m checking the deployed version of AutoUpgrade at first:
[CDB3] oracle@hol:/u01/app/oracle/product/21/rdbms/admin $ java -jar autoupgrade.jar -version build.hash 57ab246 build.version 21.1.3 build.date 2021/04/21 13:32:13 build.max_target_version 21 build.supported_target_versions 12.2,18,19,21 build.type production
Now please …Continue reading...
As we often tell you, our Upgrade Development team is working hard to ensure an agile release cycle for AutoUpgrade. And the New version of AutoUpgrade (21.2) is available for download.
As usual, you can (and should) always download the most recent version of AutoUpgrade from this MOS Note: 2485457.1. Usually the tool gets refreshed every 6-8 weeks. And the version you will download is guaranteed newer than the one you could get on disk.
The fact the tool has a 21c versioning does not affect 19c upgrades. There …Continue reading...
Many people on the northern hemisphere will escape during July into the summer holidays. But we won’t. Instead, thanks to Sai Penumuru, we will give seven webinars for the aioug. And we are looking forward to talk to you soon at the aioug Webinar Series July 2021: Database Upgrade and Migrations.
This morning I looked into my calendar. And I realized: Wow, July 2021 is just a few days away. Roy will start with the first session on Friday, July 2. And then myself, Rodrigo, Daniel, Fred and Bill will …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...
This will be a short but very important blog post for those of you with Exadata systems. Then you should Upgrade to Oracle 19c on Exadata with AutoUpgrade.
Until a week ago, the database upgrade MyOracle Support (MOS) note showed the process using the DBUA. And we had plenty of customers asking us why AutoUpgrade isn’t mentioned there. Our team worked already with some of you, and we knew that AutoUpgrade works perfectly fine and takes over some manual actions.
But our MAA team wanted a perfect solution. They …Continue reading...
When we launched AutoUpgrade, it could upgrade non-CDBs and CDBs with all PDBs. Soon after, it learned to upgrade a non-CDB and plug it into an existing CDB as a new PDB. And then, as next step, we added Unplug / Plug / Upgrade with AutoUpgrade. In this case you have a PDB (or hopefully more than one), and you’d like to upgrade one or many PDBs by moving them to a new CDB with a higher database version.
As test setup I use our Hands-On Lab.
I will …Continue reading...
Ernst Leber sent me an email today. He hit an error at a customer upgrading to Oracle 19.9.0 on Exadata with AutoUpgrade. ORA-1422 and ORA-6512 from SYS.DBMS_STATS in Post Upgrade were signaled – and he better flashed back to the Guaranteed Restore Point. He found even a MOS note but still had questions. So time to blog about it in case you hit this error sequence as well.
At first, this is not an AutoUpgrade issue. You may see the same error stack in the post upgrade …Continue reading...
I know, I didn’t blog for a while due to seminar preparations and holidays. But as I’m going through the open comments on the blog trying to answer them, I came across a question regarding the strange UPG error codes, AutoUpgrade is printing sometimes. And of course, where are AutoUpgrade error codes documented?
Once AutoUpgrade hits an error condition, it prints an error code such as UPG-1400 or UPG-1303. And often, this error code is not very meaningful. In the comments section, somebody asked where to fine more information about these …Continue reading...
If you haven’t signed up, there are less than 48 hours left to sign up now to our Virtual Classroom Series – Episode 2: Database Upgrade on Feb 18. We’ll cover everything you need to know for a smooth and successful database upgrade to Oracle 19c.
What else? Haha!
No worries. We have a lot of fresh content and a full agenda. Our focus is to equip you with everything you need to know about upgrades – to make your next upgrade(s) the smoothest upgrade experience ever. We will cover mostly AutoUpgrade but …Continue reading...
for Feb 10, 2021 – 10:00h CET
Virtual Classroom Web Seminar No.8:
Database Upgrade Internals – and so much more
Do you want to speed up your database upgrades? Did you ever ask yourself what AutoUpgrade does in the background? And do you want to know what all the logfiles are meant for? Or how you monitor 20 database upgrades with one simple call? In this webinar, we’ll not only cover database upgrade internals—we want to deliver real insights. We’ve invited Frederick Alvaraz from the AutoUpgrade development team to join us and share his expertise.
In addition, …Continue reading...
It’s out now and available since yesterday: AutoUpgrade 21c. Download the newest AutoUpgrade for 19c and 21c upgrades with many new features and improvements.
This is the current version of AutoUpgrade:
build.hash 8ee6880 build.version 21.1.1 build.date 2020/12/14 14:41:34 build.max_target_version 21 build.supported_target_versions 12.2,18,19,21 build.type production 48 bug fixes since v21.0.0 release Tag: v21.1.1 Description: This is the release for 21.1.1 MOS only
As usual, download it please from:
Derzeit keine Unterlagen zum Download verfügbar.
Oracle Database 21c should be out soon – but have you upgraded to Oracle 19c yet? And should you upgrade to Oracle 21c? That’s one of the many question you’ll get an answer for in this 45 min talk. I will demonstrate the upgrade to Oracle 19c and 21c – and highlight important differences and things
The October 2020 Version of AutoUpgrade is available now for download since Friday last week. As usual, you can access it easily via MOS Note: 2485457.1 – AutoUpgrade Tool.
As usual you find the change.log at the end of MOS Note: 2485457.1 – AutoUpgrade Tool for the most recent Oracle Database upgrade tool. You will find the following fixes and enhancements:
This may become a longer blog post. One of the customers I work with for many years contacted me a few weeks ago. After upgrade to 19c, it looked like as if some Unified Auditing Policies weren’t correct anymore. It started as a tiny issue, but thanks to the customer who analyzed down to the bones, it seems to be bigger than we thought at the beginning. So you may Check your Unified Auditing Policies after upgrading to Oracle 19c as well.
Actually a lot of my customers use Unified Auditing these …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
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...
In my previous blog post I demonstrated how you can upgrade with AutoUpgrade between two servers. This a very typical scenario where you get new server, often also with a newer operating system version installed. But I was wondering if you can use Oracle AutoUpgrade between two servers – and Plugin?
Please see my previous blog post about all the details:
At the end of it, I was curious if I couldn’t just plugin afterwards. But I …Continue reading...
I try to catch up with missing AutoUpgrade posts. And I should have written this one a while earlier ideally. Just yesterday a colleague asked me about it. So it’s time now to describe how to use Oracle AutoUpgrade between two servers.
The Oracle Database 19c Upgrade Guide has this section about the scenario:
And you see that it consists of 5 steps:
I encountered this issue now multiple times in my own environment. And I searched MOS and tried different things. But I couldn’t solve it yet. My Upgrade fails with ORA-20001 during datapatch run – and I’d like to show you how to bring the upgrade to an successful end.
In my lab environment I upgrade two databases often in parallel. An 126.96.36.199 database and a 188.8.131.52. The 184.108.40.206 upgrades always flawless. But the 220.127.116.11 occasionally fails. This is the screen AutoUpgrade is showing me – but this is not …Continue reading...