Re: DBA Skill tree
Date: Fri, 3 Apr 2009 16:42:53 +0200
I don't agree. After being an instructor for oracle courses for the past 3 years, I can say very confidently that the years of experience count for nothing when it comes down to really knowing how oracle works.
There's people that "use" oracle and there's people that use oracle. How long you do it doesn't really mean much. Its all about how curious you are, and how much effort you put into it.
Especially nowadays, you can be a full-time full-GUI DBA using nothing but enterprise manager (I'm not saying this is good, mind you) -- but you see it more and more. And I honestly believe someone that works like this for 3 or 4 years has a far less good knowledge about oracle than someone taking it apart for 6 months, doing so passionately.
Stefan P Knecht
CEO & Founder
10046 Consulting GmbH
Cell +41 (0) 79 571 36 27
On Fri, Apr 3, 2009 at 4:24 PM, Maria Gurenich <gurenich_at_gmail.com> wrote:
> Well, how about years of experience for starters? IMHO, OCP with 2 years of
> experience could not beat old school DBA with 10 years of experience even
> though the newbie thinks that he/she knows all new features. I haven't had
> chance to wrote down my thoughts, but being on a couple of interview so far,
> I end up with something like this:
> newbie - from school to 2 yrs of experience, is able to maintain database
> without unexpected downtimes, is able to make, test and keep backups and
> recovery and even if doesn't know for sure, feels with his/her guts where
> the problem is.
> standart - 2-5 yrs, includes all basics, is able to assess, judge, improve
> the existing strategies, is able to predict and plan before hand,
> understands company's benefits "using RMAN instead of hotbackups", does not
> need significant amount of time to figure out where the problem is, is ready
> with the correct (reasonable) answer for almost all questions.
> advanced - 7+ yrs, should be standart for all these years, and also be an
> expert in non-standart features: RAC, HA, RASP, architecture design.. Should
> be heavily involved in business part of the deal, meaning that he/she not
> only maintains his/her databases, but totally understands the business needs
> and the impact of downtime. This would be somebody who understands hardware
> part, is able to distinguish between small nuances, has a solid knowledge of
> database internals, is able to work productively without any gudget/tool,
> e.g. can fix anything from the command line balancing his/her laptop on the
> knee. Somebody who is able to train newbie and standart, who understands
> that database IS for developers rather than something that he/she has to
> protect FROM developers. Please, don't underestimate this fact. I've seen a
> lot of experienced DBAs, who absolutely seriously think that their job is to
> protect the database from intruders like developers and end users. IMHO,
> these are obvious signs of unripeness.
> On Fri, Apr 3, 2009 at 8:49 AM, Charles Schultz <sacrophyte_at_gmail.com>wrote:
>> After mulling this over with a few folks, I thought to hit a larger
>> audience. Has anyone done work to identify basic, standard and advanced DBA
>> skills? Oracle University has an interesting framework with their
>> certification program, but I find it lacking in several different ways and
>> looking for something a little more realistic and practical.
>> Tying together some other blog posts, I had a strange thought about basing
>> it off RPG-style skill points and how one builds a character in the virtual
>> world (so all you WOW fans should jump on this! *grin*):
>> Charles Schultz
>> Sent from Champaign, Illinois, United States