> Yes, we agree.
> But in practice, in a team where there is a team of several developers
> with
> many apps each one, that is working this way since many years ago without
> any security rule to follow, the change of SYSDBA privileges is the more
> secure option.

This isn't possible, change your applications instead.

With regards,

Martijn Tonies
Upscene Productions
http://www.upscene.com

Download Database Workbench for Oracle, MS SQL Server, Sybase SQL
Anywhere, MySQL, InterBase, NexusDB and Firebird!

Database questions? Check the forum:
http://www.databasedevelopmentforum.com

> Ramiro
>
> 2009/10/28 Dimitry Sibiryakov <sd@...>
>
>> > The fact is that today, the factibility of replace this data in every
>> apps
>> > is too much.
>> >
>> > That's why we think there exist the possibility to create another user
>> > as
>> a
>> > SYSDBA and let the actual SYSDBA with less rights to avoid "strange"
>> > behaviours.
>> >
>> > Is this possible?
>>
>> In theory - yes. On practice - no. Replacing user credentials in
>> application is much easier.
>>
>> SY, SD.