Re: RE: EM access to developers

From: <kellyn.potvin_at_ymail.com>
Date: Sat, 31 Jan 2015 05:37:24 +0300
Message-ID: <1422671844.547728872_at_f23.my.com>



 Not that Pete and Courtney can't hold their own, along with other supporters, but I do want to add my 2c on this topic due to it's importance to me. I've spent the last couple years speaking on this exact topic of granting access to EM12c performance data to developers. I worked a number of years in the industry teaching developers how to properly use features like Top Activity and AWR data to understand performance challenges so they can be more successful.

I saw too many IT departments remove DBA roles from their staff because DBAs were viewed as roadblocks to project success. Attend a conference like ODTUG's KSCOPE and you'll hear this story so often from the developers that it will make you realize that the "us vs. them" scenario is making DBAs a liability instead of an asset. Steven Feuerstein often asks in his sessions, "of the DBAs in here, how many grant access to performance views in Enterprise Manager?" I'm often the only one who raises their hand and the common excuse is, "If we grant them access, then they'll be able to see things" Really.

Well, here's the way I see it. No DBA has any excuse for complaining about the quality of code released in production if they aren't willing to provide developers and testing the same access to view performance data in tools such as Enterprise Manager as they have. With more and more companies moving towards Agile, more companies using scrum masters/scrum collaboration, it is essential for everyone to understand the challenges they are up against and truly work as a team.

We should all be part of the solution, not part of the problem.

Kellyn Pot'Vin-Gorman
Consulting Member of Technical Staff, Enterprise Manager SCP

Sent from myMail for iOS
>
>Friday, January 30, 2015, 4:01 PM -0700 from MacGregor, Ian A. <ian_at_slac.stanford.edu>:
>Both SQL*Developer and OEM provide capabilities which are useful to DBA's and developers. In OEM you can control access to a target, and ensure that access is read only, but you really cannot control which panels a user sees. Much of what is presented is of little value to the developer.
>
> What developers want from OEM is to be able to view the overall health of the system, and whether any malaise is being caused by what they support. OEM comes closer to providing this than SQL Developer but is not there yet. It's been a few years since I looked at the SQL Developer capabilities in this area it seemed that it required giving a way the keys of the kingdom.
>
>Another problem with granting OEM access to developers is the load it may place on the OMS.
>
>Ian MacGregor
>
>-----Original Message-----
>From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Mladen Gogala
>Sent: Friday, January 30, 2015 1:53 PM
>To: oracle-l_at_freelists.org
>Subject: Re: EM access to developers
>
>Hi Pete,
>I beg to differ. EM is a DB management tool and I cannot fathom what would developers do with it? SQL plans are available from SQL Developer. Developers should use development tools, DBA should use management tools. It's not us and them, it's a division of labor. I doubt that developers would be interested in how long did the backup run or how many log switches are generated during the peek time business hours. So, it's us using EM and them using SQL Developer and Eclipse. That's just the natural order of things.
>
>On 01/30/2015 02:28 PM, Peter Sharman wrote:
>
>Quick answer: Not enough. J
>
>As Courtney mentioned, a lot more is possible more easily with EM12c than in previous releases. We really should be getting away from the “us versus them” mentality we’ve had for way too long between DBA’s and developers. As DBA’s, give the developers access so they can do their job properly but in a secured manner. As developers, use the tools that have been provided to understand and resolve your issues.
>
>Easy, right? ;)
>
>Pete
>
>Oracle logo
>
>Pete Sharman
>Database Architect, DBaaS
>Enterprise Manager Product Suite
>33 Benson Crescent CALWELL ACT 2905 AUSTRALIA
>
>Phone: +61262924095 <tel:+61262924095> | | Fax: +61262925183 <fax:+61262925183> | | Mobile: +61414443449
>
>________________________________
>
>"Controlling developers is like herding cats."
>
>Kevin Loney, Oracle DBA Handbook
>
>"Oh no, it's not, it's much harder than that!"
>
>Bruce Pihlamae, long term Oracle DBA
>
>________________________________
>
>From: kyle Hailey [mailto:kylelf_at_gmail.com]
>Sent: Saturday, January 31, 2015 4:15 AM
>To: ORACLE-L
>Subject: EM access to developers
>
>Quick poll : how many folks give developers logins to EM?
>
>Last I was talking to people about 4 years ago no one was doing that. Have times changed?
>
>I know EM Express looks perfect for developers but I'm asking about access to regular EM.
>
>Thanks
>
>Kyle Hailey
>
>http://kylehailey.com
>
>--
>Mladen Gogala
>Oracle DBA
>http://mgogala.freehostia.com
>��i��0���zX���+��n��{�+i�^

--
http://www.freelists.org/webpage/oracle-l
Received on Sat Jan 31 2015 - 03:37:24 CET

Original text of this message