Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

GRANT  EXECUTE on Package body??

Posted on 2010-08-30
11
Medium Priority
?
13,845 Views
Last Modified: 2012-05-10
Hi,
can you please somebody send me syntax for GRANT Execute on Package body? i did not see package body in SQL developer even I  ran the " GRANT EXECUTE ON schema.xyz_pkg to  some_user;" i do see the package specification but not package body. i am using SQL developer. Did i am missing anything in the systax??
0
Comment
Question by:husseink
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
  • 2
  • +3
11 Comments
 
LVL 77

Expert Comment

by:slightwv (䄆 Netminder)
ID: 33561562
>>Did i am missing anything in the systax??


Nope.  You grant execute on the package.  That's it.
0
 
LVL 143

Expert Comment

by:Guy Hengel [angelIII / a3]
ID: 33561566
connect as the owner/schema to grant the permissions. not "everybody" can grant permissions.
0
 

Author Comment

by:husseink
ID: 33561647
i connected as a schema owner and executed the above syntax. still the user don't see the packagebody...
0
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

 
LVL 143

Expert Comment

by:Guy Hengel [angelIII / a3]
ID: 33561667
in the sql developer, you might need to "refresh" in the package folder to see the new permissions.
though EXECUTE permissions does not give you permissions to see the package body code, if I remember correctly ...
0
 
LVL 77

Expert Comment

by:slightwv (䄆 Netminder)
ID: 33561671
Unless there is a synonym they need to fully qualify it with schema.xyz_pkg.

If the user logs in to sql*plus what do they see when the do the following:
SQL> describe schema.xyz_pkg



0
 

Author Comment

by:husseink
ID: 33563837
i refreshed but still package bodies folder does not have anything.
when i say describe schema.xyz_pkg , i see only package specification....
0
 
LVL 7

Expert Comment

by:sumit2906
ID: 33564140
describe will show only signature of packages procs.
if you want to make sure that the package is avaialble, query all_source.
0
 
LVL 1

Expert Comment

by:saxtonj
ID: 33564763
try

SELECT text
FROM all_source
WHERE owner = <schema_owner>
AND   NAME = <package_name>
AND TYPE = 'PACKAGE BODY'

or get an IDE like TOAD, SQL Developer, or PLSQL Developer
0
 
LVL 13

Accepted Solution

by:
riazpk earned 200 total points
ID: 33565379
You either need to grant 'create any procedure' or 'select on dba_source' to the user whom you want to be able to see the source code of package body. Here is the test case to prove this:
 

SQL> ed
Wrote file afiedt.buf

  1  create or replace package pkg_test as
  2  procedure p_test;
  3* end;
SQL> /

Package created.

SQL> ed
Wrote file afiedt.buf

  1  create or replace package body pkg_test as
  2  procedure p_test is
  3  begin
  4    null;
  5  end;
  6* end;
SQL> /

Package body created.

SQL> create user test identified by test;

User created.

SQL> grant execute on pkg_test to test;

Grant succeeded.

SQL> conn test/test@test-server
ERROR:
ORA-01045: user TEST lacks CREATE SESSION privilege; logon denied


Warning: You are no longer connected to ORACLE.
SQL> conn riaz@test-server
Enter password: ********
Connected.
SQL> grant create session to test;

Grant succeeded.

SQL> conn test/test@test-server
Connected.
SQL> desc riaz.pkg_test
PROCEDURE P_TEST

SQL> ed
Wrote file afiedt.buf

  1* SELECT distinct type from all_source where name='PKG_TEST'
SQL> /

TYPE
------------
PACKAGE

--So the user can only see package not package body. This is your situation.

SQL> conn riaz@test-server
Enter password: ********
Connected.
SQL> grant create any procedure to test;

Grant succeeded.

SQL> conn test/test@test-server
Connected.
SQL> SELECT distinct type from all_source where name='PKG_TEST';

TYPE
------------
PACKAGE
PACKAGE BODY

--User can see package body as well now

SQL> conn riaz@test-server
Enter password: ********
Connected.
SQL> revoke create any procedure from test;

Revoke succeeded.

SQL> conn sys@test-server as sysdba
Enter password: ***********
Connected.
SQL> grant select on dba_source to test;

Grant succeeded.

SQL> conn test/test@test-server
Connected.
SQL> SELECT distinct type from all_source where name='PKG_TEST';

TYPE
------------
PACKAGE

SQL> ed
Wrote file afiedt.buf

  1* SELECT distinct type from dba_source where name='PKG_TEST'
SQL> /

TYPE
------------
PACKAGE
PACKAGE BODY

--User can see package body as well now. With this method you need to query dba_source.

Open in new window

0
 
LVL 77

Expert Comment

by:slightwv (䄆 Netminder)
ID: 33566514
>>describe schema.xyz_pkg , i see only package specification....

What are you wanting to do here?  

You do not grant execute on a package body.  You grant execute on the package itself and users can execute any exposed procedure or function in the package.

If you are wanting to actually see the code then use the queries above to select against dba_source.

Please explain exactly what you are wanting to do.
0
 

Author Comment

by:husseink
ID: 33570259
Thanks riazpk: Thanks for all ur anaswers.  Problem is when the user log on using SQL developer he is not able to see the package body . he only sees package spec.

As per riazpk comment: i did   "grant create any procedure to test;".  I grant this on the my user. now user can able to see the package body using SQL developer.

Thanks for all once again....
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I remember the day when someone asked me to create a user for an application developement. The user should be able to create views and materialized views and, so, I used the following syntax: (CODE) This way, I guessed, I would ensure that use…
From implementing a password expiration date, to datatype conversions and file export options, these are some useful settings I've found in Jasper Server.
Via a live example show how to connect to RMAN, make basic configuration settings changes and then take a backup of a demo database
This video shows how to Export data from an Oracle database using the Original Export Utility.  The corresponding Import utility, which works the same way is referenced, but not demonstrated.

609 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question