Today’s video is a demonstration of the JSON_EQUAL condition introduced in Oracle 18c.
If videos aren’t your thing, you can read about it here.
The star of today’s video is Patrick Hurley, being a little over-dramatic. 🙂
I woke up at 02:00. I tried to got back to sleep, but by a little after 03:00 I gave up and got out of bed. I hit the gym for a while, but felt pretty dreadful.
I mentioned yesterday, I had helped some people with setting up Oracle Cloud. Since I was awake I grabbed some screen shots and wrote a couple of small posts so I could forward them to one of the folks, so they could remember what we did. These along with a couple of other posts I released a few days ago pretty much show how we set up a demo environment in a few minutes..
Pretty soon it was time to go down to the Oracle ACE Director Briefing…
Like yesterday, the meeting was covered by a Non-Disclosure Agreement (NDA), so there isn’t really anything I can say about it, but during the briefing we were told Oracle Database 18c Express Edition (XE) had been released for download. I had previously done an 18c RPM installation on Vagrant, so it was pretty simple to modify it to do the XE installation in a similar way and leave it going while I was watching the sessions. Yay! Go automation! 🙂
I did my thing of not eating again, so I could stay awake during the meeting. By the end of the last session I felt pretty hungry, so I picked up a bag of cheese flavoured popcorn and downed that before heading to Chipotle (again). I think I’m done with Chipotle now. My vegetarian burrito had a huge chunk of meat in it, which I bit into and spat out. If it had been at the start of I would have demanded a new one, but as I had nearly finished I just walked up to the counter and said, “This is a vegetarian burrito and that is meat. Sort yourself out!”, then left in a bad mood.
I got back to the hotel and had about an hour before 19:00, when I was meant to go and meet people at some place about a block down the road. I made the fatal mistake of lying on the bed to watch TV for a bit, and waking up at 04:00 the next day. Sorry folks! 🙁 The fact I slept for about 10 hours, which is extremely rare for me, kind-of shows you were I was at by this point. 🙂
So that’s the first two days of briefings done. Tomorrow (today by the time you read this) is a “day off”, but I do have an event in the middle of the day and a dinner in the evening. I’ve also got to go through my three (and a bit) talks, because once the conference starts, there’s no telling when I will get time…
PS. I was forced to “disappear” Maria Colgan from the family because she came into the room and didn’t come immediately to say hello to me. If she is really good, and I don’t replace her with someone else, she may be allowed back into the family at some point in the future… 🙂
I wanted to try something with Oracle 18c Data Guard, so I thought I might as well create a hands-off build of it using VirtualBox and Vagrant, much as I did with my recent hands-off RAC build.
I did the 18c build and figured I might as well do 12cR2 and 12cR1 builds too, as they were pretty similar. I could have done them as a single build with a few tweaks to sort out the differences, but I couldn’t be bothered. 🙂
Along the way I noticed I hadn’t done a 12cR2 data guard article, so I did these.
Just a quick heads-up to let you know I’ve updated my Docker builds to use the new 18c on-prem software.
If you like to play around with Docker, here is some stuff you might want to check out. Remember, I’m not saying this is production ready. It’s just stuff I use for learning and demos…
Remember, if Docker is not your thing, you can always my Vagrant build here to fire up the same thing, but in a single VirtualBox VM.
Hot on the release of Oracle Database 18.3.0 On-Prem for Linux, I got on the case with doing some installations. The first of which can be found here.
I few things to point out about these…
First, I’ve gone with a read-write Oracle home. I like the idea of the read-only home, but I’ve not played around with it enough at this point to commit.
The other thing is the Oracle home path itself. Currently I’m using “18.0.0”, rather than “18.3.0”. This feels a little strange to me, but I’m not sure how the Release Updates (RUs) will work out for this. I’m guessing what I’ll end up doing is creating a new Oracle home when a RU drops, then switch across to it, so it would be more appropriate to use 18.3.0, with a switch to 18.4.0 later. I’m still trying to decide how I want to play this. If you look at the SQL*Plus banner you will see this.
Connected to: Oracle Database 18c Enterprise Edition Release 188.8.131.52.0 - Production Version 184.108.40.206.0
So neither of these choices feel bad. 🙂
I usually post pictures of the installer, but I think this is sending the wrong message. IMHO you shouldn’t be installing this way, so this time I’ve made the break and only posted the silent installation.
I’ve got a couple more things in the pipeline, which will probably come out tonight. We shall see.
I was just about to go to bed when I saw this post by Mike Dietrich. Yay!
I’ve had access to 18c on the Oracle Cloud for some time, so I’ve already been able to write a bunch of stuff about it (see here), but it always feels geekier when it’s running on your own kit. It also makes demos a little less dangerous if you can fall back to your own machine. 🙂
Of course I’m starting the downloads now, so maybe I’ll get to have a play tomorrow? 🙂 If you want it you can grab it from here.
Every time a new database version is released a group of people, myself included, start pushing out content about it. I can guarantee you one thing about all these people. None of them are experts at Oracle 18c! There isn’t a single expert at 18c on the planet. Not even in Oracle. To be honest, I would say there are very few people who could really call themselves experts at 12cR2 at this point. Why? Because it takes time to get good at stuff and even 12cR2 hasn’t been out that long. It’s about 1 year since it was released for use on-prem (see announcement). Yes, it was around on cloud for a while before then, but most folks have had 12cR2 for 1 year and that’s it. Most people writing about 18c have had it for a few days tops. 🙂
So you’ve got one year of experience at 12cR2 right? I’m not so sure. You see you’re probably spending a lot of time working on 11gR2 and/or 12cR1 instances, as well as the odd 12cR2 instance that has made if to production. Humans are pretty lazy, so you are probably still doing a lot of stuff “the old way”.
I mentioned on a recent mailing list conversation, my approach to a new version is as follows.
I’ve been doing this for a long time and this approach has served me well, but I still think it takes me a few years before I feel really confident with a new version.
I don’t think many of the good content producers throw around the term “expert” very often, but I think some of the people who follow can have unrealistic expectations when they look at content on the internet. Most people are writing about something new they are doing, so at the point they are writing it, they are far from being experts. If you’re lucky they will go back and revise that content when they learn more, but more often than not they don’t. As a result, you are often following the guidance of a first-time user. 🙂
So when you ask me to help you with your implementation of Data Guard between two 18c Exadata machines, you’ve got to realise how naive that question is. There will be lots of people and companies who will happily take your money to learn the new tech, but that’s probably the subject of another post… 🙂
I was looking through the list of deprecated and desupported features along with terminal releases in Oracle Database 18c and there were some surprises.
This won’t be a complete list, so I would advise you to check it out for yourself (starting here), because what is important for me may not be for you, and vice versa. In no particular order, and not taking it too seriously, here we go.
No time to worry about what they are getting rid of. There’s all the lovely new stuff you don’t understand yet. That’s really what you should be afraid of! 🙂
In a previous post I mentioned the release of 18c on Oracle Cloud and Engineered Systems. The only way you could get that on the Oracle Cloud at the time was if you were using an engineered system on the cloud. As a result us folks that don’t have pockets that deep were forced to get our 18c fix on LiveSQL.
You can now get Oracle Database 18c on the Oracle Database Cloud Service, the DBaaS offering, on Oracle Public Cloud (OPC), so you don’t have to have such deep pockets anymore. It also means you can probably get a free trial now.
I’ve fired one up and updated an old article (here) to have the latest screen shots.
PS. I’m not overly bothered about constantly updating screen shots for cloud service articles as they change so frequently, as do the names of the services from time to time. As long as the general message is OK, that’s good enough. If you try to stay on top of the quarterly roll out you would never get something new done. 🙂
Just in case you missed it, Oracle Database 18c was released on Friday. You can read the announcement in this post.
You might be a bit disappointed if you don’t have an Oracle Cloud account, or an engineered system. Not to worry. You can try Oracle Database 18c on Live SQL.
The documentation is already available. You should probably take a look at the new features doc.
Just a few things to manage your expectations.
In the old terms, Oracle Database 18c is a patchset for Oracle 12.2. For quite some time it’s been known Oracle have moved to a new release model for most products, including the database, with the version number now including the year and the quarter etc. How the version numbers now work is explained in MOS Doc ID 2285040.1. The release schedule for these database versions is shown in MOS Doc ID 742060.1.
So before you lose your mind about how few new features there are for a “6 number jump in version”, just think for a second! All this has been reported for months. Mike Dietrich first wrote about the new versioning system in August last year. Many of the announcements at OpenWorld 2017 mentioned 18c was 220.127.116.11 with a different name. None of this is a surprise if you’ve been following the news. 🙂
If you follow me you will have seen these posts.
I can’t believe I’m still seeing this confusion. What has been released in the Oracle 18c database, not the Autonomous Data Warehouse Cloud Service. The product that’s been released is a DBaaS release of 18c, so it’s pretty much what you will get to run on-prem. It’s not autonomous! Once again, none of this is a surprise if you’ve been following the news. 🙂
The debate about “cloud first” has been going on for some time. I wrote a couple of pieces about it in 2016.
I think the cloud first approach worked out well for 12.2. I don’t remember a release that has been this stable before the first patchset for ages. I think some of that is down to the fact it was released to the cloud first, and the first on-prem release contained a bunch of bug fixes found during that cloud first release.
Another gripe I’ve heard is we aren’t getting 18c until part way through the year, so we will probably get 18.2 or 18.3. By the time we get 18c, the 19c release will practically be due. 🙂 My thoughts on this are:
It couldn’t have come at a better time for me.
You may have noticed I’ve seemed a little quiet on the website front. In fact I’ve recently written 19 articles that are live on the site, but haven’t made it to the front page. Most of them are covering older subjects, or what I call backfill. Many of those articles are covering features that have been available since Oracle 8i, but still relevant now. Since they are not “new”, they’ve not been promoted to the front page of the website, and I’ve not pushed them out on social media. I like to stay in the habit of writing, even if I’m struggling to find things I care to write about. I’m not saying I’ve written everything there is to write about 12.2, but I’ve written about pretty much everything I care to write about at this point.
The new release should give me an opportunity to write about something I can promote without feeling stupid. 🙂