Boys and girls, please make yourself comfortable. Sit back, clip your seatbelt, and relax as we ready ourselves to take the scenic route to YAPC. I’ll try to stick to a semi-chronological order, which means that I will begin at the beginning. Maybe not the beginning beginning — my youth was a fairly uneventful and boring one — but a beginning that provides both scope and a springboard to this odyssey.
An ideal summer day is when the sun is shining, the warm sunshine refreshes your body, the light breeze becomes naught with your hair, the birds sitting on intoxicated leaves smile at you, and you to top all of that you get the latest hot issue of the Log Buffer. Yes to put cherry on your cake, Log Buffer #227 is here.
In your hands, the new edition of Log Buffer is smiling and it wants your undivided attention, because it is full of selected simmering yet cool blog posts from around the blogistan of database arena. Enjoy the Log Buffer #226.
I’ve been so amazed by the community response to my requests over the past few days that I just HAD to blog about it. In this post I’ll cover Oracle MIX and Suggest-a-Session voting, my very first experience and approach to the event, and special thanks to those who showed their support.
Are you considering Oracle Exadata as a data warehousing or consolidation solution for your organization? Before you go any further, be sure to join Alex Gorbachev, Oracle ACE Director & Pythian CTO at noon tomorrow (EST) as he outlines where Oracle Exadata is the best fit.
I was reading my session evaluation results and came accross comment that said: “copy and paste coder.” I’ve been doing this specific presentation for almost 5 years now with a few tweaks every once in a while based on feedback. Yes, I live and breathe disaster recovery as part of my day-to-day job. However, there are several reasons why I do not type nor write code during my presentations. Here are a few of them.
In this follow up post: I’m going to provide notes and diagrams as well as answer questions from my web cast on Oracle 11G SCAN – RAC SIG. Let’s get into it….
March of bloggers goes on and so is the unstoppable production of the blog posts. It’s getting more exciting week after week watching the new and old bloggers adding spice to the database blogosphere. This edition of Log Buffer brings some of the simmering and scintillating posts from around the globe in Log Buffer #225.
While trying to move a schema from one MySQL server to another, I encountered a very odd issue. The schema to be moved contained both MyISAM and InnoDB tables, so the only option I had was to dump the schema using mysqldump on the source server and import it on the destination server. I did some digging and found that the problem was that the MyISAM engine silently changed the table definition without any indications. Here are some solutions.
No, this isn’t a re-post of my earlier blog about bug 1233183.1. We’ve found a fun new bug that seems to be specific to our poor standalone ASM instances when upgrading from Oracle Grid Infrastructure 188.8.131.52 to 184.108.40.206.