Re: ASM or not to ASM
Date: Tue, 12 Jul 2011 07:47:53 -0700
In this case I would say that the change management implementation was flawed.
We had quite comprehensive change management, but changes were not difficult
and emergency changes could be made the same day.
Change management is a good thing, if done properly.
On Mon, Jul 11, 2011 at 12:47 PM, Lange, Kevin G <kevin.lange_at_ppoone.com>wrote:
> Worse scenario I have ever seen was an organization that had
> 1) DBA
> 2) Storage Admin
> 3) Server Admin
> 4) Hardware Admin
> 5) Change Management Admin
> Every time you wanted to get anything done you needed a weeks notice and
> 10 meetings and entries in the change management system by all departments
> involved in which any one of them being late on responding caused the entire
> process to stall and possibly have to be rescheduled.
> Give me a situation with a DBA with authority to manage their own servers
> from the hardware on up any day.
> *From:* oracle-l-bounce_at_freelists.org [mailto:
> oracle-l-bounce_at_freelists.org] *On Behalf Of *Aaron Leonard
> *Sent:* Monday, July 11, 2011 1:56 PM
> *To:* jkstill_at_gmail.com
> *Cc:* tim_at_evdbt.com; RStorey_at_dcso.nashville.org; Oracle L
> *Subject:* Re: ASM or not to ASM
> I think the key to situations such as Jared's was the "excellent system
> administrators" comment. I've also had situations that were the opposite of
> that. In the case where I deal with system/storage admins of a more junior
> level, I certainly prefer to have as much control over storage as possible,
> so ASM can be a good choice for that.
> On Mon, Jul 11, 2011 at 1:30 PM, Jared Still <jkstill_at_gmail.com> wrote:
>> On Mon, Jul 11, 2011 at 9:55 AM, Tim Gorman <tim_at_evdbt.com> wrote:
>>> The main thing that is happening is that stuff which used to "belong" in
>>> the realm of "root" and the Sys Admins are being moved under the realm of
>>> DBA. So, there is a huge political aspect to the adoption of ASM that often
>>> overshadows the technical aspect, and this political "shift of power" from
>>> Sys Admin to DBA can be more of an obstruction than any other aspect of ASM
>>> adoption. Not sure what things are like in your shop, but that is not a
>>> trivial concern.
>> In addition to the political issues, there may also be matters of
>> convenience - yours.
>> At my previous employer I did not use ASM.
>> Whenever that topic came up, fellow DBA's felt obligated to chastise me
>> and attempt
>> to convince me to use ASM. Well that just wasn't going to happen at that
>> Why not? I was the only DBA.
>> That company has some excellent system administrators, but they do not
>> know Oracle that well.
>> I liked the fact that they could look at storage on the server and monitor
>> it and see where the space was.
>> As the lone DBA, I did not really want to 'own' the storage.
>> Had I proposed ASM, I am quite sure the SA manager would have shot it down
>> when he learned the ramifications for his team,
>> and with good reason IMO.
>> Jared Still
>> Certifiable Oracle DBA and Part Time Perl Evangelist
>> Oracle Blog: http://jkstill.blogspot.com
>> Home Page: http://jaredstill.com
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or entity
> to which it is addressed. If the reader of this e-mail is not the intended
> recipient or his or her authorized agent, the reader is hereby notified
> that any dissemination, distribution or copying of this e-mail is
> prohibited. If you have received this e-mail in error, please notify the
> sender by replying to this message and delete this e-mail immediately.