The MySQL errorlog is an important point of reference when administering a MySQL Server. We can grasp much about the state of our MySQL instance by the informational and error messages written out to it by our MySQL daemon. I was asked to investigate some replication outage alerts a colleague had received overnight. One of the primary directions I took was the error log file. This is where I would expect find any evidence of replication being stopped or crashes etc. When I ran the command to tail the log I was shocked to see the log was totally empty.
A bit more than a week passed since most of us who been part of the OpenWorld are back from San Francisco. It is about time to start sharing stories on how it went for each of us. I must admit that it happened to be a very stressful OpenWorld for me personally. I am recovering from it slowly. On the positive side I met so many great people, discovered how supportive people are and how great is to be a part of the Pythian Team! Let’s talk about how my 2 presentations went at Oracle OpenWorld 2011.
This post was thought of as an attempt to make some performance test with new multi-threaded replication in 5.6, at least that was my initial intention. Based on Luis Soarez – Replication Team Leader in Oracle – post. I wanted to play with new set of variables and features in order to understand how new multi-threaded replication works and make some performance tests.
Pod::Weaver, which does to POD what Dist::Zilla does to distribution files, is all that, only moreso. But it feels so powerful, holds so much promises to make my life easier once I manage to master it, that I won’t let the steep learning curve deter me. I’ll climb down my brain bicycle, and push it up that hill. And I’ll provide a running (well, walking slowly) commentary as I go along, in the hope that it’ll help other peeps who might want to venture is those exciting yet dark waters. Okay. Enough preamble. Let’s get cracking.
The following story about DBA_JOBS_RUNNING and DBA_SCHEDULER_RUNNING_JOBS is based on real events.
‘m going to be presenting two of my OOW11 sessions at the Toronto Oracle User Group’s DD Day. I’m going to be presenting two sessions, Is Oracle Exadata for You? Starring Roles for the Best Technology, and Under the Hood of Oracle ASM: Failability Analysis.
World has opened up in San Fransisco with the database bangs. MySQL and Oracle databases have scintillated the hearts of developers, DBAs, technology aficionados, and the mere spectators. That and plethora of news has also poured in from SQLServer melas. This Log Buffer Edition is proud to shed spotlight on all these happenings in this Log Buffer #241.
Pythian’s presence at OOW each year permits this fine company, of which I have been a part for a total of close to 8 years, to get higher on Oracle’s and the industry in general’s radar. There are so many differentiators that separate Pythian from other companies. Take homes from OOW?
A few days ago I was asked to estimate how much space needed to be added to the ASM diskgroup to handle the database growth for one year without additional need of adding disks. To do this I needed to calculate acceleration and assuming the acceleration stays the same I would be able to calculate the “distance” or (how much the DB would grow in one year). I used the following formulas…
There has been some chatter at Oracle Open World (OOW) about the next release of the database. They will be calling it Oracle Database 12c (for Cloud) and it is expected in the 16-18 month timeframe from this version of OOW. Oracle has made no commitment to this time frame, but satiated the appetite of CORE database people by giving an update with no firm