Video : JSON_OBJECT Function Enhancements in Oracle Database 19c

Today’s video is a demonstration of some of the enhancements to the JSON_OBJECT function in Oracle Database 19c.

If videos aren’t your thing, you can get the same information, and more, from this article.

The star of today’s video is Patrick Jolliffe. πŸ™‚

Cheers

Tim…

Video : SQL/JSON : Generate JSON from SQL

Today’s video is a quick run through some of the SQL/JSON functionality introduced in Oracle database 12.2.

For those people that want a lot more information, including copy/paste examples, check out the article it’s based upon, and all the other JSON stuff I’ve written here.

The star of today’s video is Roel Hartman of APEX fame!

Cheers

Tim…

Oracle Database 19c : Installations, RAC, Data Guard and Upgrades

I’ve been playing around with Oracle Database 19c on LiveSQL since it was upgraded, and I pretty much thought that would be what I was stuck with until the on-prem release, as I don’t have an Exadata and it’s not on Oracle Cloud DBCS yet. Having seen a bunch people doing stuff on VMs, I got a bit frustrated and looked on eDelivery and low and behold the 19c software is available for download, even if you don’t have a Exadata CSI. I’m sure 18c was restricted during this period…

I’m pretty sure you wouldn’t be supported to use this for anything real (that wasn’t Exadata of course) until the on-prem drop, which will probably be 19.3 if they repeat what happened for 18c, but it does allow you to have a play.

Having a bunch of Vagrant environments for 18c already, meant it was pretty easy to test a whole bunch of 19c stuff within a few minutes, as most of the basics are very similar. Just minor changes to package recommendations. As a result I’ve pushed out the following stuff in the last couple of evenings.

Along the way I’ve committed a whole bunch of stuff to GitHub.

  • Vagrant build of 19c on OL7 with APEX and ORDS (here).
  • Vagrant build of 19c on Fedora 29 (here).
  • Vagrant hands-off build of 19c RAC on OL7 (here).
  • Vagrant hands-off build of 19c Data Guard on OL7 (here).
  • Docker 19c on OL7 build (here).
  • Docker compose (here) and swarm (here) stacks.

It should be obvious, but remember this is literally the first time I’ve done this stuff with 19c, so things will change over time. I just wanted to try some stuff out to see what happened, and have some test environments to play with while I’m checking out the new features. Once the real on-prem drop happens I’ll bring these up to date.

If nothing else, this is once again proof of how awesome automation is. A few minor tweaks and boom, there’s a new set of test environments. πŸ™‚

Now I can get back to doing what I was meant to be doing… πŸ™‚

Cheers

Tim…

Video : Override External Table Parameters and Inline External Tables in Oracle Database

Today’s video gives a quick demonstration of overriding external table parameters and inline external tables introduced in Oracle database 12.2 and 18c respectively.

There is a more general video on external tables here.

For those of you that don’t do YouTube, you can read all the articles here.

The cameo on this video is Ilmar Kerm, in a really noisy bar. πŸ™‚

Cheers

Tim…

Video : Real-Time Materialized Views

Today’s video is a quick demo of Real-Time Materialized Views,
introduced in Oracle Database 12c Release 2 (12.2).

This is based on information from the following articles.

The cameo for today’s video is Maria Colgan. πŸ™‚

Cheers

Tim…

Video : Collation and Case-Insensitive Queries in Oracle Database

Today’s video is a run through the Collation functionality introduced in Oracle Database 12c Release 2 (12.2).

If videos aren’t your thing, you can find a lot more information about this subject in my article here.

The cameo in today’s video is Kim Berg Hansen. πŸ™‚

Cheers

Tim…

PS. Subscribe to my YouTube channel here.

Video : Extended Data Types in Oracle Database 12c Onward

Today’s video is a quick run through the Extended Data Types functionality introduced in Oracle Database 12c Release 1. Why such an old subject? Well, it’s a prerequisite for something I was planning to do a video on, so I thought I better do this first. πŸ™‚

For those that don’t like videos, you can find the same information and more here.

The cameo in today’s video is Martin Klier. πŸ™‚

Cheers

Tim…

PS. Subscribe to my YouTube channel here.

Pay to Present? I don’t think so!

There is some strong language and emotion here, and remember it’s just my opinion. Don’t read if you are easily offended!

Something interesting crossed my inbox last night. There was an email thread amongst a bunch of presenters about a policy of pay to present at Collaborate this year. I have, and never will present at Collaborate, as Apps is not really my scene, but I think anyone accepting this policy is helping to set a dangerous precedent and I would encourage them not to go. I know funding user group events is problematic, but NO!

Collaborate already do something that I personally think is quite scummy, which is to make you pay $200 extra if you don’t stay in an official event hotel. They’ve done this for a while. This year they are going a step further. If you work for an Oracle partner that isn’t exhibiting at the event, you have to pay to go to the event, even though you are speaking. It’s a reduced rate of $299, but you still have to pay. You can’t present more than one session unless your organisation is a member.

People go to conferences to watch presentations and get advice from presenters. If the presenters weren’t there, there would be no event! We are the commodity they are selling and we don’t get paid to speak. Some lucky people like me get to claim some of our expenses back from evangelist programs, but even then we lose money. I buy back extra holiday from work. Those working in consultancies lose consultancy money. My first two conferences of this year are fully funded by me. If someone were to then tell me, in addition to all the other expenses I incur, I had to pay to go to the event my reply would be something to the tune of, “Shove it up your arse and f*ck off while you’re doing it!”

“But it only affects people working for partners!” Loads of presenters work for partners. Not all partners are giant corporations.

“But think of all the free advertising partners are getting!” Newsflash! Most companies would rather you were working and earning them money than poncing around at a tech conference. Most companies aren’t getting loads of new leads as a result of you presenting at a tech conference. I think people outside the conference circuit have quite a skewed view of what it really is. On numerous occasions I’ve spoken to people about this, and letting their technical staff present is less about company profile and making money, and more about staff development and keeping them happy so they don’t leave and go somewhere else. Good staff come at a price, and not all of it is about wages.

“Times are hard for user groups!” Making the speakers you are relying on to make your event successful pay to attend is a scumbag move.

“But you don’t even go to this conference!” True, but if people start to see this as a revenue stream for their conference, others will follow. I honestly believe this is the thin end of the wedge!

“Why should you get the whole conference experience for free?” I understand this for someone that maybe presents once a year. You could see this as a free learning experience. Having said that, if you present a lot it gets increasingly hard to find something you’ve not seen several times already. Added to that, many presenters are still working during the events. Meetings with existing customers, or just going back to the hotel to do your day job between presentation commitments. It’s not like one long party! πŸ™‚ Update: Samuel Nitsche pointed out, even if you do one presentation a year, you still invest a lot of time to get ready for that, so you still deserve the free pass. I agree. As you say, at least for us we can use the same presentation multiple times, so the investment per event on preparation time is a little less.

“You’re a presenter. Of course you would say that!” I think most of my presenting days are behind me. What happens with user groups and the conference circuit is really of little concern to me personally, but how does this affect who comes next?

I know this might be hard for folks who see Collaborate as their main conference of the year, but I would suggest all speakers and attendees boycott this event unless they reverse this decision! It’s a slippery slope folks!

Just my opinion. You don’t have to agree!

Cheers

Tim…

Update : Some extra things coming out of the woodwork from private messages…

  • Two other reports of different user groups suggesting a pay to present model, then backing down when confronted.
  • Sponsor us, or you can’t present seems to be quite common.
  • Some speakers being paid to speak at regular user group events. I have heard this before, but I’ve never been paid. *
  • Some speakers getting travel expenses paid by the user group for regular user group events. I have been offered this a couple of times, but never taken it. One conference I go to pays the hotel bill for speakers, which is very welcome as I usually end up self funding that one. *

* I have no problem with a user group deciding to pay a speaker, or pay expenses, but I would be super-pissed if I had been asked to pay to present, then I found other speakers at the same event had been paid to be there. Screw that!

I’m telling you people. You’ve got to nip this thing in the bud!

MobaXterm 11.1

Looks likeΒ MobaXTerm 11.1Β was released about a week ago. I upgraded at work soon after release, but I just noticed I hadn’t upgraded at home, and I hadn’t mentioned it on the blog. πŸ™‚

The downloads and changelog are in the usual places.

If you are using a Windows PC or laptop and you spend a lot of the time using SSH, this is a great tool!

Cheers

Tim…

To upgrade or not to upgrade? That’s the question!

Saturday’s post about 19c generated a lot of feedback on a number of my social media networks. To generalise, you could probably split the responses into two camps.

Of course, this discussion applies equally to other technologies, including the middle tier and development frameworks. It can also be applied to people’s attitudes to patching, as well as to upgrades.

We don’t want to upgrade.

I totally get why people think this is a viable option. Such arguments might include:

  • Stability is more important than new features. With new versions come new bugs and new instabilities.
  • We don’t have time/resources to test our application against the new version.
  • The cost (in time and resources) of upgrading is not worth the pay-off of being at the new version. It’s cheaper to pay for extended support than upgrade.
  • The version we are using has all the features we need, so upgrading is a waste of time.
  • Our customers don’t care about new versions.
  • We do all our business logic in the middle tier, so the DB is just a bit bucket. New features are irrelevant.

We want to upgrade to the latest versions.

This is closer to my position, with a few important caveats.

  • You have to have time to learn the new version, so you can get the most out of it, and not fall foul of new features that do things you might not expect.
  • You need to test your application properly against it, to make sure the new version doesn’t break anything. This seems to be the biggest sticking point for companies that haven’t invested in automated testing. A lacklustre approach to testing your application will often result in a disastrous upgrade.

So why would you bother? This is where I do my totally biased sales pitch. πŸ™‚

New versions contain new features, some of which actually work. πŸ™‚ There are headline new features that are just marketing bumf and irrelevant to me, but there are also some really useful things, which make life easier for you and your company. Look what’s happened just for online operations in the last few versions. I know some of these features have saved loads of downtime for people.

I tend to think development new features drive change more than DBA new features, because they outwardly affect more people in the company. For people who do development in the database, the last few releases have included a lot of really useful things. Let’s look at just one of them that is dear to my heart.

If you know what is in the new releases and you don’t find anything compelling, then a choice to stay where you are is fine. We don’t all want the same things, and different opinions are fine. If you are just sticking with what you’ve got because you can’t be bothered to learn the new stuff, and you are content to do the same thing you’ve always done forever, I think you are selling yourself and your company short. Just my opinion though.

I’ve already declared my bias towards upgrades. Why? Because many of the problems I come across actually come from not staying up to date with versions and/or patches. The rest of the industry keeps moving, and somehow DBAs want to be totally static. I don’t understand that. Caution is good. Static is bad IMHO! πŸ™‚

Cheers

Tim…