How to debug package in sql developer?

Hi,
I need to debug one of procedures in my package in sql developer version 1.5.5. In Debugging log, I got the following:
Connecting to the database <databasename>.
Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '127.0.0.1', '2754' )
ORA-01031: insufficient privileges
ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
ORA-06512: at line 1
This session requires DEBUG CONNECT SESSION and DEBUG ANY PROCEDURE user privileges.
Process exited.
Disconnecting from the database <databasename>.
I have granted both DEBUG CONNECT SESSION and DEBUG ANY PROCEDURE user privileges from SYS as the following:
GRANT DEBUG ANY PROCEDURE TO ESM_OWNER;
grant DEBUG CONNECT SESSION to ESM_OWNER;
However, I still get the same error. What did I do wrong? I really appreciate any help to solve my problem.
Thanks in advance!!!
Cindy

I logged in as ESM_Owner. Now I got the following errors:
Connecting to the database <databasename>.
Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '127.0.0.1', '1131' )
ORA-30683: failure establishing connection to debugger
ORA-12541: TNS:no listener
ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
ORA-06512: at line 1
Process exited.
Disconnecting from the database <databasename>.
Edited by: user13375135 on Sep 22, 2010 1:31 PM

Similar Messages

How to start listener in sql developer for remote debug

how to start listener in sql developer for remote debug ? Since the new version 1.1.0.23 is different with the old version for remote debug, I don't know how to start the listener on the new version for remote debug.
even follow the user guide below and not work . Experts on sql developer please help me with this.
Remote Debugging
To debug a procedure or function for a connection where the database is on a different host than the one on which you are
running SQL Developer, you can perform remote debugging.
Remote debugging involves many of the steps as for local debugging; however, do the
following before you start the remote debugging: Use an Oracle client such as SQL*Plus to issue the debugger connection command. Whatever
client you use, make sure that the session which issues the debugger connection commands is the same session which executes your PL/SQL
program containing the breakpoints.
For example, if the name of the remote system is remote1, use the following SQL*Plus command to open a
TCP/IP connection to that system and the port for the JDWP session:
EXEC DBMS_DEBUG_JDWP.CONNECT_TCP('remote1', '4000'); The first parameter
is the IP address or host name of the remote system, and the second parameter is the port number on that remote system on which the debugger
is listening.
Right-click the connection for the remote database, select Remote Debug, and complete the information in the Debugger - Attach
to JPDA dialog box. Then, follow the steps that you would for local debugging (for example, see Debugging a PL/SQL Procedure).
Debugger - Attach to JPDA This dialog box is displayed when you right-click a database connection name and select Remote Debug.
Use this
dialog box if you are using the Sun Microsystem's Java Platform Debugger Architecture (JPDA) and you would like the debugger to listen so
that a debuggee can attach to the debugger.
For more information about remote debugging, see Remote Debugging.
Host: Name or IP address of
the remote host on which SQL Developer should listen for the database to connect.
Port: Listening port number on the remote host. You can
choose any valid port number that is not in use by another process.
Timeout: The number of seconds that SQL Developer will wait for the
remote database to make a debugging connection. Don't Show Dialog Box Before Connecting: If this option is checked, this dialog box will not
be displayed before future connections for remote debugging

You're not the only one:
Not able to start remote debug listener
Re: remote debug question at version 1.1.0.23 64

Debugging in Oracle SQL Developer

I would like to know how to debug my PL / SQL programs in the Oracle SQL Developer program using breakpoints and such. I've never known how to use debugging tools like this and since this program provides this kind of feature, I was wondering if anyone on here might be able to shine some light on this for me. How are these used? How could I use them to say, figure out what the value of a given variable might be on line whatever? Etc.
One reason I'm setting out to learn this is because I'm tired of typing DBMS_OUTPUT.PUT_LINE all the time. I would think that there must be a better way than this.
Lastly (and while we're on that subject), what would cause SQL Developer to not output a DBMS_OUTPUT.PUT_LINE line? I've given this a string of text to output to the monitor and it's not working. It's in the DECLARE section (thinking I could place these almost anywhere my tiny little heart desired, but apparently, I'm wrong?)
Again, any insight is appreciated.

- K - :
Oh, I get it... We had another pesky drop-out fishing for homework cheats again, right?
Here's a suggestion to make this forum (you know, a place where people come together who all think differently about things both deep and shallow) somewhat more accepting and useful a place for idiots like me who might happen to overlook an apparently obvious "Help" menu item with the glowing neon-colored label heading of "Table of Contents": instead of wasting your own time (let alone, others) by posting silly responses that serve arbitrary agendas for the sake of inflating one's ego and online rep points due to having a bad high school experience, why not just instead take a high road (all the real Oracle kings around here hopefully take) and either ignore the response altogether or post something at least 1% useful. Sound like a plan? Great! For instance, why not inquire about why someone posted something that might not make sense to you? It's an amazing concept...
Because after all...
"+I'm often perplexed about the "answers" we get. Seems like you never posted your suggestions.+"
...doesn't do a lot for people who come across this thread in similar straights or perspective I was in at the time of creating it.
That said, something like...
"+Since you're using Oracle SQL Developer, you should have a 'Help' menu item near the top of the window. Click on it and then click on 'Table of Contents'. Proceed to do as Jim suggested by locating the topic 'Running and Debugging Functions and Procedures'. In that section of the contents, you will find more information about debugging your program, tips and tricks, etc. If this doesn't help you or if you're unsure about something in general, feel free to post back and we'll try to help you further.+"
...is much more helpful and succinct. It's welcoming, objective, and very informative (not that Jim's response wasn't).
On that note, Jim, I do appreciate your response. When I first read your suggestion, I had misinterpreted what you proposed in the heat of the moment. Above all else, I also had some things going on around me that were distracting me. Thanks again. I'm reading the topic right now...

Creating Data Mining PL/SQL Package in SQL Developer

hi,
i have built a model and want to create a PL/SQL package.
in SQL developer, i launch a "New Gallery", select "All Items" from the drop-down menu, and click on "Database Objects". but in the right window pane, i am not able to see "Data Mining PL/SQL Package" in the options.
can somebody please tell me how to fix this?
thanks!

To verify that Oracle Data Mining PL/SQL Package extension is properly installed, please do the following:
Select Menu Help->About, click on "Extensions" tab. Look for "Oracle Data Mining PL/SQL Package" in the Name column ( you can sort it).
If it is, please make a note of the version installed and post it here as well as the SQL Developer version.
Just to clarify, you don't see "Data Mining PL/SQL Package" item in the "Database Objects" at all or is it grayed out?
Thanks

ORA-01722 when opening a package in SQL Developer 1.2 with oracle 9iR1

Hi,
I use SQL Developer with Oracle Database 9i release 1.
When I open a package in SQL Developer 1.2 (or 1.5) for editing, I receive the error ORA-01722. The package successfully opens but this message, which pops everytime, is really annoying.
I monitored the requests sent by SQL Developer and it seems that the following request is responsible of the error :
SELECT LINE,POSITION,TEXT,ATTRIBUTE FROM USER_ERRORS WHERE TYPE=:1AND NAME=:2
Notice there are no spaces between ':1' and 'AND'. When executing 'by hand' the request with SQL Developer, it asks for the value of '1AND' bind variable and the value of '2'. Then, it fails to execute with... ORA-01722.
Is it possible to avoid this bug ?
Thank you for your help.

We're doing rolling 2 week releases until production. Expect something new next week.

How to do profiling in sql developer?

how to do profiling in sql developer?
also-can somebody plz suggest a gud site for information on pl/sql code profiling.

You might want to ask your SQL Developer-related question in the SQL Developer forum: SQL Developer
gud site for information on pl/sql code profiling.Online Oracle Documentation:
http://download.oracle.com/docs/cd/E11882_01/appdev.112/e10472/tuning.htm#LNPLS01214
and/or
http://www.oracle-base.com/articles/9i/DBMS_PROFILER.php
Edited by: hoek on May 19, 2010 12:55 PM

Creating PL/SQL package in SQL Developer 4.0.0.12

Hi,
I have built a model in SQL Developer 4.0.0.12 and I want to create it's PL/SQL package.
In ODMiner 11.1.0.4 from "Tools" > "Create pl/sql package" I can get a script for creating package and every thing is OK.
but in SQL Developer I select "Deploy" from every node's context menu and it generates a folder containing some scripts related to every node. I don't see any relevant script for creating any package.
How can I create relevant PL/SQL package from my workflow?
Thank you for any help you can provide in this situation.

Please refer to this White paper for how to generate PL/SQL package for workflow deployment:
Oracle Data Miner (Extension of SQL Developer 4.0)
Generate a PL/SQL script for workflow deployment
http://www.oracle.com/technetwork/database/options/advanced-analytics/odmrcodegenwhitepaper-2042206.pdf

Setting/using a variable in a package in SQL Developer

The 10g db I'm working with has a package that contains a variable and routines to set and get the value of the variable. The variable is used in a number of views to tailor data displayed according to the variable value. This all works well in applications, which set the variable after a connection is opened and then issue queries against the views, and then close the connection.
This also works well in Toad - I can open Toad, run a package routine to set the value and then open views (or run queries against views) in Toad to see how different variable values effect the data displayed. The package variable maintains its value so long as Toad is open, which seems to imply that Toad keeps a connection open.
But I can't use SQL Developer in the same way. I can run the SET routine, but it has no effect in on views subsequently run. When running the SET routine, setting the value to 1, the output is:
Connecting to the database HERC DB.
Process exited.
Disconnecting from the database HERC DB.
I can then run the GET routine, but the value of the variable is always zero:
Connecting to the database HERC DB.
v_Return = 0
Process exited.
Disconnecting from the database HERC DB.
The implication seems to be that a connection is made, the routine is run and then the connection is closed. The closing of the connection resets the variable. Is there some way I can have SQL Developer behave like Toad, such that the package variable value is maintained for my SQL Developer session? I've looked at connection roperties and application preferences, but I've not seen anything that seems to be related keeping a connection open.
BTW, I have tried the "connection startup script", but to no avail. Perhaps I've doen this improperly; the script simply attempts to invoke the package set routine, like so: myPkg.set_identity(1)
Thanks.
Edited by: user483973 on Oct 20, 2009 9:20 AM

When running stored PL/SQL through the IDE context node or editor, indeed a new session is opened and consequently closed on completion after committing. Although great for having the IDE free to continue working, it does have its drawbacks when you want variables to persist and changes to be visible in the IDE before committing.
To prevent the new session and the commit, just call the PL/SQL from a worksheet (in a call, query or anonymous block).
The startup script should work in that respect, but make sure to wrap your call in an anonymous block, else you'll get a syntax error.
Hope that helps,
K.

How to debug all PL/SQL code.

Forms 6i.
I know debugging in general.
But I want to debug every pl/sql code in my form, not only a certain trigger.
How to do this?
I tried: DEBUG -> Trigger -> "Every Statement". Trigger-Body: "raise debug.break;", but I get following error message:
PDE-IKP008 » The current source location is undefinedEdited by: WoMo on Sep 11, 2012 5:03 AM
Edited by: WoMo on Sep 11, 2012 5:38 AM

Hi,
Have you tried : Tools - Database Unload.
There are several types of objects which you can choose - package and package bodies.
I usually put them into a single file. I haven't tried to do so into multiple files.
If you need to get them into different files, use the Unload feature from the Connection - Package - right click and choose Unload. But you need to do this one by one for each package.
Btw, it is not Import. The correct term for what you want is to Export, here in SQL Dev refers to Unload.
Import is used when you want to put something from outside source into the Database.
Regards,
Buntoro

Unit testing packages in sql developer

It appears that the specify parameters window is blank for packaged functions which means the test call fails when run. Is this a grant or synonym issue ( or something similar ) or is there an issue with testing packages via the unit test interface of sql developer. Thanks in advance.

Seems that you cannot right click on the packaged schema object from the schema connection i.e. you have to create the test from the unit test tab and then choose the object type i.e select packages and then the packaged function or procedure. This method results in the Specify Parameters window having the correct signature displayed. Procedures or methods can be created via the unit test tab or the active connection tab.

Issue with viewing packages in SQL Developer EA2

I posted a message when EA1 came out asking why I couldn't see the package's body in EA1.
Now I couldn't see the any thing under '$schema/packages' in EA2.
Does anybody know why?
My OS: Windows XP Pro SP2
Oracle: 9i
SQL Developer version: EA2

In version 9 a very simple sql is supposed to be executed:
SELECT OBJECT_NAME, OBJECT_ID,
DECODE(STATUS, 'INVALID', 'TRUE', 'FALSE') INVALID,
'TRUE' runnable
FROM SYS.ALL_OBJECTS a
WHERE OWNER = :SCHEMA
AND OBJECT_TYPE = 'PACKAGE'
AND SUBOBJECT_NAME IS NULL
-- for packages
SELECT OBJECT_NAME, OBJECT_ID,
DECODE(STATUS, 'INVALID', 'TRUE', 'FALSE') INVALID,
'TRUE' runnable
FROM SYS.ALL_OBJECTS o
WHERE OWNER =:SCHEMA
AND OBJECT_NAME = :PARENT_NAME
AND OBJECT_TYPE = 'PACKAGE BODY'
-- for package bodies
If either of these doesn't return anything in worksheet, then the problem is right there. However, this part hasn't been changed since EA1 (The only change was adding SYS.DBA_PLSQL_OBJECT_SETTINGS requirement for version >=10). I can't reproduce the problem: in 9i scott sees any procedure/package I create.

Problems with debugging in Oracle sql developer

Dear all,
I have a stored procedure with about 3500 lines of code. The SP is calling some other SP's , so altogether around 30,000 lines of code is to executed.
I have some delete statements in the beginning of my SP.
Till nw i was able to debug and run this SP.
But nw I am facing a strange problem.
I can run the SP.
But if i try to debug it , it gets hanged after the delete statement and does not move forward.
So i moved all that statements to another SP and I call the new SP from my present one.
In this way If i debug , after calling the newly created SP , my main Sp does not recognise the break points , and it just finishes execution ..
Can any one help me on this.
Thanks in Advance,
Kurian Simon

Simon,
Did you move the breakpoint, and once you'd moved the lines of code, did you recompile, using compile for debug? Also, it's important to do compile for debug on all the program units you want to debug, otherwise SQL Developer will just step over the units not compiled for debug.
Sue

How input korea in pl/sql developer

I input korea in "the sql edit windows" of pl/sql developer 7 ,but it show "??"
Could you tell me how to resovle this problem
my os is windows XP ,oracle is 10.2.0.3
my NLS_LANG=ZHS16CGB231280
it should be store korea character.

I had never heard of this either, but I think this is the web site: http://www.allroundautomations.nl/plsqldev.html.
Perhaps you should review the product docs or contact support.
Greg

How create new user in sql developer?

so i tried creating a new user in SQL developer, under the worksheet section, for a 12c database
create user Hares1
identified by book;
but I get this error
SQL Error: ORA-65096: invalid common user or role name
Sorry I know this is a generalized question. I only learned how to actually connect today - any help of a next step would be appreciated.

so i tried creating a new user in SQL developer, under the worksheet section, for a 12c database
create user Hares1
identified by book;
but I get this error
SQL Error: ORA-65096: invalid common user or role name
The 'next step' is RTFM. Sorry but for 12c multitenant you simply MUST read the documentation about the new multitenant architecture.
Your 'problem' is not creating a user with sql developer - it is how to create users in 12c.
See my extended comments and reply in this thread (and several other threads I reference there) which addresses your exact problem
12c: ORA-65049: creation of local user or role is not allowed in CDB$ROOT
http://www.oracle.com/pls/db121/homepage
I suggest you first read chapters 17 and 18 of the Concepts doc about the new multitenant architecture of 12c.
http://docs.oracle.com/cd/E16655_01/server.121/e17633/part_consol.htm#CHDGDBHJ
The 'Common Users in a CDB section answers your question
>
The name of every user-created common user must begin with the characters c## or C##. (Oracle-supplied common user names do not have this restriction.)
>
There are two types of users in 12c: common and local. You need to understand the difference between them.
Until you read those doc chapters you won't understand these terms: common user, local user, CDB, PDB, root container, and many others.
As I said in that other thread:
You will NOT be successful working with 12c unless you have read and understand the new multitenant architecture that it uses. There are very simple things (connecting, startup/shutdown, creation of users, grants to users, etc) that just don't work the same old way anymore.
If you try to just 'plow through it' without reading about it you will likely get an exception that you won't understand and it will likely use a term (CDB$ROOT) that you won't understand. Then you will hunt all over (or worse, ask in the forums) to find out about that term.
Yes - I know how adverse some people are to RTFM replies. But for 12c multitenant it is mandatory to read the docs no matter how expert you may be in previous Oracle versions.

Privileges to view packages in Sql Developer

I'm sure this has been covered before, but I cannot view a package (spec or body) unless Execute has been granted.
Create any procedure will allow spec/body to be displayed.
Is this as intended?
I searched the forum and elsewhere, and found comments and workarounds. What I am looking for is the actual rules that determine when a package can be viewed.

You could probably connect to the database with toad, have the session traced, and click around and view some packages to see what sql was run, then do the same with sql developer. My guess would be the views that each tool is using by default, perhaps toad goes ofter dba_objects/source and maybe sql developer goes after all_objects/source, something like that. so with a permission like select any view or select any table, you might see different results depending on the tool, Purely speculation on my part.

How to debug package in sql developer?

Similar Messages

Maybe you are looking for