Re: DBA Responsibilities... who owns the database?

Hi Mark,

There are many permissions belonging ordinary to DBA, that should be granted to senior developer for his effective work. It is necessary to

alter system kill session 'x,y'

for long running queries during tuning process. It is necessary to create new test users. The ability to select SYS.DBA_ views is very useful when comparing structures in development and production databases.

I use encrypted password from SYS.DBA_USERS to restore original password after changing it. This is necessary to change password, connect as another user,
create, replace or compile some objects and restore original password. You need DBA permission in order to change another user's password.

I need SELECT ANY TABLE, INSERT ANY TABLE and UPDATE ANY TABLE rights to insert or update table contents from one schema into another.

One may grant all these rights to some role and this role will be VERY similar
to DBA role but with another name. Maybe all this schema management is responsibility of our DBA but he deels only with hardware, physical structure
and backups. Schema management is developer's responsibility.

Andrew Protasov

Mark Powell wrote in message
<01bd8ef8$c17a6720$a12c6394_at_J00679271.ddc.eds.com>...
>No, it really isn't that hard to give a senior developer access to other
>user accounts without giving them a DBA id. You the privileges 'create any
>table, create public synonym' etc... instead of the DBA role and then they
>do not have unneeded authority like adding files.
>
>Andrew Protasov <protasov_at_percombank.kiev.ua> wrote in article >>
>> Hi Mike,
>>
>> Our senior developers have access to DBA accounts in order to have
>> simultaneous access to more than one developer's schema.
>> This is necessary for example to synchronize schemas. It is
>> quite hard to do this job without DBA account.
>>
>> Andrew Protasov
>>
>> Mike Oswald wrote in message <3574B0EB.706D8E1E_at_mitec.net>...
>> >Okay... so we are going around and around... I came from the
>> >Applications world and still do some development to support the DBA's
>> >using Oracle*Forms. But recently the Apps Director insisted that his
>> >Developers play/be the DBA's in an Oracle instance that we have setup
>> >for them (for testing).
>> >
>> >They seem to think it is okay to have the SYSTEM/SYS account password(s)
>> >and that they should be adding datafiles!
>> >
>> >-Mike
>
Received on Thu Jun 04 1998 - 07:01:47 CDT