My very first words on Oracle Database 12c Release 184.108.40.206 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 220.127.116.11, 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!
This is an almighty long post, because it walks you step-by-step through the setup of Pluggable Database as a Service (PDBaaS) in Enterprise Manager 18.104.22.168 so there are a lot of screenshots. The actual setup doesn’t take long at all, so don’t be put off by the length of the post. Just as a bit of enticement, there is also a way this can be done without going through the process I outline below, but you will need to understand this process first. So persevere with this, and I’ll reward you with another separate post of how this can done more simply!
If only I could do the following…(but it seems that it isn’t supported yet)… That is…based on the first “Loading XML documents into an Oracle...
Very often people want to load XML documents into an Oracle database so, for example, they can shred the needed values from those XML documents...
The SLOB code that is generally available here differs significantly from what I often test with in labs. Recently I was contorting SLOB to hammer an EMC XtremIO All-Flash Array in a rather interesting way. Those of you in the ranks of the hundreds of SLOB experts out there will notice two things quickly in the following AWR snippet:
1) Physical single block reads are being timed by the Oracle wait interface at 601 microseconds (3604/5995141 == .000601) and this is, naturally for SLOB, the top wait event.
2) Disk file operations I/O is ranking as a top 5 timed event. This is not typical for SLOB.