Over the past days I exchanged several emails with a very important customer regarding Fixed Objects Stats gathering in relation to database upgrade. The customer found out that it takes very long in their environment – over an hour to be precise. Relaxing on the weekend helped me a bit. And this morning, it dawned me that I’ve had two similar cases before already. Plus I didn’t blog about it yet. Now it’s time to tell you a little but about Unified Auditing and the situation when Fixed Object Stats Gathering takes very long during upgrade …… Continue reading...
Daniel and I did Web Seminars this week. One of them was about the different migration strategies. We did talk a lot about Data Pump. One attendee mentioned that Data Pump Import does not work parallel into PDBs in Oracle 184.108.40.206 and Oracle 18c. We were skeptical, and today I tried out to check: Does Data Pump import only serially into PDBs?
Very simple test setup
For this test, I take a schema export from an 220.127.116.11 database in our Hands-On Lab, the TPCC user HammerORA uses in the UPGR database.…Continue reading...
The other day I received a question on Twitter regarding my experience with Oracle 18.104.22.168 on Linux 8. I first thought this may be an error. Why should Oracle 22.214.171.124 been certified on Linux 8. And I didn’t see anything internally about Oracle Database 126.96.36.199 certified on Oracle Linux 8 and RHEL8.
But it is true …
Thanks to Marian Bednar (Thanks a lot!!) who couldn’t find any information on my blog, now I know. Marian pointed me to the Release Notes Oracle Database 188.8.131.52. They’ve got updated in July 2020 already …Continue reading...
A long while ago I blogged about whether you should keep your patch versions between Grid Infrastructure and Databases Homes in synch, or not. And today, Daniel dropped me a note mentioning that this old blog post may need an update for 18c/19c. He’s right. And as I’ve had trouble finding my old blog post, I title this one a bit more obvious: Does your GI RU/RUR patch level has to match your database’s?
Before Oracle Database 18c
Since Oracle 18c we move from a 5-number release schema to a 3-number one. …Continue reading...
A few weeks ago, you read the announcement of the availability of Limited Error Correction Support for Oracle Database 184.108.40.206. But many of you had some questions right away. I could answer most of them easily. But it was clear to us that there was more information needed. Hence, we published more information for Oracle 220.127.116.11 – Clarification for Limited Error Correction Support.
What has been announced in April 2020?
Just a few weeks ago we announced the availability of Limited Error Correction Support for Oracle 18.104.22.168 after November 2020. You could find …Continue reading...
We are running the AutoUpgrade-for-RAC beta test since last week. And the first issue one customer encountered … is neither an AutoUpgrade nor a RAC issue. It has to do with APEX and SPATIAL, and missing grants. APEX is invalid after upgrading to 12.2 – ORA-20001
What is happening?
You are doing an upgrade to Oracle Database 22.214.171.124. And you receive a number of errors during the component validation phase.
19:04:14 SQL> EXECUTE dbms_registry_sys.validate_components; ...(19:04:15) Starting validate_apex for APEX_180100 ORA-20001: MISSING GRANT: grant execute on "MDSYS"."SDO_DIM_ARRAY" to APEX_180100 ORA-20001: MISSING GRANT: grant execute on… Continue reading...
This topic is included in our Multitenant slides for a long time. But whenever I want to point somebody to the blog post, I realize that it’s not on the blog yet. Actually I discussed this topic recently during a customer visit again. It’s time to put it on the blog. When you use Oracle Multitenant: Be aware of the silent COMPATIBLE change.
Mixed version environments
When you work with Oracle Multitenant, the sooner or later you will have mixed version environments. This may be CDBs with Oracle 126.96.36.199 or Oracle 188.8.131.52 together with …Continue reading...
Today Roy and I received a question from a colleague about the RELOCATE feature in Multitenant. And I’d like to shed some light and this topic a bit more. Upgrade PDBs with RELOCATE – How does it work?
RELOCATE and UPGRADE?
At first, it looks very promising to me. RELOCATE uses the HOT CLONE functionality of Multitenant but then relocates the PDB from one to another CDB. You need to fulfill a few important requirements, for instance:
- Local Undo must be enabled in both CDBs
- This limits the technique to at least Oracle
Internally we can use a Gold Image service at Oracle. I can download a zip with 19.6.0 included. But externally for you as customers, the download of 19.6.0 required that you download 19.3.0 at first, then apply 19.6.0 on top of it. But a day ago, a tweet by my Belgium friend Philippe Fierens caught my attention. Do we offer patched Gold Images already?
What is a Gold Image?
Since Oracle 18c, the installation routine has changed to the better. You download zip file containing the Gold Image, you create a directory and …Continue reading...
These are good new in case you plan to use Oracle Database 184.108.40.206 longer in production. Just last week we extended the Extended Support for Oracle Database 220.127.116.11 by one additional year.
Extended Support Extension for Oracle 18.104.22.168
Before, the Extended Support for Oracle 22.214.171.124 ended end of July 2021. Now you can purchase it until end of July 2022. For those of you who have it included in your contract anyway (for instance if you have a ULA or PULA), these are great news.
Please see:Continue reading...
I need to bring this blog post forward about AutoUpgrade and Data Guard, RAC, Restart and non-CDB to PDB. Initially I planned to write this a bit later. But some of you had questions or were wondering why AutoUpgrade hasn’t done certain tasks. Hence, I’d like to clarify what AutoUpgrade can do, what it can’t and what you’ll have to do at the moment.
I refer to the AutoUpgrade tool as of July 2019. In later versions, one or the other restriction may be lifted. I will blog about it then as well.
AutoUpgrade – Step-by-stepContinue reading...
Since last night, the new version of the AutoUpgrade utility is available. Please download the new July 2019 (20190715) AutoUpgrade and exchange your previous version in your destination
$ORACLE_HOME/rdbms/admin with this one.
Please download the tool from: MOS Note: 2485457.1 – AutoUpgrade Tool
When you copied the new tool, call it for a version check to make sure you are using the most recent one:
$ java -jar $OH19/rdbms/admin/autoupgrade.jar -version build.version 20190715 build.date 2019/07/15 12:45:48
Please notice that the tool allows you to upgrade to Oracle 126.96.36.199 and Oracle 18c as well:
The listed releases are the minimum …Continue reading...
In the previous blog posts you could read about how to create the configuration file, adjust it and tweak the init parameters for the AutoUpgrade tool. And then I described the different modes of it. In this blog post I’d like to give you some insights into AutoUpgrade: Where do you find all the logfiles?
AutoUpgrade – Step-by-step
- The new AutoUpgrade Utility – Download, documentation and supported versions
- Create and adjust the config file for AutoUpgrade
- Config file for AutoUpgrade – Advanced options
- Config file for AutoUpgrade – Tweaking init parameters
- AutoUpgrade: ANALYZE, FIXUPS, UPGRADE and DEPLOY modes
Most of you may have recognized the desupport of
UTL_FILE_DIR with Oracle Database 18c. Reason is mostly that
UTL_FILE_DIR opens a lot of possibilities to do insecure things. But this has another effect which may not be obvious to you. There’s a behavior change in Oracle 18c/19c: No symbolic links for Data Pump directories. Read further to learn more about it.
In Oracle Database 18c we announced the desupport of UTL_FILE_DIR initialization parameter. But as you can read as well in the Database Upgrade Guide, there’s this remark:
UTL_FILE Package Symbolic Link in Directory Paths Not Supported
In the previous blog posts I explained mainly how to create, alter and tweak the configuration file for the AutoUpgrade tool. By now you should have your config file set up and adjusted for your environment(s). Let me go a step further and explain the different processing modes of AutoUpgrade: ANALYZE, FIXUPS, UPGRADE and DEPLOY modes. Then you’ll have a precise idea what the tool is actually doing, and how it operates.
AutoUpgrade – Step-by-step
- The new AutoUpgrade Utility – Download, documentation and supported versions
- Create and adjust the config file for
In the previous blog posts I explained how to generate a sample config file for the AutoUpgrade tool and how to adjust it. Then I gave you an overview about the most important Advanced Options you may want or need to deal with when using the utility. And in the below blog post I would like to show you have you need to edit the Config file for AutoUpgrade – Tweaking init parameters is an important topic.
This is the forth post of a series of blog posts regarding the new AutoUpgrade tool. Please find all the other available …Continue reading...
Oracle Database 19c on premises is available – and one of the key features is the new AutoUpgrade utility. In the following days I will publish several blog posts explaining and showcasing the new AutoUpgrade.
What is the AutoUpgrade?
The Oracle Database AutoUpgrade utility is a new tiny little command line tool which allows you to upgrade your databases in an unattended way. I call it the Hands-Free Upgrade. The idea of the tool is to run the prechecks against multiple databases, fix 99% of the potential issues, set a restore point in case something goes wrong …Continue reading...
First of all, this blog post is not new. I blogged about this SCN topic a while ago already. But some of you seem to operate still older databases for various reasons. And even if you think that you are safe, double check for any older databases in your environments. You MUST patch 188.8.131.52 and 184.108.40.206 and older databases before June 23, 2019. And just to be clear: June 23, 2019 is going to happen in less than 4 months.
Who is NOT affected?
If you use the following Oracle database releases …Continue reading...
This question sounds very simple: How long will Oracle Database 12.2 be supported? Right? But I learned at a customer site recently that the information about the support periods for Oracle 12.2 may puzzle people sometimes. Hence I thought some clarification may be useful.
Lifetime Support Policy Brochure
First of all, when you have a look into the Lifetime Support Policy brochure the answer you’ll read there is:
- Premier Support until March 2023
- Extended Support until March 2026
But this doesn’t give you any distinction between Oracle 220.127.116.11, Oracle 18c and Oracle 19c. These three releases fall under the Oracle …Continue reading...
Wait a bit. Oracle Database 19c is not out yet (only in beta right now) but how can we initiate a Premier Support Extension for Oracle 19c already? Well, Oracle 18.104.22.168, Oracle 18c and Oracle 19c all together sail under the cover of the “Oracle 12.2 Release Family” and hence have a common support frame.
What has been announced?
The single-source-of-truth MOS Note:742060.1 got updated. Roy tweeted about it already. And the major change in the note is the extension of the Premier Support for Oracle 19c until March 2023. That is one year more than it was …Continue reading...
A few weeks ago I published a blog post about provisioning dates in Oracle Cloud environments for different databases releases. As we did an important update, I rewrite today: How long can you provision database version X in the Cloud? – NEW.
What has changed since the original post?
The key point in the previous blog post was:
“And by end of this calendar year, the option to provision an Oracle 22.214.171.124 instance will go away. The same will happen in less than 1 year with Oracle 126.96.36.199 instances.”.
With “this calendar year” I pointed to end of 2018. …Continue reading...
Yesterday a former colleague from the UK pointed me to a very old blog post about the fact that no patches will be produced for Oracle 188.8.131.52 anymore. Which is a true fact. But it reminded me that it may be time for an overview on the current support status for Oracle database releases as of October 2018.
Current Support Status for Oracle Database ReleasesContinue reading...
Less than two weeks until the potentially busiest Oracle Open World conference I’ve ever attended. The schedule is filled up already and closed down. And I’m pretty sure I will need time off afterwards to relax and recover. But I’m looking forward to our annual big event in San Francisco. To make it as exciting as possible for you we are very happy to have high profile speakers with us in all our talks. And we promise: No marketing. Just tech facts. If you’d like to sneak into OOW 2018: Upgrade to 18c – Live and uncensored, then mark …Continue reading...
That’s a question I have gotten several times already: How long can you provision database version X in the Cloud? Meaning, is there a fixed date when you’ll be unable to provision an instance containing Oracle Database 184.108.40.206 for instance?
How long can you provision database version X in the Cloud?
Please find the updated blog post here:
Monday morning, another way-too-hot July day. Summer is crazy this year in Europe. We all enjoy nice sunny weather but nobody does enjoy a serious drought. Nowhere. While going through my inbox I spot this statement: ““Why should we go to 18.x with support till 2020?“. And this is not an unusual question. But I think I should write a Clarification: Support Periods for Oracle 220.127.116.11 and 18c. I receive plenty of such questions in the past weeks. And actually many from my colleagues.
Clarification: Support Periods for Oracle 18.104.22.168 and 18c
First of all, your Single …Continue reading...