Tez

 Profile Answers by Tez 

• Oct 9th, 2005

 

U can unerstand these if u hav an idea of DBA..... DBA is the one who has all the priveleges on the database.....So if u are a user of the database........ and if u want to make some operations on the database......(Whatever may be the operation)...... u should have the required privelege to perform an operation...... if u dont hav..... the superior who has the rights to provide the priveleges to u can provie u.......GRANTis a command to grant the priveleges

Antony Gubert

• Mar 6th, 2006

 

Definer Rights

--------------

A routine stored in the database by default, is executed with the definer rights (owner of the routine), depending on the user who calls it. 

 

For example, table "Test" belongs to schema A. User A creates a procedure PR_TEST allowing for updates of a table. User B is granted execute privileges on the procedure. Now user B cannot access the table as no privileges have been granted, but can call the procedure to do the required process logic for updating the table.

 

Invoker Right

-------------

With Oracle 8i, there is no need for this duplication of code. A single compiled program unit can be made to use schema A's objects when invoked by User A and schema B's objects when invoked by User B. This way, we have the option of creating a code repository in one place and sharing it with various production users. The owner of the routine must grant EXECUTE privilege to other users.

 

To enable code to run with Invoker rights, an AUTHID clause needs to be used before the IS or AS keyword in the routine header. The AUTHID clause tells Oracle whether the routine is to be run with the invoker rights (CURRENT_USER), or with the Owner rights (DEFINER). If you do not specify this clause, Oracle by default assumes it to be AUTHID DEFINER.

 

Create or Replace procedure test authid current_user as

????????;