SLOB on steroids v0.1: Use it at your own risk. First of all, let me state that I’m falling in love with SLOB :).
Interval partitioning – this ability to create partitions on the fly was introduced in 11g. When the feature came out, there were several nasty bugs. One such particular “limitation” has to do with parallel group by on the partition key. If you want to see just that part, skip towards the end, but I think reading the whole post will offer some insight on how Oracle Parallel Query works.
First of all, if you are using NFS to store Oracle database data files, I strongly advise you to enable Oracle Direct NFS (DNFS) to access these files. However, if you are not using NFS, DNFS is probably not of interest to you, and you should stop reading here. But, if you want to set it up, let’s go!
A while ago, I was paged by a client having backup job failure. Doing my routine as usual, I started the investigation by looking at the job execution log. Connected to the box was a strange output. Here it is!
Sharing knowledge not only is beneficial to others, but also enhances one’s own knowledge and broadens the spectrum. Blogging is all about sharing and this Log Buffer Edition brings together some great blog posts from around the database arena.
Recently, I was upgrading a database from 18.104.22.168 to the current 22.214.171.124 version. The database was using ASM, but I should notify at the beginning that the configuration is for a Stand-Alone Server and not RAC. Basically, the first things to be done for this procedure are part of the following checklist…
A new trial version of DBD::Oracle has been churned out. This release is mostly about Martin J. Evans going all ninjawesome on minor bug fixes as well as paving the way for an upcoming refactoring/speed boost of ora_verbose. As usual, the new version will be soaked for at least 2 weeks before it will turn into its fit-for-general-consumption v1.46 incarnation. Testers, please give this baby a whirl. The full changelog follows for the curious-minded.
We have a few clients already using Enterprise Manager 12c Cloud Control. The interface and navigation have improved a lot from the 11g version in my opinion. However, as with any new release of anything, quite a few bugs still need to be fixed. After working with Oracle on some of these bugs last week, we were asked to apply the Bundle Patch 1 (BP1) to one of our clients’ installation. The first thing that I noticed when I started looking for information about BP1 was the amount of warnings from different people I found in MOS and around the internet.
The Ottawa Oracle User Group (OOUG) was kind enough to invite me to give presentations for a whole morning. The group was ultra engaged and asked a lot of good questions, so my usual 50-minute Big Data presentation ended up taking 100 minutes, and the rest of the content had to be squeezed a bit. I hope everyone had a good time!
So how is the actual “waiting on lock” implemented? How does session B, waiting for a transaction to commit started by session A, knows that the resource is free for use? To find out how it is implemented, I have traced Oracle foreground processes. I tried this on Oracle RDBMS 126.96.36.199 running on Linux. This is a excerpt of system calls being executed during a session waiting for a lock…