I’ve rewritten this blog post in the series to include other new features in SQL Server 2012 outside of high availability and disaster recovery. Ever since the product has been released, I’ve had a chance to look at features that will address performance challenges and business intelligence requirements.
We’ve got 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 but, as with any new release of anything, there are still quite a few bugs to be fixed. Last week, after working with Oracle on some of these bugs, they asked us 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.
Here is the latest MySQL news.
The Ottawa Oracle User Group (OOUG) were kind enough to invite me to give a whole morning full of presentation.
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 188.8.131.52 running on Linux. This is a excerpt of system calls being executed during a session waiting for a lock:
This is just a very short blog entry to inform folks that there is an open discussion group over at LinkedIn for SLOB topics of interest. The group can be accessed through the following link
The actual challenge calls for a more generic solution than originally described in the magazine. Because there is no glory in half-solving a problem, I had to come back to it. And because the Great Karmic Balance could probably use it, I thought I could take advance of the broader scope to produces a solution more geared toward elegance and modernism.
Update 13-June-2012: it has come to my attention that the numbers from the original source may have been incorrect or improperly released. To avoid confusion and potentially misleading information, the original content of this blog post has been removed.
The first MySQL/MariaDB/NoSQL Latin America event is on its way and Pythian will have a MySQL guy there. Yes, Francisco Bordenave is going to be one of the speakers. I am presenting a conference about Replication in MySQL, how to’s and what’s new in newer versions. This is a very important event and many of our friends will be there.
I was on an Exadata environment with four RAC instances, when a fellow DBA created an incident package. No big deal, except part of the adrci packaging procedure was to take a backup of the controlfile and include it in the incident package. Though the package was created successfully, the controlfile never made it.