Pldoc utility to document packages created in sql developer

I am trying to find a quick way to produce documentation of packages developed in the sqldeveloper.
PLDOC claims that we can produce documentation easily. but I find it quite cumbersome to use it. since it is free source, tech support is not available.
I appreciate if any one can shed light on usage of pldoc

I don't see how this is related to SQL Developer..
Here is the forum for pldoc:
http://sourceforge.net/forum/?group_id=38875
Homepage for pldoc:
http://pldoc.sourceforge.net/
You may find help on the Oracle sql/plsql forum:
PL/SQL

Similar Messages

Package Body from SQL Developer ?

Team I am using SQL Developer Version 2.1.1.64 But I can not able to see the package body.
Right click on the package provides an option to 'Save Package Spec and Body', but when I save it .. it only store the package spec ..
Is it not possible to view the package body from SQL Developer ?
Can anyone confirm ... how to get code of package body ... ?

Hi Bipul,
Although there might be people here using that specific tool, there is still the dedicated SQL Developer forum to ask in:
SQL Developer
Regards
Peter

&& Substitution Variable in Package Body using SQL Developer

Hi Folks,
I've moved over to working to in SQL Developer (its a very early version - 1.0.0) from a combination of SQL*Plus command line and a text editor. I'm trying to get this upgrgraded, but I think the question will be the same with a newer version anyway.
I am creating a package, and in the package body I have some &&my_var substitutions that I was previoulsy prompted for when calling the .sql from the command line SQL*Plus. I need this as the variable needs to be different for the development and live environment.
When working in SQL Developer, I can load the package body from Connection->Packages->My Package->My Package Body, and click the edit button to edit the code, however, when I click the Compile button in the top of the window my code error's because of the substituion variablle. An example is:
CREATE OR REPLACE
PACKAGE BODY MY_PACKAGE AS
PROCEDURE MY_PROCEDURE
BEGIN
my_variable := &&my_function_from_live_or_dev_database
END MY_PROCEDURE
Can anyone tell me if there is a way of defining a compiler variable within the IDE widow while editing a package body stored in the database, without manually copying the code into the Worksheet and running it as a script?
Thanks,
AM

953104 wrote:
Thanks for the reply, the code was just quickly typed to show the sort of thing I am doing, it wasn't actual code form my project.
I've come from a C background so what I would have done would be create a #define and changed to when on live or development - or passed the variable to the build environment from the IDE or makefiles and the change would have reflected through my whole project.
What I want to be able to do is alter a definition of some sort that will reflect throughout my whole project, so I can change it in one location to minimize code changes before going live. I don't really want to be prompted at all. On one system it needs to be DEV_10 and on the other it needs to be LIVE_10.Is there a possibility to elimiante this difference at all?
For example if DEV_10 is the oracle schemauser on the development database and LIVE_10 would be the one on the production system. THen you could just remove all references to the schema from your code.
IF you are already connected to this schema, then you don't need to specify the schema name anymore.
example
instead of
create or replace package dev_10.myPackage
...you can simply use
create or replace package myPackage
...If needed you can alter the cuurently connected user just before you run the script.
alter session set current_schema = LIVE10;
create or replace package myPackage
...This would be a different working window in the developer (script worksheet, instead of direct pl/sql editor).
Substitution variables are allowed there.

Package, Function in SQL Developer

DB 10gR2
SQL Developer 2.1.1.64
I can see the following package's code on my SQL Developer
create or replace PACKAGE zero AS
FUNCTION one (P_TABLE VARCHAR2) RETURN VARCHAR2;
FUNCTION two RETURN VARCHAR2;
END zero;
But I can't find function one or function two on the left hand side navigation. Why can't I see the codes for both of the function? and how do I see the codes of those function?
Thanks

You are seeing the package specification. To see the body (what you call "codes"), you should expand the package's navigator node and click on the body exposed just below.
Hope that helps,
K.

Can't see package body in SQL Developer version 3.1

Hello,
Have been scouring the boards and google for this issue for quite some time now. I think I have discovered the issue, but would like to see if a work around exists.
Problem:
I am unable to view packages, procs, VIEW DDl, etc. of other users. When a colleague of mine uses Toad, with the EXACT same connection ID and setting, they are in fact able to see all the source code...
What I've found:
Looking around, apparently Toad and SQL Dev work in different ways. Toad apparently uses DBA_SOURCE and DBA_OBJECTS to generate everything.
SQL Dev uses the META_DATA package to retrieve everything. Further, in order to use the meta_data package, I need the grant catalog role, or something like that.
Is there a way to set up SQL Developer to use the same method as Toad to retrieve the code? It's a fact that I WILL NOT receive the catalog permission per the DBAs... I can write out the
select text from DBA_SOURCE where OWNER = 'OWNER' and NAME = 'OBJECT NAME';
But, I would prefer to just be able to use the tree nodes and click on objects to generate all this. Anyone know of any setting for this?

Hi,
No doubt SQL Developer wants to be competitive with Toad but, in terms of raising red flags over inconsistencies in basic functionality, any difference versus SQL*Plus would be more surprising than versus Toad.
DBA_SOURCE and DBA_OBJECTS are public synonyms available in any standard Oracle installation, but you also need the SELECT ANY DICTIONARY privilege to get maximum benefit from them. That lets you view code in another user's schema without having an explicit privilege (like EXECUTE) on a package/procedure/function.
If you already do have such privileges (either SELECT ANY DICTIONARY, or EXECUTE or DEBUG on specific executable objects), and the Code tab is empty, then you will need to provide a test case, as Vadim indicates.
In terms of any case where SQL Developer utilizes DBMS_METADATA, my understanding is the API relies on the SELECT_CATALOG_ROLE privilege if a user does not own or otherwise have an explicitly granted privilege on an object. Developers like to use this API wherever possible in place of writing a script that might break or need maintenance to deal with future versions of the Oracle database.
I have no idea how Toad works, and I probably shouldn't speculate, but here is one scenario that could explain the case you mention without the connection user having any of the privileges noted above. Let's say the Toad client software calls a PL/SQL package that selects from DBA_SOURCE and is installed in a schema that has the SELECT ANY DICTIONARY privilege. All Toad users are granted EXECUTE on this package and therefore inherit SELECT ANY DICTIONARY in the context of running the package. This will work, but at the price of complicating installation of Toad. Also, it doesn't afford an administrator fine-grained control over metadata security.
Regards,
Gary
SQL Developer Team

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.

Can't see package body in SQL Developer version 2.1.1.64

When I go to the object browser, I can see all of the package specs but can't seem to get to the package body. I can access the package body just fine through Toad, so I don't think it is an Oracle user issue. Help?

I can see any user's Package Body when I'm logged into the database as a DBA, so it must be some privilege that you need. The privilege I would have guessed you need is SELECT ANY DICTIONARY but you say you have that privilege. If you were granted that privilege through a role, make sure that the role is active, or that it is a default role.
Another role it might be looking for is EXECUTE ANY PROCEDURE, but I'm not sure. See if you can do these selects, since these are probably the views that SQL Developer is using:
select * from dba_objects where owner = 'some owner' and object_type = 'PACKAGE BODY';
select * from dba_source where owner = ' some owner' and type = 'PACKAGE BODY';Of course, if your database administrator is willing to grant you the DBA role, that ought to do the trick - works for me. Otherwise, you and your DBA may have to try different system privileges until you find the one that works.

Can I create a SQL Developer command script?

I have a frequently repeated process where I:
open SQL Developer (v3.2.2 because of 32-bit requirements),
connect to a previously-defined database connection,
connect to a previously-defined MS Access database connection,
select 3 tables in Access
use the context menu to Copy To Oracle
specify Append on conflict
and I'm done.
I would like to automate that process. Can it be done?
Thanks!

Sorry; I had read "don't see a 'copy to oracle' action" as a deprecation. I see now you meant that as "not [yet] in the command list." I was also reflecting on the migration tools for MS Access, which seemed to have both grown and shrunk in utility through versions 2, 3, and 4 (which we discussed earlier in another topic).
And, no, I do not object to bringing sqlplus features into the new product. What I found confusing was the deprecation of sqlplusw, to be replaced by a product that did not provide the same capabilities. But that's mainly a symptom of "everybody wants improvements without any changes." As long as you're making the improvements, keep up the good work!

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

Using package constant in SQL

I am trying to use a package constant in a query as follows:
SELECT field1 FROM table t WHERE CEIL(sysdate - t.field2) > schema.package.constant
field1 is a name
field2 is a timestamp
constant is an integer indicating the expiration time in days
basically I am trying to find all expired items.
I get the error "ORA-06553: PLS-221: 'constant' is not a procedure or is undefined" on this query.
I use this same query as a cursor in the package itself with no errors.

Unfortunately you cannot directly use package global variables in select statements like this.
One workaround is to use bind variables for that:
<p>
SQL> CREATE OR REPLACE PACKAGE pkg
AS
   myconstant   VARCHAR (20) := 'This is my constant';
END pkg;
Package created.
SQL> VAR myconstant VARCHAR2 (20)
SQL> EXEC :myconstant := pkg.myconstant
PL/SQL procedure successfully completed.
SQL> SELECT :myconstant
FROM DUAL
:MYCONSTANT
This is my constant

Oracle SQL Developer for OSX not able to compile/execute/handle packages?

Hi,
Have been stuck with this for quite some mins now,
When I execute this simple -valid- create package statement in Oracle SQL Developer:
http://www.pastebin.ca/757859
It shows it's not compiled and has errors, when I check the Packages part in Oracle SQL Developer I see this:
http://www.pastebin.ca/757860
The ; after end has been removed by the application. In fact this means I can't do anything with packages in Oracle SQL Developer for OSX?
Is this a known bug?
Or am I doing something wrong?
Any resolving response to this matter would be really appreciated.

Yeah, that bug is in there since stoneage, and is really a no-brainer to fix. Until they don't, we'd be losing time recompiling.
FWIW, everything works fine using the procedure editor for creating, editing and compiling.
Regards,
K.

Package creation in SQL*Plus

DB Version: 10gR2
Sometimes, we have huge Packages, stored procs to compile. I don't want the entire code of Package to be 'Echoed'. I just want to see if a particular package/SP/Function has been Compiled succesfully or not.
So, i set the ECHO to off.
set echo off
set feedback on
set define off
Spool test9.log
create table xyz_tab1
empid          varchar2(15 byte)           not null,
emp_Code       varchar2(15 byte)           not null,
updated_c      varchar2(1 byte)            not null
alter table xyz_tab1 add constraint pk_xyz_tab1 primary key (empid, emp_Code);
CREATE OR REPLACE PACKAGE lms
AUTHID CURRENT_USER
AS
FUNCTION get_emp_x
   (in_code            NUMBER,
   iv_period            VARCHAR2,
   iv_emp_id            VARCHAR2,
   id_date            DATE
   RETURN VARCHAR2;
end ;
spool off;But it doesn't say which procedure got created (or errored in compilation)
SQL > drop table xyz_tab1;
Table dropped.
MANU:rac > @test.sql
Table created.
Table altered.
Package created.
SQL >How can I get the Package/SP name to be printed ?

you could use PROMPT:
PROMPT Create Package: lms
CREATE OR REPLACE PACKAGE lms
AUTHID CURRENT_USER
AS
FUNCTION get_emp_x
   (in_code            NUMBER,
   iv_period            VARCHAR2,
   iv_emp_id            VARCHAR2,
   id_date            DATE
   RETURN VARCHAR2;
end ;
{Code}
Output:
Create Package: lms
Package created.
Edited by: jowahl on 19.10.2010 13:35

Reading package contents in SQL Plus

Hi,
I'd asked a similar question last week, but didn't see it responded to with a proper reply.
Ive created a package in SQL Plus, and much like you use the DESCRIBE command to see info on tables that are created, I'd like to see the contents and script of my package to verify some contents of it.
How can I do that? Or can I do that?
I've read this:
http://download-west.oracle.com/docs/cd/A87860_01/doc/appdev.817/a77069/08_packs.htm#4376
But it doesn't explain within how to go about doing that if indeed that is possible at all. Would anyone that knows if this can be done please reply with the way to do it?
Thanks!

Hi,
You can query USER_SOURCE (or ALL_SOURCE, at your choice) to get what you need.
Consider:
SQL> create or replace package small is
2    procedure Test;
3 end;
4 /
Package created.
SQL> create or replace package body small is
2
3 procedure Test is
4 begin
5    null;
6 end;
7
8 end;
9 /
Package body created.We just created simple package, for demonstration purposes. Now, we're about to view its source:
SQL> column text format a100
SQL>
SQL> select line, text
2    from user_source
3   where name = 'SMALL'
4     and type = 'PACKAGE'
5   order by line;
      LINE TEXT
         1 package small is
         2   procedure Test;
         3 end;
SQL> select line, text
2    from user_source
3   where name = 'SMALL'
4     and type = 'PACKAGE BODY'
5   order by line;
      LINE TEXT
         1 package body small is
         2
         3 procedure Test is
         4 begin
         5   null;
         6 end;
         7
         8 end;
8 rows selected.
SQL>Alternatively, you can make use of DBMS_METADATA package.
Regards.

Unable to see packages / triggers etc in SQL Developer 3.1.07

Hi
The user has SELECT_CATALOG_ROLE role granted but still cannot see packages of other users.
Is there anything else I need to grant to this user in order that it may have visibility?
Can't see package body in SQL Developer version 3.1 covers it to a point but I need more please.
Thanks.
This user has SELECT AND TABLE and CREATE SESSION.
When I run this on the database connecting as this user I get rows returned which tells me its a SQL Developer thing?
select text from dba_source where name like '%a_package_name%';
Which could also mean I need to reinstall the damn thing doesn't it?
SQL Developer 3.1.07
DB 11.2.0.3.0
Edited by: 869150 on Nov 15, 2012 6:41 AM
Edited by: 869150 on Nov 15, 2012 7:07 AM
Edited by: 869150 on Nov 15, 2012 7:34 AM

Hi,
The SELECT_CATALOG_ROLE should be sufficient as far as privileges go. I cannot recall at the moment, but there may well have been a bug or two fixed between 3.1.07.42 and 3.2.20.09.87 that solves this. Please try upgrading.
Regards,
Gary
SQL Developer Team

Why does SQL Developer insist on opening up the package header?

When expanding a package (clicking the '+') SQL Developer keeps opening up the package header (at least the first time you click it). I'm very rarely interested in viewing the header and it's annoying to have all those tabs open.

See SQL Dev 2.1 RC1 - Expanding packages under Schema Browser
Don't know if dev filed a bug against this, so to be sure you'd have to log a SR on Metalink/MOS.
Regards,
K.

Pldoc utility to document packages created in sql developer

Similar Messages

Maybe you are looking for