Re: Remote DBA
- From: Kellyn Pedersen <kjped1313@xxxxxxxxx>
- To: Andy Klock <andy@xxxxxxxxxxxxxxx>
- Date: Mon, 27 Sep 2010 13:45:33 -0700 (PDT)
Oh, I love this topic...:)
Doesn't this go back to "Why do it right when I can do it twice"? You will
always find those folks that due to a need for instanct gratification or maybe
a need to play superman, "look, I came and saved the day AGAIN! Aren't I
great!" that will simply duct tape/band aid the problem vs. researching what is
actually causing the issue and correct it long term, which often means
investing the proper amount of time and effective research to do so?
Professionally, if a problem arises a second time, I have a real problem with
it... It signifies that I'm not doing my job or I'm not being allocated
correctly to perform what needs to be done to correct issues long term. As a
DBA, I believe that is a waste of valuable resources that could be allocated
more efficiently, aka, "do it right, don't do it twice..."
Yes, I know there are emergency situations that arise and demand a short term
fix to allow accessibility to a system or resolve an issue asap, but when it
starts to become a consistent option for all resolutions, it's not resolving an
issue, its a waste of company resources, time and money. This type of
technical resource is not an asset, they are a liability in the long run- IMHO
Kellyn Pedersen
Sr. Database Administrator
I-Behavior Inc.
http://www.linkedin.com/in/kellynpedersen
www.dbakevlar.blogspot.com
"Go away before I replace you with a very small and efficient shell script..."
--- On Mon, 9/27/10, Andy Klock <andy@xxxxxxxxxxxxxxx> wrote:
From: Andy Klock <andy@xxxxxxxxxxxxxxx>
Subject: Re: Remote DBA
To: kjped1313@xxxxxxxxx
Cc: Richard.Goulet@xxxxxxxxxxx, andrew.kerber@xxxxxxxxx, cicciuxdba@xxxxxxxxx,
"oracle-l-freelists" <oracle-l@xxxxxxxxxxxxx>
Date: Monday, September 27, 2010, 1:54 PM
I also like Matt's glass half full definition of "ticket closer". The ability
to prioritize and work tickets is an important (and not easy) skill. However,
I've been using that same nickname for years, but in a more derogatory way.
There are some DBAs (but this mentality affects developers too) who will take
the path of least resistance just to be able to close a ticket. And close many
of them. For example:
Ticket: Investigate ORA-01653 in UAT
Action: alter database datafile
'/u01/app/oracle/oradata/important_tablespace01.dbf' resize 1000m;
Ticket State: closed
But then, only to have this same issue rear is ugly head in PROD the next day.
I think a more important skill is to effectively work a low priority ticket to
completion so it never becomes a critical one. I also like verbose
descriptions of the resolution path and copy/pastes of the exact commands so
they can be easily understood and reproducible.
I get very worried when I see a resolution that only consists of "Done".
Other related posts:
