I’ve often found that while I’m investigating one Oracle feature I get waylaid by noticing anomalies in other parts of the code. I was caught by one of these events a little while ago while experimenting with the new (220.127.116.11) Inmemory Columnar Store. After reading a posting by Martin Bach I asked the question:
“If you have a partitioned table with a local index and one of the table partitions has been declared INMEMORY, would a query that could use that index be able to apply table expansion to produce a plan that did a tablescan on the in-memory partition and an indexed access path on the partitions that weren’t in-memory?”
I have created a new youtube channel – and have uploaded some videos there already! Bookmark & Subscribe here:
More stuff is coming over the next weeks & months :-)
NB! If you want to move to the "New World" - and benefit from the awesomeness of Hadoop, without having to re-engineer your existing applications - check out Gluent, my new startup that will make history! ;-)
I headed on down to the conference and instantly saw a bunch of friendly faces, including lots of people I had met on the OTN Yathra 2014 Tour.
After the keynotes, I got to have a quick chat about User Groups with Mary Lou Dopart from Oracle, then it was off to my first session about database consolidation.
The taxi to the airport was good. The driver was interesting, speaking to me about his visits to India and Pakistan. It certainly helps pass the time when the driver is chatty.
Update: The first talk is now “Why use PL/SQL?” by Bryn Llewellyn.
This is the day after I get back from India, right after my first day back at work. It’s going to be really hard to drag myself there, but I know it will be worth it!
This article is about the Oracle 12c in-memory option, and specifically looks at how the background worker processes do IO to populate the in-memory column store.
Hardware: Apple Macbook with VMWare Fusion 7.1.3.
Operating system: Oracle Linux 6.7, kernel: 3.8.13-118.el6uek.x86_64.
Database version: Oracle 18.104.22.168
Patch: opatch lspatches
19392604;OCW PATCH SET UPDATE : 22.214.171.124.1 (19392604)
19303936;Database Patch Set Update : 126.96.36.199.1 (19303936)
But first things first, let’s setup the in-memory option first with a test table. The first thing to consider is to create the in-memory area to store the objects. I only want a single table stored in the in-memory area, so I can very simply look at the size of object:
This is a short post to help out any possible “googlers” looking for an answer to why their 188.8.131.52 EM Cloud Control install is failing in the make phase with ins_calypso.mk.
Note, this EM install was taking place on an Oracle Linux 7.1 host.
The following snippet shows the text that was displayed in the dialogue box when the error was hit:
VirtualBox 5.0.10 has been born.
There has been a bit of a discussion on Twitter today about the pros and cons of upgrading VirtualBox. I run VirtualBox on Windows 7 at work and Linux and Mac at home. Unless I’m travelling, I pretty much upgrade straight away. In recent history I only remember one time a patch has caused me problems and forced me to back it out. It seems other people on Twitter have had more issues than me.
I made the jump from VirtualBox 4 to 5 immediately and haven’t suffered at all.