Posts Categorized: Technical Blog
A few days ago, we faced an interesting problem on one of our customer’s slave mysqld servers. An Alter for adding a new column was run on master server took 542 seconds where as it took few hours on the slave server to complete due to a SELECT blocking the Alter was not allowed to complete. What happened in this situation was: ALTER started first, then concurrent SELECT started on the same table, when ALTER finished copy to a temp table it tried to RENAME table, but failed to get global lock on data dictionary. All the threads that started after this point had to wait on ALTER to finish.
Backup jobs can be scheduled in many different ways (crontab, Grid Control, Scheduled Tasks, etc) and finding the log file may be tricky if you don’t know the environment well. Furthermore, log files may also have already been overwritten by the next backup or simply just deleted. An alternative way of accessing that information, thus, may come handy. Fortunately, RMAN keeps the backup metadata around for some time and it can be accessed through the database’s V$ views. Obviously, if you need this information because your database just crashed and needs to be restored, the method described here is useless.
Pythian’s Oracle ACE, Fahd Mirza appears in this month’s Community: Peer-to-Peer review “In With the New”, as published in the September/October 2011 issue of Oracle Magazine. Fahd states that “Oracle Exadata Database Machine” has most changed his life – changing the game, and setting very high standards of performance, support, scalability, reliability and unification. Shout out to Fahd from your peers at Pythian!
t’s a busy summer at Pythian, with our continuing wave of speaking sessions at upcoming community and regional industry events. Coming to a city near you, watch for Pythian presenting hot Oracle and Microsoft SQL Server database topics.
Just a few days ago I received a reminder email from Burke Scheld for the “AUSOUG National Conference Series – Perth 2011 – Call for Papers”. I had an event-related conversation with several Oracle guys in my professional networks and the answers I received triggered this blog post. Some of the very good Oracle professionals I personally respect said “…I am not sure what I would get out of it …” or “…I haven’t done anything exciting for the last FEW MONTHS …”. The answers I received shocked me a bit.
On many of our clients, we have a need to run XtraBackup as a regular OS user. Aside from running into the issue where tar4ibd was not provided with Percona’s xtrabackup-1.6.2.tar.gz package, our main issues have been with permissions when attempting a streaming backup. Here is the innobackupex command that works for us.
We have incident reporting procedures at Pythian. This incident report was sent just recently internally at Pythian. We learned some good lessons from it so I hope it would be useful to the community as well – As part of our incident management process, you will find below a summary of the details from the incident that occurred on July 29th at 3PM EDT. Overview: Pythian employees were de-motivated by the lack of refreshments on Friday afternoon
I already aluded to the fact in a few posts already, but just to make it a wee bit more public: a few weeks ago, someone had a lapse of common sense and knighted me Maintainer of DBD::Oracle. mouahahaha *ahem* I mean, I’m honored to be allowed to at the wheel of what is one of the most venerable battleships of the CPAN armada, and hereby swear to serve her at the best of my abilities.
I’m following up on a conference almost half a year later — try to bet that! Actually, this blog post was written more than 3 months ago and was sitting in my drafts waiting the moment I understand why I really wrote it. 3 months later… I still don’t know but I thought I should share it anyway. Maybe I could at least get some comments…
There has been quite a bit written about Oracle Mix Voting (let me refer to it as OMV for short) this year and I don’t think I should waste your time restating any of this. What I wanted to do is to take a step back and try to list “stakeholders” of OMV.