Re: Objects ownership in Oracle !!!

This is a religious issue. It depends on how powerful the developers are.

It is SOP in large shops for the DBA to own objects, grant permissions, etc. Often, scripts for creating or modifying such are submitted to him for vetting and implementing.

It is common to give developers a tablespace where they can play - create objects, views,procedures, etc. This is generally small (e.g., a 2MB quota). In particular it is important not to give 'create public synonym' out so rebellious developers don't build their own little fiefdom.

I believe one of the FAQ's discusses this at some length.

Regards,
jh

"Nabil Courdy" <moab_at_emirates.net.ae> wrote:

>I'd like to know how Oracle manages ownership
>of database objects (tables, views, rules, procedures, etc.).
>
>What is the standard practice? Does the DBA own all
>objects and permissions are granted to users, groups, and
>roles. Or can any user create an object and grant permissions
>to whomever he/she wishes. What is standard practice?
>
>Any recommendations and hints are appreciated. Perhaps
>there is a document out there discussing the subject!
>
>TIA
>
>Nabil
>====
>

Jared Hecker, CODBA       | Oracle  and Sybase Architect and DBA
jared_at_planet.net          | - consulting in the 
76276.740_at_compuserve.com  |   NYC/NJ region