If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

I support a 3rd party app that uses this privilege to allow a proxy user to attach to the database and execute commands on behalf of the actual user. I don't like it (you abdicate control at the Oracle level), but a lot of apps seem to be going that way. Security is defined and implemented (supposedly!) in the app itself, and the proxy user is given "almost DBA" level privileges.

There are both good and bad points, but (I believe) the main reason 3rd parties like to use it is that the app can be implemented to support multiple flavors of databases with less effort on the 3rd party developers part.

well in that case it will be an application level privilege; It has nothing to do with Oracle privileges. The application grants some Oracle privileges when the "BECOME" privilege is granted to the user. The name "BECOME" is not very self-revealing though.

Originally posted by rsuri .... It has nothing to do with Oracle privileges....

BECOME USER is a valid Orcale system privilege. Its main purpose is to enable one user to import other database users with import utility. It is required privilege for any user who wants to perform full import of the database, that is why it is granted to IMP_FULL_DATABASE role by default.

Jurij ModicASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?