Migrate Oracle 12c non-cdb to pdb in Oracle 19c
It's been a long time from my last post, but again it's time to show you something interesting. In this article, I will show how to migrate a Non-Container Database to a Pluggable Database.
I will use Oracle 12c noncdb which will migrate to Oracle 19c PDB. For that purpose, I had to install Oracle 19c software with an empty container.
The installation of Oracle 19c doesn't have any specifics. So we can proceed with the main steps.
Security Issues after Patching Oracle BI Publisher 11.1.1.9.0
As all know, patching process is not a big deal in most of the cases, but sometimes it is like "pain in the ass". As soon as starting dealing with BI Publisher, I faced issues which want to share.
I have discovered that after patching the BIP, security losts its permissions. So, let's see how to fix it! :)
Redo is inconsistent with data block {ORA-00600: internal error code, arguments: [3020]}
Is it a bug or a feture? That's the question!
In this article, we will show how to copy and restore datafiles from Primary to Standby Database on ASM using RMAN.
"Same,same, but different!" It is the same day as yesterday, but not exactly.
Today, when I logged in and start working, I got an alert for my standby database that Standby Database is not in sync with the Primary Database.
Patching Oracle DB home with - Patch 26636295: COMBO OF OJVM COMPONENT 12.1.0.2.171017 DB PSU + DB BP 12.1.0.2.171017
It took me a lot of time to decide what to be my first post, because the Internet is full of information, cases and etc.
But I have decided to write about this case because I think that it would be good to have it here and share knowledge with you all.
This topic is about patching Oracle Database Home 12.1.0.2 with the below Combo:
Patch 26636295: COMBO OF OJVM COMPONENT 12.1.0.2.171017 DB PSU + DB BP 12.1.0.2.171017
With this Combo you can also patch GI Home, but in our case we are patching only Database Home. (For reference you could check the readme in MOS)
Let's start with the steps that should be followed in order to accomplish the task.
First of all, you have to change the Opatch version to 12.2.0.1.7 or later based on the readme from the patch and as a best practises
Also you should be aware that lower OPatch version may lead to conflicts during patching process and this is primary due to patch level changes in the OPatch version.