Posted by David Edwards on Feb 2, 2009
Take a look at this! The January/February edition of Oracle Magazine features an interview with The Pythian Group’s Vice President East Asia-Pacific, Alex Gorbachev. Congrats, Alex!
It must be said here that Alex is no Christo Kutrovsky, a fact that the editors of Oracle Magazine have underscored by publishing a very small picture of Alex with his face obscured by shadow. Don’t be too hurt, Alex—what you lack in coverboy style and sass, you more than make up for in Oracle acumen.
In the background looms either the dome of the famous Sydney Opera House or one of Australia’s Great White Sharks.
Posted by Sheeri Cabral on Sep 5, 2008
I confess — I have not always been an exclusive MySQL user. I have fooled around with other DBMSs. I was young, inexperienced, and I needed the money, I swear!
This comes about because I was doing some electronic de-crufting….From a file last modified on 10:50 am on 2005-06-30:
> more addcatalog.sh
#!/bin/sh
db2 catalog tcpip node $1 remote $2 server 50000
db2 terminate
db2 catalog database sample as $2 at node $1
db2 terminate
# [db2inst1@midgard db2inst1]$ db2sql92 -a db2inst3/password -d coworkername
And from the same time-frame there’s also:
Read the rest of this entry . . .
Posted by Alex Fatkulin on Nov 22, 2007
Just a short blog entry about a funny error message I’ve got while trying to activate a physical standby database:
SQL> alter database recover managed standby database finish skip standby logfile;
alter database recover managed standby database finish skip standby logfile
*
ERROR at line 1:
ORA-00283: recovery session canceled due to errors
ORA-01110: data file 1: '/oradata/stage/datafile/system_01.dbf'
ORA-01122: database file 1 failed verification check
ORA-01110: data file 1: '/oradata/stage/datafile/system_01.dbf'
ORA-01130: database file version 9.2.0.0.0 incompatible with ORACLE
version 9.2.0.0.0
Database file version 9.2.0.0.0 is incompatible with ORACLE version 9.2.0.0.0, is it?
Posted by David Edwards on Jun 11, 2007
Congratulations to Christo, Senior (and stylish!) DBA for The Pythian Group, on his spread in the July/August issue of Oracle Magazine, which you can download! Just jump straight to page 41 (not page 3), feast your eyes and hear what he has to say about Oracle Enterprise Manager! Here’s a sneak preview!
Christo is wearing a conservative but bold button-down russet shirt with pinstripe flat-front trousers, an ensemble that screams, “I’m a world-class DBA, but I don’t have to be one!” Here’s a little more about our Christo!
Turn-Ons:
- long row-level locks on the beach
- the soft whine of a disk spinning up
- lounging by a contiguous shared pool
- a nice RAC
- saving his clients time and money (Paul made me write this one, okay?)
Turn-Offs:
For those of you who’d like to meet him in the flesh, don’t forget — Christo will be making appearances at Oracle conferences throughout the year!
Posted by Babette Turner-Underwood on May 2, 2007
I am an ex-tea tottler. Several months ago, I started to once again drink that elixir of the Database Gods. Now that I am beginning to drink coffee again, I can really appreciate Jon Emmons’s humor in naming his blog site www.lifeaftercoffee.com. Truly, a DBAs work life does NOT begin until after coffee.
Unfortunately, it had been years since I actually brewed a pot of coffee. What was I going to do? Like many people using a new technology, I wanted to make some but had no idea of where to begin. Luckily, our company had a BIG sign posted next to the coffee machine, “Are you tired of weak, crappy coffee?”, with detailed instructions.
I don’t think I am giving away too many Pythian secrets here, but not only did it explain to only put a portion of the potential water reserve so the coffee would be stronger. It also gave warnings of potential problems. One problem was that putting the coffee grinds and water in before turning the unit off would cause a burst of steam to cause the grinds to be blown all over and ruin the pot of coffee. Pure Genius!
The instructions were so humorous because I see them as exemplifying the work ethic at Pythian. And that is, documentation and sharing of information. When we do work for a client, we carefully document all the steps taken, and any problems encountered and workarounds we discovered. The information is then put into a shared repository for all the DBAs to access and use in similar situations.
Most recently markings were added to the actual coffee pot to indicate MINIMUM and MAXIMUM levels. As a DBA, I am very familiar with thresholds. If something like free space reaches a MININUM, then I react by adding additional space. When the coffee pot reaches the minimum, there is an indication that it is time to make a new pot. The MAXIMUM indicator assists us to ensure that we do not go over our limits (for water).
So sharing the secret to making a perfect cup of coffee or cloning a database with RMAN are handled the same way around here. Freely, in the spirit of teamwork and making each others’ lives easier for both us and our clients.
