It was inevitable that I would have to have a play with the In-Memory Column Store.
It’s just a functional look. I have no idea about performance at the moment, although I should be starting a proof of concept in the next couple of weeks for one of our internal systems, so it will be interesting to see how it holds up.
Another thing that has come out of this release is the Full Database Cache Mode. That’s nothing to do with the In-Memory Column Store, but I can definitely see us using this on some of our stuff!
So the AWR Warehouse patches are out, but documentation has not officially caught up to it yet, so as we appreciate your patience. I thought I would post about what I went over in my webinar last week when I had the wonderful opportunity to speak to the ODTUG members on this feature that everyone is so anxious to get their hands on.
Let’s start with some of the top questions:
It is indeed that sample as switching a knob to turn it on. To enable it you will have to set a reasonable among of...
My very first words on Oracle Database 12c Release 220.127.116.11 can be summed up in a single quotable quote:
This release is hugely important.
I’ve received a lot of email from folks asking me to comment on the freshly released In-Memory Database Option. These words are so overused. This post, however, is about much more than word games. Please read on…
When querying the dba_feature_usage_statistics view the option is known as “In-Memory Column Store.” On the other hand, I’ve read a paper on oracle.com that refers to it as the “In-Memory Option” as per this screen shot:
Schema as a Service provides database consolidation by allowing administrators to host multiple application schemas within a single database. This offers Database as a Service to possibly hundreds of application users without creating database sprawl. Users can perform day-to-day actions like provisioning, monitoring, and backup, all from a single Self Service console. Schema as a Service leverages database features like Resource Manager and Database Vault to isolate users of the cloud. This is complemented by metering and showback / chargeback capabilities, which provide visibility and transparency into resource consumption by each user.
Schema as a Service can be used to provide profiles and service templates for both an empty schema service and a schema service with seed data. In each case, the Cloud Infrastructure setup is very similar to the PDBaaS model. Typically, these steps are done only once and consist of:
With all the excitement around the release of Oracle Database 12.1.02, it’s easy to forget that there is other stuff going on as well.
Just remember, it takes quite a while to get products certified on this stuff, so although I’ve already tried installations on the beta versions, I would not install any Oracle products on this stuff “for real” until the official certification is announced for each product.
The world around us is changing and new stuff in the Oracle database arena is nowadays released on patch level. Although not many new features...
I assume it will be available from MOS also at some point.
PS. It will allegedly be made available on OTN at some point in the future.
Following on from my earlier blog post on setting up Pluggable Database as a Service (PDBaaS) in EM 18.104.22.168, this post will cover how you actually use the Self Service Portal to create on demand an empty pluggable database within the container database I created for that earlier post. You’ll no doubt be pleased to know that this post is much shorter!