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.

Similar Messages

  • 3.1EA2 bug still not fixed - Members of package body not listed in the tree

    Hi, I was working today with SQL Developer again and found that this bug is still not fixed even when it was reported more than 1 year ago!!!
    I did a quick search and found it here
    Package Body Tree not always showing
    The problem is when you expand the package specification or package body tree, not all members of the specification/body are listed. This is mostly observable in the package body, but it regards to the specification as well.
    Consider this case:
    CREATE TABLE EMP (
        ID               NUMBER(6,0) DEFAULT 0,
        NAME             VARCHAR2(20 BYTE) DEFAULT NULL,
        DEPT             VARCHAR2(20 BYTE) DEFAULT NULL,
        FUNCTION         VARCHAR2(20 BYTE),
        PROCEDURE        VARCHAR2(20 BYTE));
    CREATE TABLE LOOP (
      AREA    VARCHAR2(5),
      VALUE   VARCHAR2(2));
    CREATE OR REPLACE PACKAGE Test_Package1 AS
    gvc_const CONSTANT VARCHAR2(10) := 'xxx';
    PROCEDURE Test(p_RC OUT NUMBER,
                   p_ID IN NUMBER);
    END Test_Package1;
    CREATE OR REPLACE PACKAGE BODY Test_Package1 AS
    PROCEDURE Test(p_RC OUT NUMBER,
                   p_ID IN NUMBER)
    IS
    BEGIN
      --INSERT INTO EMP (ID, NAME, DEPT, PROCEDURE) VALUES (1, 'Tina', 'xxx', 'xxx');
      --INSERT INTO EMP (ID, NAME, DEPT, FUNCTION) VALUES (2, 'Jeff', 'xxx', 'xxx');
      --INSERT INTO LOOP(AREA, VALUE) VALUES('a','b');
      NULL;
    END;
    END Test_Package1;Compile the package specification and the body. Expand the spec + body in the tree. Uncomment any of the commented lines in the package body and compile the body again. Now expand the package body again and look what is displayed.
    Why? It is because SQL Developer handles words "Function", "Procedure" and "Loop" as keywords and according to them does the parsing.
    Another case
    CREATE OR REPLACE PACKAGE Test_Package1 AS
    gvc_const CONSTANT VARCHAR2(10) := 'xxx';
    TYPE Loop_rec IS RECORD(
      item1   LOOP.AREA%TYPE);
    PROCEDURE Test(p_RC OUT NUMBER,
                   p_ID IN NUMBER);
    END Test_Package1;Compile just this specification and try to expand it in the tree. Again, during parsing the package, SQL Developer takes the word "LOOP" into consideration and fails to parse the specification.
    There is exactly the same problem when you declare functions from external dll libraries in package body. Since there is no "END;" in this case, SQL Developer's parser fails...
    To me it seems you simply blindly took some keywords like "FUNCTION" and expect there will be some "END;" keyword corresponding with it.
    Can anyone have a look at this and finally fix it?

    Hi,
    Thanks for trying out SQL Developer 3.1 EA2 and providing a clear, reproducible test case for this issue. I logged an internal bug for it:
    Bug 13438696 - 3.1EA2: FORUM: CERTAIN KEYWORDS IN PKG BODY BLOCK MEMBERS FROM CONN VIEW TREE
    It seems the bug noted in the other forum thread you reference has been fixed, but really had nothing to do with problems discussed either here or there. That fix involved adding an Edit Body... item to the Package context menu in the Schema Browser, not displaying Package members correctly in the Connection view tree.
    Regards,
    Gary
    SQL Developer Team

  • BUG 1.5:Can't edit package body in other user.

    This is getting ridiculous. I didn't really have time to do anything with pl/sql development during the EA period and now that I do, nothing seems to work.
    I have a package and package body owned by user x. I am connected as system.
    I can edit the package, but not the body. The edit window opens, and I can compile it but I can't make any changes in the editor.
    1.5 prod with jre
    windows xp sp2
    Oracle 11.1.0.6.0

    We don't have a date scheduled for the patch release. We're working on the key issues and will release the patch when these are done. We do not plan to make this a long drawn out process.
    Sue

  • Bug report : Navigator display wrong messages in package body

    Just run some code , you can see the Navigator display wrong messages in the package body,but the package work fine in sqlplus / toad or other tools.
    create or replace package SIMPLE AS
    Procedure simple_proc ;
    END;
    create or replace package body SIMPLE AS
    Procedure simple_proc
    IS
    v_tname varchar2(100);
    begin
    SELECT PERCENTILE_disc(0.5) WITHIN GROUP (ORDER BY tabtype DESC)
              INTO v_tname
              FROM tab;
    END simple_proc;
    END;
    Then open the package body in the Navigator (Connection Pane==> Connection Name ==> Packages ==> Simple Body ) , and show the error message:
    Unexpected token
    Missing Expression
    But if I just create the procedure out of the package , it work fine.
    CREATE OR REPLACE
    Procedure simple_proc
    IS
    v_tname varchar2(100);
    begin
    SELECT PERCENTILE_disc(0.5) WITHIN GROUP (ORDER BY tabtype DESC)
              INTO v_tname
              FROM tab;
    END simple_proc;
    /

    This has already been discussed a number of times (see http://forums.oracle.com/forums/search.jspa?objID=f260&q=Unexpected+token).
    As I understand it, it is related to the parser that SQL Developer is using to display the package decomposition in the navigator not coping with the full PL/SQL and SQL syntax (largely analytical functions from memory).

  • BUG 1.5 : Can't create package body.

    I'm getting this stack dump in the console trying to create a package body.
    I'm logged in as a dba.
    executed 'alter session set current schema=x';
    created package in the worksheet.
    opened package from Other users|x|packages.
    Edited and compiled package.
    Tried to create body from connection tree context menu.
    I have both viewer and edit window open on the package. The stack dump occurs regardless of which one had focus before I go to the tree to create the body.
    Exception while performing action Create Body
    java.lang.IllegalStateException: Not in compound edit
            at oracle.javatools.buffer.AbstractTextBuffer.endEdit(AbstractTextBuffer.java:1126)
            at oracle.ide.model.TextNode$FacadeTextBuffer.endEdit(TextNode.java:1074)
            at oracle.dbtools.raptor.dialogs.actions.CreateBodyAction.launch(CreateBodyAction.java:94)
            at oracle.dbtools.raptor.controls.sqldialog.ObjectActionController.handleEvent(ObjectActionController.java:140)
            at oracle.ide.controller.IdeAction.performAction(IdeAction.java:524)
            at oracle.ide.controller.IdeAction.actionPerformedImpl(IdeAction.java:855)
            at oracle.ide.controller.IdeAction.actionPerformed(IdeAction.java:496)
            at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
            at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
            at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
            at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
            at javax.swing.AbstractButton.doClick(AbstractButton.java:302)
            at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1000)
            at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1041)
            at java.awt.Component.processMouseEvent(Component.java:5488)
            at javax.swing.JComponent.processMouseEvent(JComponent.java:3126)
            at java.awt.Component.processEvent(Component.java:5253)
            at java.awt.Container.processEvent(Container.java:1966)
            at java.awt.Component.dispatchEventImpl(Component.java:3955)
            at java.awt.Container.dispatchEventImpl(Container.java:2024)
            at java.awt.Component.dispatchEvent(Component.java:3803)
            at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
            at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
            at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
            at java.awt.Container.dispatchEventImpl(Container.java:2010)
            at java.awt.Window.dispatchEventImpl(Window.java:1774)
            at java.awt.Component.dispatchEvent(Component.java:3803)
            at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
            at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
            at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
            at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
            at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
            at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)

    This has been fixed for the patch release 1.5.1.
    Sue

  • "Read Only" open other schema's package body even have write permission

    Oracle SQL Developer 2.1 (2.1.0.63)
    I can view and modify package under my schema, but when I open other schema's package body, it show "Read Only" in status bar and can't type in code editor.
    I'm sure my connected user have write permission and it works fine in old sql developer version.
    Is there some toggle for "read only" view or some issue for new release?

    Not very helpful for you at the moment, but according to EA 2.1. Can't edit another users store procedures. this has been bugged and will hopefully get fixed soon.
    theFurryOne

  • Search Package Body for Keywords

    I would like to know if anyone has a query to search a package body for a particular word and then return all of the procedure names where that word (or words) are found. I am in the beginning stages of a 3-5 year upgrade/re-write project and just when I think that I have been given all of the requirements "they" come up with something else. Go figure! For instance I might need to find all of the procedures for a package or packages that contain the word product. Manually searching through all of my packages is very time consuming and I'm sure that someone out there has already written a query to do this.
    Any help will be greatly appreciated!
    Thanks!
    Randy

    >
    I would like to know if anyone has a query to search a package body for a particular word and then return all of the procedure names where that word (or words) are found. I am in the beginning stages of a 3-5 year upgrade/re-write project and just when I think that I have been given all of the requirements "they" come up with something else. Go figure! For instance I might need to find all of the procedures for a package or packages that contain the word product. Manually searching through all of my packages is very time consuming and I'm sure that someone out there has already written a query to do this.
    >
    A query? No
    Would you settle for Oracle supplied functionality that can probably provide all of that cross-reference information for you?
    As you can tell from all of the other replies it seems many, if not most, people are not familiar with PL/Scope, which was introduced in version 11.1 (you should always provide your 4 digit Oracle version).
    >
    PL/Scope is a compiler-driven tool that collects data about identifiers in PL/SQL source code at program-unit compilation time and makes it available in static data dictionary views. The collected data includes information about identifier types, usages (declaration, definition, reference, call, assigment) and the location of each usage in the source code.
    PL/Scope enables the development of powerful and effective PL/Scope source code browsers that increase PL/SQL developer productivity by minimizing time spent browsing and understanding source code.
    PL/Scope is intended for application developers, and will usually be used in the environment of a development database.
    >
    See Chapter 8 Using PL/Scope in the Advanced Appication Developer's Guide
    http://docs.oracle.com/cd/B28359_01/appdev.111/b28424/adfns_plscope.htm
    >
    Specifying Identifier Collection
    By default, PL/Scope does not collect data for identifiers in the PL/SQL source program. To have PL/Scope collect data for all identifiers in the PL/SQL source program, including identifiers in package bodies, set the PL/SQL compilation parameter PLSCOPE_SETTINGS to 'IDENTIFIERS:ALL'.
    >
    Without knowing your actual needs or requirements I can't speculate on whether this will give you everything you are looking for.
    But don't reinvent the wheel without checking this out first.
    Basically just set the compilation parameter and recompile all of the code. Then there will be static dictionary views available with the cross-reference data.
    Even if you are not currently using 11g if I were you I would create an 11g sandbox with all of the objects and code (no data needed) just so you could use PL/Scope to get this cross-reference information.

  • EA 3.0 returns error on compiling of package body

    Hi,
    I got the following error
    Error: ORA-06550: line 1, column 64:
    PLS-00172: string literal too long
    when I was trying to compile package body.
    In previous version of SQL DEV the package is compiled without any problems.
    I have a procedure in package with more than 120 parameters.
    Edited by: user635344 on Oct 15, 2010 10:54 AM

    This problem is a bug : SQL*Developer 3EA1 - Not Compiling package Body
    regards Karsten

  • How can i find start line of any functions or procedures stored in package body?

    hi
    how can i find start line of any functions or procedures stored in package body?
    is there any way to write a query from for example user_source?
    thanks

    how can i find start line of any functions or procedures stored in package body?
    Why? What will you do differently if a procedure starts on line 173 instead of line 254?
    Tell us what PROBLEM you are trying to solve so we can help you find the best way to solve it.
    If you use PL_SCOPE that info is available in the *_IDENTIFIERS views. See 'Using PL/Scope in the Advanced Dev Doc
    http://docs.oracle.com/cd/B28359_01/appdev.111/b28424/adfns_plscope.htm
    Try this simple sample code. The query is modified from that doc sample:
    -- tell the compiler to collect the info
    ALTER SESSION SET PLSCOPE_SETTINGS='IDENTIFIERS:ALL';
    -- recompile the package
    CREATE OR REPLACE package SCOTT.pack1 as
    PROCEDURE proc1;
    PROCEDURE proc2;
    END;
    CREATE OR REPLACE package BODY SCOTT.pack1 as
    PROCEDURE proc1 IS
    BEGIN
      NULL;
    END;
    PROCEDURE proc2 IS
    BEGIN
      proc1;
    END;
    PROCEDURE proc3 IS
    BEGIN
      proc1;
      proc2;
    END;
    END;
    -- query the info for the package spec
    WITH v AS (
      SELECT    Line,
                Col,
                INITCAP(NAME) Name,
                LOWER(TYPE)   Type,
                LOWER(USAGE)  Usage,
                USAGE_ID,
                USAGE_CONTEXT_ID
        FROM USER_IDENTIFIERS
          WHERE Object_Name = 'PACK1'
            AND Object_Type = 'PACKAGE'
    SELECT LINE, RPAD(LPAD(' ', 2*(Level-1)) ||
                     Name, 20, '.')||' '||
                     RPAD(Type, 20)||
                     RPAD(Usage, 20)
                     IDENTIFIER_USAGE_CONTEXTS
      FROM v
      START WITH USAGE_CONTEXT_ID = 0
      CONNECT BY PRIOR USAGE_ID = USAGE_CONTEXT_ID
      ORDER SIBLINGS BY Line, Col
    LINE,IDENTIFIER_USAGE_CONTEXTS
    1,Pack1............... package             declaration        
    2,  Proc1............. procedure           declaration        
    3,  Proc2............. procedure           declaration        
    -- query the info for the package body - change 'PACKAGE' to 'PACKAGE BODY' in the query above
    LINE,IDENTIFIER_USAGE_CONTEXTS
    1,Pack1............... package             definition         
    2,  Proc1............. procedure           definition         
    6,  Proc2............. procedure           definition         
    8,    Proc1........... procedure           call               
    10,  Proc3............. procedure           declaration        
    10,    Proc3........... procedure           definition         
    12,      Proc1......... procedure           call               
    13,      Proc2......... procedure           call               

  • Strange behaviour in PL/SQL package - known bug or feature?

    On 10g (10.1.0.2.0/win32) we have some packages who behaves different than on 9i and 8.1.7. The problem is about a call to a procedure who clears a package record. The behaviour is strange because the result is wrong depending on the datatype of the elements in the record. The following example illustrates the problem:
    create or replace package p as
    type vc_type is record(f varchar2(10));
    type nl_type is record(f number(10));
    type nu_type is record(f number);
    vc_rec vc_type;
    nl_rec nl_type;
    nu_rec nu_type;
    procedure vc;
    procedure nl;
    procedure nu;
    end p;
    sho err
    create or replace package body p as
    procedure clr is
    begin
    vc_rec := null;
    nl_rec := null;
    nu_rec := null;
    end clr;
    procedure vc is
    w vc_rec.f%type;
    begin
    vc_rec.f := '5';
    w := vc_rec.f;
    dbms_output.put_line('vc, before clr. w: '||w||', vc_rec.f: '||vc_rec.f);
    p.clr;
    dbms_output.put_line('vc, after clr. w: '||w||', vc_rec.f: '||vc_rec.f);
    dbms_output.put_line('Expected: w = 5 and vc_rec.f = null');
    end vc;
    procedure nl is
    w nl_rec.f%type;
    begin
    nl_rec.f := 5;
    w := nl_rec.f;
    dbms_output.put_line('nl, before clr. w: '||w||', nl_rec.f: '||nl_rec.f);
    p.clr;
    dbms_output.put_line('nl, after clr. w: '||w||', nl_rec.f: '||nl_rec.f);
    dbms_output.put_line('Expected: w = 5 and nl_rec.f = null');
    end nl;
    procedure nu is
    w nu_rec.f%type;
    begin
    nu_rec.f := 5;
    w := nu_rec.f;
    dbms_output.put_line('nu, before clr. w: '||w||', nu_rec.f: '||nu_rec.f);
    p.clr;
    dbms_output.put_line('nu, after clr. w: '||w||', nu_rec.f: '||nu_rec.f);
    dbms_output.put_line('Expected: w = 5 and nu_rec.f = null');
    end nu;
    end p;
    sho err
    set serveroutput on size 1000000
    exec p.vc
    exec p.nl
    exec p.nu
    The output on my database is:
    vc, before clr. w: 5, vc_rec.f: 5
    vc, after clr. w: 5, vc_rec.f:
    Expected: w = 5 and vc_rec.f = null
    nl, before clr. w: 5, nl_rec.f: 5
    nl, after clr. w: , nl_rec.f:
    Expected: w = 5 and nl_rec.f = null
    nu, before clr. w: 5, nu_rec.f: 5
    nu, after clr. w: 5, nu_rec.f: 5
    Expected: w = 5 and nu_rec.f = null
    Whats going on here? Can anyone help?

    Looks like a bug to me. I reproduced the results in 10.1.0.3.0 (linux) as well. Obviously you should check on Metalink and log a TAR if you don't find it.

  • SQLDeveloper 3.2.20.09. Package body button is not active.

    SQLDeveloper version: 3.2.20.09
    OS: Ubuntu 12.04 LTS
    JDK: jdk1.6.0_35 (Oracle)
    To be short and precise, there is a bug introduced with the latest SQLDeveloper release: the "Open Body" button in the package specification editing worksheet is inactive (greyed out) when the package opened for the first time (http://imm.io/KxbO) and is normal when opened for the second time and so on (http://imm.io/KxcE).
    Steps to reproduce the bug:
    1. (Re)connect to the DB
    2. Open "Packages" in the object tree
    3. Double click any package, that has a package body - this will open the package specs
    4. See the inactive "Open Body" button
    5. Close the package specs
    6. Repeat step 3.
    7. See active "Open Body" button
    Does anyone has the same problem? Is it a bug? Any workarounds to eliminate it?
    P.S. Terminal output is totally empty:
    arino@firestarter:~$ sqldeveloper
    Oracle SQL Developer
    Copyright (c) 1997, 2011, Oracle and/or its affiliates. All rights reserved.
    Registered TimesTen

    Hello Arino,
    On the Windows 3.2.20 version I can reproduce the bug.
    The 3.2.10 and 3.1 version works ok.
    Workaround: open the body in the connection window by double clicking the body. Close the Spec tab and open the spec tab by clicking the 'Open Spec' button in the body.
    Best regards,
    Joop

  • Package body name in script - Oracle SQL Developer Data Modeler 3.0.0.6.

    Hi,
    I have problem with package body full name. In package body properties I have my <schema_name>. But there is something like "user5" insted my <schema_name> in package body script. I replaced it and saved it. But, when I re opened package body, there is user5 again, while name of package is OK.
    Can I set some property to stay there my schema_name?
    Thank you.
    Stefan.
    Edited by: user13617034 on 4.4.2011 5:10
    Edited by: user13617034 on 4.4.2011 5:12

    SQL Server Physical model doesn't save table identity column.
    here are the steps to get this bug:
    1. create a table in relational model with a column as an integer to be used as an identity.
    2. create or open a physical model for SQL-SERVER 2005
    3. open the table in the physical model
    4. edit the integer column property dialog
    5. tick the identity check box and close the property dialog
    6. save the model and close it
    7. open it again, you will find the identity check is removed! (probably not saved from the start)

  • SQL*Developer 3EA1 - Not Compiling package Body

    Don't know if this is best place to post this, if not tell me where.
    In some packages i'm getting: Error: ORA-06550: linha 1, coluna 64:PLS-00172: literal de cadeia de caracteres demasiado extenso; Sorry about the portuguese error message but it's cpopy paste from compiler log.
    The strange about this is that the package is compiling with no errors on Version 2.1.1.64 and also on others editors. In both packages i had this was after formatting the code.
    So far is the only bug i got, keep on the good work.
    António Cunha

    Just tried from pl/sql node. The package body does not compile from there either. The issue seems to be the size of the package. The package size is 35,000 characters and spaces. I can remove any combination of source lines to get it down to 32,000 characters and spaces and it will compile.
    Edited by: dagtech on Oct 21, 2010 9:34 AM

  • 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).

  • SQL developer 3.1 in schema browser doesn't show package body

    Hi,
    When i search a package with schema browser, i can't see the package body of other owner, the menu "edit body" is disabled.
    My user as select any dictionary et select_catalog_role
    When i connect with a DBA's user, i can see all.
    I'am on windows with sqldev 3.1
    Thanks

    Hi erifet,
    This one seems to go back and forth. It was originally fixed in Schema Browser for 3.0. The "Edit Body" was greyed out, but an "Open Body" icon in the code editor toolbar for Package Spec was enabled. Here is the forum reference:
    30EA1 package bodies missing in schema browser still not fixed
    In 3.1, both "Edit Body" and "Open Body" are greyed out, and that applies both to Schema Browser and Connection Navigator for Other Users packages, so at least 3.1 is consistent. The difference between the Browser and the Navigator is Schema Browser has no option to display a Package Body type (must go through Package Spec type), while the Connection Navigator displays a Package Body node type in the tree beneath the Spec node. In the forum thread AM references, Vadim explains what 3.1 does: it uses the ALL_OBJECTS view, which apparently does not include package bodies. Off-hand I'm not sure why it does not include them, and the following link doesn't shed any light:
    http://docs.oracle.com/cd/B19306_01/server.102/b14237/statviews_1001.htm
    Adding the execute privilege on the package does not help either. At least you have the workaround of using the Connection navigator to view the package body metadata (code) of Other Users if you have been granted either SELECT_CATALOG_ROLE or SELECT ANY DICTIONARY. As for returning to the 3.0 Schema Browser behavior, perhaps Vadim will notice your post and have some explanation as to why or why not that may be possible.
    Regards,
    Gary
    SQL Developer Team

Maybe you are looking for