Problem in viewing package body methods

Hi,
Methods are showing in object browser in the package header only but not in the body where I think it is the most useful. On clicking the desired method, the right window should also scroll to the selected method.
Thanks.
JC

Hi Mithu,
CAF service browser is based on CAF Web Dynpro model which has several limilations. Check the SAP note <a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_caf/~form/handler">1030595</a> and <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20063659-4f03-2a10-6a8a-d88786c39b71">this</a> document for more details on the limitations of CAF Web Dynpro model. To check the operations working properly create a web service for the app service test from the wsnavigator.
Thanks,
Dipankar

Similar Messages

Why i cant view package body ?

hi all,
i cant view package body in my pl/sql.
pls help.
tks.

It'isn't yours then!!
So try this
SELECT TEXT
FROM ALL_SOURCE
WHERE ( OWNER,NAME ) IN (
     SELECT OWNER,NAME
     FROM (
               SELECT USER AS OWNER,OBJECT_NAME AS NAME
               FROM USER_OBJECTS
               WHERE OBJECT_NAME = :NAME
                    AND OBJECT_TYPE <> 'SYNONYM'
               UNION ALL
               SELECT TABLE_OWNER,TABLE_NAME
               FROM USER_SYNONYMS
               WHERE SYNONYM_NAME = :NAME
               UNION ALL
               SELECT TABLE_OWNER,TABLE_NAME
               FROM ALL_SYNONYMS
               WHERE SYNONYM_NAME = :NAME
               AND OWNER = 'PUBLIC'
     WHERE ROWNUM=1
) AND TYPE = 'PACKAGE BODY'
ORDER BY LINEBye Alessandro

How to view package body in sqlDeveloper

Hi everyone, I am able to use popup describe to view a PL SQL package definiton in SQL developer.
My problem is how to view the package body easily. In TOAD, say I have a package called XX_TOAD with a procedure get_name, I can type in XX_TOAD.get_name in the editor and describe it to show the package body.
Is there an easy way to view the package body in SQL developer without having the browse the database objects?
Thanks

Type the package name in the Sand select the package /procedure and press SHIFT + F4. A new window will open displaying the package script
--rsrini

Issue with viewing Package Body in SQL Developer 2.1 RC1

Were anybody able to see the package body of other user in 2.1 RC1.
I had an issue since 2.1 EA 1 so... just curious.
- Oracle 9i
- Windows XP SP3
Please do let me know if there is any hint or setting that can be change to view the package body.
Thanks!

Thanks for your msg.
Below is the info:
1.
SQL: SELECT * FROM v$version;
Result:
Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
PL/SQL Release 9.2.0.8.0 - Production
"CORE 9.2.0.8.0 Production"
TNS for Solaris: Version 9.2.0.8.0 - Production
NLSRTL Version 9.2.0.8.0 - Production
2.
Result:
The account has 'EXECUTE' privilege on the package.
3.
SQL: SELECT username "User"
,granted_role "Granted_Role"
,initcap(admin_option) "Admin_Option"
,initcap(default_role) "Default_Role"
FROM user_role_privs
ORDER BY username
,granted_role;
Result:
User``````````Granted_Role```````````Admin_Option``Default_Role
~~~~ ~~~~~~~~~ ~~~~~~~~~ ~~~~~~~~
USER_NAME```SELECT_CATALOG_ROLE``No````````````Yes
4.
SQL:
SELECT privilege "Privilege"
,initcap(admin_option) "Admin_Option"
FROM user_sys_privs
ORDER BY privilege;
Result:
Privilege````````````Admin_Option
~~~~~~ ~~~~~~~~~
ALTER SESSION`````No
CREATE SESSION````No
CREATE SYNONYM```No

Issue with viewing Package Body in SQL Developer 2.1 EA1

I was able to view the package body from different schemas after I log in with user account in SQL Developer 1.5.5.
But with SQL Developer 2.1 EA1, I could view only spec and I can see the package body only if I log in with DBO account.
Is there any setting that needs to be configured to be able to view the package body?
Thanks!

Thanks for replying my message.
It's Oracle 9i.
What I meant 'spec' is you can see only the headers you defined in spec. You can expend the package and be able to see the all functions and procedures but you won't be able to see the '%packagename% Body' where all the detail code were written.
As I mentioned in my previous post, with SQL Developer 1.5.5 version, you can see spec and package body if you expend the package.

View package body in another schema

I have developers who want to view the code in the package body in another's schema.
I know select text from all_source/ user_source works only for packages in your own schema.
Granting system privelege 'create any procedure' allows the developer to view as well as update priveleges.
As the owner of the objects what grants do I need to give to developers so that they can only view the code.

You can grant select_catalog_role permissions to your developers. This will give your developers select access to all of the V$ views and DBA_% views. Then they can view the dba_source table to view other schema's package code..
Regards,
David

Privilege to view package body

Hi all,
I have two users... user 'A' and user 'B' (real user names changed to protect the innocent). User A creates a package spec and package body.
I want user B to be able to see the code in the package body that user A owns. Ideally I would like user B to be able to view the body code in TOAD via the schema browser or via a DESC. Is this possible?
Thanks,
Scott
PS user B can see the package spec just fine...

Having the execute privilege on a package should not give anyone the ability to see the source for the package body in all_source and if definitely does not give the user the ability to change the package. The privilege only allows them to execute the package.
By default only the owner and DBA privileged users can read both the package specification and the body from all_source. Having execute privilege will allow a user to read the specification.
One way to provide access is to create your own version of the all_source views and grant this to whoever needs the access. You can either write a very specific tailored view for the one user or create a user security table that you use to control who can see what via this special view. Plus you have to grant select access to the special view before anyone can use it.
HTH -- Mark D Powell --

Grant command to view package body

I sent a request for the DBA's to grant me rights to the package body but I only see the spec with the grant execute command.
Here is the command I just sent:
grant create any procedure to DEVELOPER1;
But the DBA changed my grant command to:
grant create procedure to DEVELOPER1;
But I still cannot see the package body. This is on a test environment.
Would the "create any procedure" command help me see the package body of different schema owners package bodies?
Or is there another grant command to see different schema package bodies?

primefsu wrote:
My dba say that you cannot use debug in this grant because session belongs right after debug.I have no clue what your dba is talking about. Anyway:
SQL> create or replace
2    package pkg1
3      is
4        procedure p1;
5 end;
6 /
Package created.
SQL> create or replace
2    package body pkg1
3      is
4        procedure p1
5          is
6          begin
7              null;
8        end;
9 end;
10 /
Package body created.
SQL> grant execute on pkg1 to u1
2 /
Grant succeeded.
SQL> connect u1@orcl
Enter password: **
Connected.
SQL> exec scott.pkg1.p1;
PL/SQL procedure successfully completed.
SQL> select text
2    from all_source
3    where owner = 'SCOTT'
4      and name = 'PKG1'
5      and type = 'PACKAGE BODY'
6    order by line
7 /
no rows selected
SQL> connect scott@orcl
Enter password: *****
Connected.
SQL> grant debug on pkg1 to u1
2 /
Grant succeeded.
SQL> connect u1@orcl
Enter password: **
Connected.
SQL> select text
2    from all_source
3    where owner = 'SCOTT'
4      and name = 'PKG1'
5      and type = 'PACKAGE BODY'
6    order by line
7 /
TEXT
package body pkg1
    is
      procedure p1
        is
        begin
            null;
      end;
end;
8 rows selected.
SQL> As you can see, package body became visible to user U1 as soon as user U1 was granted DEBUG on package.
SY.

Problem in Viewing Application service methods through Service Browser.

Hi All,
I have an Application Service (ReadFundDetails) which contains some Operations
1> createFundAtSA
2> updateFundAtSA
But I cant see the operations under the Application Service through service browser.
I have deployed the project in two diff server. But the same problem persists in both the server. All the class files under the jar file have been generated successfully. There is no build issue. I have undeployed the project then build and redeploy but still the problem comes.
I have another project for which i can see the Application Service operations successfully.
Regards,
Mithu

Hi Mithu,
CAF service browser is based on CAF Web Dynpro model which has several limilations. Check the SAP note <a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_caf/~form/handler">1030595</a> and <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20063659-4f03-2a10-6a8a-d88786c39b71">this</a> document for more details on the limitations of CAF Web Dynpro model. To check the operations working properly create a web service for the app service test from the wsnavigator.
Thanks,
Dipankar

DB Doc Package Body Bug

Hi,
i was trying the new DB Doc feature and after it completed analizing my schema i noticed that package bodies werent documented.
At first i thought it was a feature and not a bug :) but later in some of my views i saw my packages bodies were being referenced. After clicking on top of that link I'm directed to a "Page not found" page becouse that directory wasnt created.
What i wanted to know is if the DB Doc will analize package bodies, it would be usefull, if not at least the referencing link should be removed from views and other objects.
Thanks,
Alexandre.
Message was edited by:
Alx

Did someone tried this feature yet?
Can you please post your experience with it, maybe my DB Doc generation was by some problem badly generated.
I tried in other schemas and in all the same problem occurs, the package body is referenced in many other objects but when you try to click on the link you go to a "page not found".
This is happening becouse the package body directory that should have been created doesn't exists.
Alx.

SYSDBA - problem with viewing other users package body texts on sys account

Hi,
SQL Dev 1.0.0.15.27 has problem with correct display of other users package body texts on sys account. All bodies have "create or replace" text instead of all pck. bodies text.
I guest it's problem with SYSDBA role. On system account text is displayed correctly. Quest SQL Navigator 5.x has no problem with this. Any ideas ?
Regards,
MM

Hi Everyone,
Just so I can close the case on this issue, although I was successful in
using CSS to resolve the issue, actually, the issue was not really
resolved. There was (for me) still the problem of rollover images not
working in IE, and if I were ever to get another good night's sleep, I
would need to resolve it -- so I did. Recall me saying earlier about the
sizes being brought in to the javascript code by Dreamweaver? The original
issue with having the size of the small image in the code caused the code
to see the larger image as small also! However, when I deleted those size
attributes' numbers, I failed to delete the words "width" and "height"
along with the double quotes following each. So, while the other browsers
ignored these "blank" attributes within these double quotes, IE apparently
didn't, reading these "blank" values as some very small value, thus
displaying the image in the absolutely smallest size possible! Wow! When I
removed these two blank attributes, my problem went away! Live and learn!
So, to all who were desperately trying to assist me, please accept my
deepest and most sincere apologies. All the while I was blaming IE, I was
the guilty one!!! Shame on me, and thanks for the wonderful responses I
received from the Dreamweaver forum team. I will go and stand in the corner
for 8 hours with my dunce cap on...
Joe Dardard

Problem in package body creation

Hello,
I am a newbie in PL/SQL.I am sorry for posting a very silly question,but I am struggling since 2 days trying to get this PL/SQL code working.Dont know whats wrong with it.I consulated a lot of tutorials and online sources..But still couldnt figure out whats wrong.I get the following error
LINE/COL ERROR
6/1 PLS-00103: Encountered the symbol "CREATE"
The code is like following
CREATE or replace package test AS
     procedure extract_tmp_reifs ;
end;
CREATE OR REPLACE PACKAGE BODY test IS procedure extract_info(models IN varchar2,rulebases IN varchar2) is
stmt varchar2(4000);
model_name varchar2(4000);
rulebase_name varchar2(4000);
     --Create table invocation
begin
     model_name := models;
     rulebase_name := rulebases;
     stmt := 'create table '|| model_name ||'_'||rulebase_name||'_t$'||'(id number primary key, triple_id number, sd date, ed date)';
     execute immediate stmt;
     commit;
end extract_tmp_reifs;
end temporal_reification;
The line 6 is for the Create package body thing.
WIll be grateful if some one can give a hint as to whats wrong wiith it.Please help me
Thanks
Regards
Prateek!

> The requirement is to have a procedure which when provided two parameters
creates a table based on the parameters,and then values are inserted into the
table by using data from other tables.Thats why the dynamic creation of table.
I still don't like it. Besides the dynamic create issue, there is a relational design issue at stake here.
Attribute data is to be carried in the columns of a table - and not in the table name. The correct relation (from the little code I've seen posted here) is:
Model Rules = ( Model ID, Rulebase ID, Tripple ID, Start Date, End Date)
And not multiple relations where the relational table's name is dynamic and the attribute data carried in the name of the table. To put it into context, it is the same as defining an Invoice Relation as:
Invoices_20070305 = ( Invoice ID, Customer ID, Product ID, Quantity, Unit Cost, ..etc.. )
Instead of putting the date as an attribute value into the relation:
Invoices = ( Invoice ID, Invoice Date, Customer ID, Product ID, Quantity, Unit Cost, ..etc.. )
Using this dynamic method you can wind up with 1000's of tables for Model Rules. How are you going to make use of referential integrity? What about indexing? What about the complexity of having all these many dynamic tables and attempting to query them with a single query?
99% of the time, dynamically creating relations (tables) in a RDBMS is the wrong thing to do. And unless you can convince me that you have the 1% exception to the rule, I'm going to be very skeptical about the dynamic table create approach you have chosen. It is simply wrong.

Compiling package body problem

hello
i have a problem with portal 9.0.2.2.22(win2k server). When i try to log in i get the error
Error: Could not open web cache connection. The portal use-web-cache setting is set to ON while web cache may be down. (WWC-40019)
after that i run oracle enterprise manager console, logged into iasdb and tried to compile different package bodies(dbe_build_sql, wwv_qbe,...) and get the error:
Line # = 0 Column # = 0 Error Text = PLS-00801: internal error [56106]
inside this package body there is only one word
wrapped
and nothing else
on a different machine i have in the same package body tons of code(dbe_build_sql consists of 20622 lines), inside my package only one word
wrapped
where is the problem?
can anybody help me? please
need help
thanks
Marjan

Marjan,
Try to post your question in the Portal Caching forum.

What is the GRANT or permission setting that allows viewing of package body

For purposes of SOX and security/audit control, we log in under our network id's in our production environment. We have sourcecode compiled into Oracle seeded schemas ( APPS ) so that scheduled jobs are able to run with submitted from the Oracle Applications environment. We don't compile code into our personal network account areas.
I know how to GRANT EXECUTE privs so that we can execute a package in another schema, but what I want to do is to be able to view the sourcecode in another schema. Compile into APPS but be able to see the package body from my network id schema account.
I can't seem to find what the correct permission is anywhere. Granted I can look at DBA_SOURCE to get to it, but I want to use a tool like SQL Developer or TOAD to look at the code in a more presentable and easier to debug manner.
Any help ?

I guess you need GRANT DEBUG ON SCOTT.PKG TO U
SYS@LSC01> create or replace package scott.pk is procedure p; end pk;
2 /
Package created.
SYS@LSC01> create or replace package body scott.pk is procedure p is begin null; end; end pk;
2 /
Package body created.
SYS@LSC01> grant create session to u identified by u;
Grant succeeded.
SYS@LSC01> grant execute on scott.pk to u;
Grant succeeded.
SYS@LSC01> connect u/u
Connected.
U@LSC01> select text from all_source where name='PK';
TEXT
package       pk is procedure p; end pk;
U@LSC01> connect / as sysdba
Connected.
SYS@LSC01> grant debug on scott.pk to u;
Grant succeeded.
SYS@LSC01> connect u/u
Connected.
U@LSC01> select text from all_source where name='PK';
TEXT
package       pk is procedure p; end pk;
package body       pk is procedure p is begin null; end; end pk;

How do I view a FUNCTION within a Package Body

I can see the FUNCTION being executed within the Package...
FUNCTION Stop_Refresh_AsBilled
RETURN Number;
And within Oracle SQL Developer and using the Connection and "Packages" part of the Schema, I see the Function Name. However, when I <Double-Click> on the FUNCTION Name within the Schema, it is taking me to where the FUNCTION is executed within the Package and NOT to the PL/SQL Code that actually makes up the FUNCTION.
Am I missing something here??? Maybe in my Preferences??? How can I drill down further to actually find the FUNCTION Definition and PL/SQL Code that makes up the FUNCTION within the Package Body???
I can bring up the Package Body and Search on the FUNCTION that way. I'm hoping there is an easier way however to drill down to the actual PL/SQL Code that makes up the FUNCTION.
I hope I am being clear in my explanation here.
Thanks for your review and I am hopeful for a reply.
PSULionRP

Jim, opening the body node to see all functions and procedures sometimes does not work in 3.0
I have many packages generated by Feuerstien's CodeGen utility. The Query package appears just fine with every function and procedure appearing as expected in both header and body nodes. However, the Change Package fails miserably. Header shows all functions and procedures fine, but the body node only shows the top private declarations of variables and types. Not one function or procedure appears in the expanded node.
The only thing I can figure is that the Change package of about 30 named items has many of the same name+ with overloaded parameters. I think SQL Dev is having problems parsing the names in the body even though it does fine with the names in the header of the package--perhaps because of many private variables and PRAGMA's declared at the top of the body.
Both packages have about 30 functions, but the Change package body has over 2000 lines while the Query package has fewer than 500.
Just adding to the mystery--but I think it merits a bug report (gotta figure out where to report it now).

Problem in viewing package body methods

Similar Messages

Maybe you are looking for