3 Replies Latest reply: Jan 14, 2013 3:25 PM by Joyce Scapicchio RSS

    (Bug) Save specification and package body...

    Jeann_Andrade
      Hi experts,

      I'm working with Sql Developer 3.2.20.09.

      When i'm trying to export the definition of a package, using the context menu option "save specification and package body...", the result is a empty file, with two '/'.

      However,i have the permission to see the specification and package body.

      Does anyone know how to fix this error?

      Kindly suggest me.....

      Thanks and regards
        • 1. Re: (Bug) Save specification and package body...
          Gary Graham-Oracle
          Hi,
          I have the permission to see the specification and package body
          It seems that if the permission that allows you to see the code is something like
          grant catalog_role to ...
          or
          grant select any dictionary to ...
          then the export behavior you noted will occur -- as when you export from under the Other Users node.

          If you actually own the package the export will work, and perhaps if you have the execute privilege (but I did not check). I will ping the developer. Hopefully you will get an additional response about whether this is expected behavior or a bug.

          Regards,
          Gary
          SQL Developer Team
          • 2. Re: (Bug) Save specification and package body...
            Jeann_Andrade
            Hi Gary,

            It seems that the issue is related to the lack of executing privilege.

            I managed to export using another user with this privilege.

            My user really can not run the objects, can only see them.

            The question now is why I can see the specification and package body but I can not save your text to a file?

            I'll wait for a response from developer.

            Regards,
            Jeann
            • 3. Re: (Bug) Save specification and package body...
              Joyce Scapicchio
              Looking at the Save Specification and Package Body code, I can see that we are only querying the ALL_SOURCE view which means we will not find the source in your case. The code needs to determine if the user can access to the DBA_SOURCE view and use that if possible. Working on that change now.

              Joyce Scapicchio
              SQLDeveloper Team