Posts by Alex Gorbachev
Oracle RAC SIG web cast presented by your humble servant. Don’t miss it today! You can register on the RAC SIG web-site. This is a longer than usual session (90 minutes) packed with details of connection failover, load balancing and implementation details.
Long story short — I’m moving to Australia. My flight from Ottawa leaves in three hours and I’m all packed and ready to go. Today we had a kiss-goodbye lunch at here at the Pythian office in Ottawa, and I was presented my new role Down Under. Hmm . . . to be honest, I expected it to be somewhat different….
I’d like to share some great news — The Pythian Group and Open Query have become partners! Open Query is a leading provider of high-quality MySQL, PostgreSQL and related training in Australia and New Zealand. They offer consulting services too, and are also known for their MySQL Graph Storage Engine. Feel free to browse through Open Query web-site for more info.
If a MySQL DBA from Pythian goes to Oracle Open World, it would be a shame not to send an Oracle bloke, so there I am — presenting a 90-minute session on the first day of the OOW 08 entitled Under the Hood of Oracle Clusterware. I gave it during RAC Attack in Chicago and I’m pretty satisfied with how it went, so there should be no significant changes to the presentation. The session is in “User Group Forum,” thanks to RAC SIG and Dan Norris.
Interesting results you can see from some low quality news aggregators Looking at this page you might think that I’m awarded with the Liberty Medal. I’ve got this link while browsing the search results for RAC Attack. I guess should ask my granddad to pass my best wishes to Mr. George H.W. Bush.
Last night, I left my presentation in a good state and verified the first batch of demos — all worked fine. This morning turned into a disaster as I found out that the rest of my demos stopped working. Well, I didn’t have any other choice but to add new slides with some demo results. Since I did it in a rush, there were some overlaps and I ended up with way too many slides. Good news that the first demo generated sufficiently enough interest about services automation and connection load balancing so we spent significant time there. All in all, today’s session wasn’t as good as yesterday but I managed to avoid a complete failure with the demos so I guess I shouldn’t complain.
My session was scheduled after lunch and all attendees made it back which is a good sign (thanks to good presentations from Dan Norris and Edward Whalen). I’m pretty satisfied with the results — I was able to reproduce all eviction examples I planned from the first time and I had to skip only few demos at the end (I suspected I wouldn’t get there). Anyway, I covered all the material except those last few demos (well, the audience will have labs tomorrow and I can play with it) and quick look at the few script internals and sources but that was handed over as a home work.
Just a quick note that I’m going to present two sessions on the RAC Attack! event in Chicago next week — 4-5 August 2008. The event is organized as two threads — one for advanced RAC DBA’s and another one for beginners. Each thread will have one day of hands-on labs and one day of lectures. Another option would be to choose two days of lectures. More details on the RAC Attack event home page.
The Pythian blog has grown significantly since then and many more excellent authors started blogging there. While the Pythian blog was mostly focused on Oracle database just a couple years ago, it’s has got very broad coverage now.it might be just too much for some as few people already complained and unsubscribed to avoid being overwhelmed with information.here is a way to subscribe only to a selected category or a single author — just add /feed/ at the end of pretty much any page.
We hit an ORA-01450 error today trying to do online rebuild for an index in an unusable state. This was a non-unique index on a fairly large column — VARCHAR2(800 CHAR). It rang a bell. I remembered that I encountered this issue a while ago, but I couldn’t recall the details. I know that it has nothing to do with the actual data size — it’s an error that can occur during index creation.