Problems debugging PL/SQL [JDev 9.0.3.1035 Prod]

When debugging a PL/SQL procedure/function JDev creates a temporary procedure, usually called JDEV_TMP_PROC_n. From time to time it happens, that this procedure remains in the database after termination. In this case, it can not be dropped neither with JDev nor with SQL*Plus. Any ideas?

Assuming the Debug session runs to completion or successfully "terminates" the temporary procedure should be dropped. If the client is abnormally terminated (for example, killing the client from the task manager), the temporary procedure may remain until the database discovers that the client is no longer connected and cleans up its session. Once that happens, the locks on the procedure should be removed, and you should be able to drop the procedure.
Is your debugging session not running to completion for some reason?
-- Brian (JDev Team)

Similar Messages

Problem displaying data and Smart data debugging pl/sql

I'm using JDev 9.0.5.1 build 1065, when i debug a PL/SQL function from the connections navigator, it allows me to stop at a breakpoint, but it doesn't display anything in the data or smart data panes. Do i need to change a config setting somewhere ? The PL/SQL is in an Oracle 8i database, does it need to be 10g for this functionality to work ?
Thanks
Alistair

Are you trying to debug ASP.NET or a windows app or direct debugging?
If a windows app or direct debugging, follow these steps:
http://cshay.blogspot.com/2006/07/plsql-debugger-in-visual-studio.html
If ASP.NET, follow part of the steps above to configure, but then use these steps for External App debugging:
Debugging PL/SQL from .Net 2003

Problem using a SQL database Catalogue to insert data to a table

I am developing with Version:
10.3.1.0, Build: #99765....
as part of a step in my process I need to store some data in an audit table.
I have setup the SQL Catalogue entry and then use the following code:
sentMail is defined as a local variable
sentMail = RSPCA.Resources.RSPCA.R_SENTEMAIL()
sentMail.sentemailBody = sendInternalRequest.htmlbody
sentMail.sentemailDatesent = Fuego.Lang.Time
sentMail.sentemailSubject = subject
sentMail.sentemailTo = creation.participant.email
sentMail.sentemailType = "People"
store sentMail
This works if I comment out this line:
sentMail.sentemailBody = sendInternalRequest.htmlbody
The issue I'm having maybe something to do with the size of the data, in oracle the field is a varchar2(4000) and it looks like the catalogue treats it as a String(4000), if I make sure I only put around 1500 characters in the field it works, but as soon as I put all in from my test data (about 2300) it fails with this message:
The method 'CIL_sendToHQ' from class 'EstablishmentManagement.EMMaintainPeopleProcess.Default_1_0.Instance' could not be successfully executed.
Caused by: [BEA][Oracle JDBC Driver][Oracle]ORA-01461: can bind a LONG value only for insert into a LONG column
Caused by: [BEA][Oracle JDBC Driver][Oracle]ORA-01461: can bind a LONG value only for insert into a LONG column
fuego.lang.ComponentExecutionException: The method 'CIL_sendToHQ' from class 'EstablishmentManagement.EMMaintainPeopleProcess.Default_1_0.Instance' could not be successfully executed.
     at fuego.component.ExecutionThreadContext.invokeMethod(ExecutionThreadContext.java:519)
     at fuego.component.ExecutionThreadContext.invokeMethod(ExecutionThreadContext.java:273)
     at fuego.fengine.FEEngineExecutionContext.invokeMethodAsCil(FEEngineExecutionContext.java:219)
     at fuego.server.execution.EngineExecutionContext.runCil(EngineExecutionContext.java:1278)
     at fuego.server.execution.microactivity.ComponentExecutionMicroActivity.runCil(ComponentExecutionMicroActivity.java:126)
     at fuego.server.execution.microactivity.ComponentExecutionMicroActivity.execute(ComponentExecutionMicroActivity.java:84)
     at fuego.server.execution.microactivity.MicroActivityEngineExecutionHandler.executeActivity(MicroActivityEngineExecutionHandler.java:57)
     at fuego.server.execution.ImmediateActivity.execute(ImmediateActivity.java:42)
     at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
     at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
     at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
     at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
     at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
     at fuego.server.execution.DefaultEngineExecution.executeAutomaticWork(DefaultEngineExecution.java:62)
     at fuego.server.execution.EngineExecution.executeAutomaticWork(EngineExecution.java:42)
     at fuego.server.execution.ToDoItem.executeAutomaticWork(ToDoItem.java:251)
     at fuego.server.execution.ToDoItem.run(ToDoItem.java:536)
     at fuego.component.ExecutionThread.processMessage(ExecutionThread.java:775)
     at fuego.component.ExecutionThread.processBatch(ExecutionThread.java:755)
     at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:142)
     at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:134)
     at fuego.fengine.ToDoQueueThread$PrincipalWrapper.processBatch(ToDoQueueThread.java:450)
     at fuego.component.ExecutionThread.work(ExecutionThread.java:839)
     at fuego.component.ExecutionThread.run(ExecutionThread.java:408)
Caused by: fuego.components.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-01461: can bind a LONG value only for insert into a LONG column
     at fuego.sql.TableSQLObject.implicitStore(TableSQLObject.java:409)
     at fuego.sql.TableSQLObject.store(TableSQLObject.java:340)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at fuego.lang.JavaClass.invokeMethod(JavaClass.java:1410)
     at fuego.sql.SQLObject.invoke(SQLObject.java:364)
     at fuego.lang.Invokeable.invokeImpl(Invokeable.java:234)
     at fuego.lang.Invokeable.invokeDynamic(Invokeable.java:188)
     at EstablishmentManagement.EMMaintainPeopleProcess.Default_1_0.Instance.CIL_sendToHQ(Instance.xcdl:100)
     at EstablishmentManagement.EMMaintainPeopleProcess.Default_1_0.Instance.CIL_sendToHQ(Instance.xcdl)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at fuego.component.ExecutionThreadContext.invokeMethod(ExecutionThreadContext.java:512)
     ... 23 more
Caused by: java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-01461: can bind a LONG value only for insert into a LONG column
     at albpm.jdbc.base.BaseExceptions.createException(Unknown Source)
     at albpm.jdbc.base.BaseExceptions.getException(Unknown Source)
     at albpm.jdbc.oracle.OracleImplStatement.execute(Unknown Source)
     at albpm.jdbc.base.BaseStatement.commonExecute(Unknown Source)
     at albpm.jdbc.base.BaseStatement.executeUpdateInternal(Unknown Source)
     at albpm.jdbc.base.BasePreparedStatement.executeUpdate(Unknown Source)
     at fuego.jdbc.FaultTolerantPreparedStatement.executeUpdate(FaultTolerantPreparedStatement.java:623)
     at fuego.sql.TableSQLObject.insert(TableSQLObject.java:626)
     at fuego.sql.TableSQLObject.implicitStore(TableSQLObject.java:391)
     ... 39 more
Edited by: user10778731 on 21-Jan-2010 06:17

Suspect you're not going to like this answer, but I never use the store() method for a database heir object anymore.
The store() database method has been broken and then fixed and then broken again on too many release cycles to trust that it will work consistently as MPs/Hotfixes are applied. I'd suspect that your "String(4000)" problem might also be related to using the store() method.
Others will probably disagree, but only use the OOTB PBL (JDBC) SQL or Dynamic SQL in the PBL logic. In your case, I think you might be best served by using Dynamic SQL. With Dynamic SQL you don't run into the shortcomings of JDBC SQL (String(4000) might be one of them) and you can then test / debug your SQL in your favorite DB tool of choice first (e.g. Toad, Squirrel, Sql Plus). Once successfully tested, you can then paste it back into your PBL.
Dan

Probs Debugging PL/SQL proc JDev903

Im trying to debug PL/SQL functions in JDeveloper 9.0.3.
Issue N1. In Run PL/SQL window JDev adds schema name to my function and PL/SQL block fails to compile. Im manually deleting prefix from my function and block is compiled successfully.
Then an error happened: PLS-00302: component 'JDEV_TMP_PROC_1' must be declared
Please advice
Debugger attempting to connect to database.
Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
Executing PL/SQL: DECLARE
id VARCHAR2( 30 );
BEGIN
id := DBMS_DEBUG.initialize( '24.27.75.30:1036303964414', 1 );
DBMS_DEBUG.debug_on( TRUE );
END;
Debugger connected to database.
Deadlock detection is not supported by the debuggee virtual machine.
Executing PL/SQL: BEGIN MY_SCHEMA."JDEV_TMP_PROC_1"(); END;
ORA-06550: line 1, column 11:
PLS-00302: component 'JDEV_TMP_PROC_1' must be declared
ORA-06550: line 1, column 7:

JDev can debug with Oracle 8.1.7 or later.
Is the PL/SQL you want to debug in the same schema as you are connecting? Because you mentioned schema names, I wonder if there may be a bug with trying to debug PL/SQL in a schema other than the one you are connected to. If so, can you try creating connection as the owner of the PL/SQL and see if that works?
Thanks!
-- Brian (JDev Team)

How to debug PL/SQL functions? Passing parameter and debugger error

Hi,
How to debug a PL/SQL function in JDeveloper? There are two problems with it:
1) Don't see how it's possible to pass parameters required by function call (in the dialog opening after Debug -> Debug FUNCTION_NAME)
2) In a function returning table_name%ROWTYPE (and having a record declaration for table_name%ROWTYPE), debug gives error:
PLS-00103: Encountered symbol "/" when expecting one of ... in line
v_Return PL/SQL RECORD;
Debugging procedures works as expected.
Found a similar question without answer here:
Debugging PL/SQL with parameters

Check
http://www.oracle.com/technology/obe/obe9051jdev/plsqlobe/obeplsql.htm#t2
Frank

Debugging PL/SQL procedures with JDeveloper ?

Hi,
does anyone know if it is possible to debug PL/SQL procedures and packages with JDeveloper ? I'm using a 9.0.1.2.0 database but JDeveloper returns the error "The target VB_TEST could not be started because the database version does not support debugging." when I try to debug a PL/SQL procedure.
If it is not possible, does anyone know a good alternative ?Oracle Script Debugger is not available anymore at technet.

I need to retrive data from PL/SQL stored procedures. I am using the DynamicSQL component (2nd workaround) to retrive data from PL/SQL stored procedures. 
I am having some problems. 
This is the code I am running in Fuego Studio 5.5 SP 11 Build #71108: 
dynamicSQL as Fuego.Sql.DynamicSQL 
iterator as Iterator(Any[Any]) 
sentence as String 
implname as String 
dynamicSQL = Fuego.Sql.DynamicSQL() 
implname = "conexionORBPAU" 
sentence = "var result REFCURSOR; " + 
"exec :result_cursor := pkg_audbpm_bpaasig_indicador.prgetsingle(9999);"; 
iterator = executeQuery(DynamicSQL, sentence, implname, inParameters : []); 
And, this is the error: 
java.sql.SQLException: Falta el parametro IN o OUT en el indice:: 1 
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146) 
oracle.jdbc.driver.OraclePreparedStatement.processCompletedBindRow(OraclePreparedStatement.java:1681) 
 at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3280) 
 at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3329) 
 at fuego.jdbc.FaultTolerantPreparedStatement.executeQuery(FaultTolerantPreparedStatement.java:579) 
 at fuegoblock.sql.DynamicSQL.executeQuery(DynamicSQL.java:340) 
... 
This is the code of the PL/SQL in the Oracle DB: 
CREATE OR REPLACE PACKAGE PKG_AUDBPM_BPAASIG_INDICADOR IS 
TYPE cursor_type IS REF CURSOR; 
 FUNCTION prGetSingle 
 ( 
 p_ID_ASIG_INDICADOR IN NUMBER 
 ) 
 RETURN cursor_type; 
END PKG_AUDBPM_BPAASIG_INDICADOR; 
is my code OK? Any ideas? 
Thanks in advance.

Debug in sql server 2012

Hi,
I have 3 sql server (2005,2008,2012) In 2005 and 2008 remote debug (from sql management studio installed on the client) works without problems.
In sql 2012 debugging only works on sql management studio installed locally, why?
The server 2012 and the client are in the same domain, and both have the firewall disabled
to connect to all 3 I always use the same sql server management studio 2014
thanks!

Hi matti157,
As your description, you fail to use remote T-SQL Debugger in the instance of SQL Server 2012. Please help to post the error information here for analysis. Based on my research, the issue could be due to the RPC or authentication issue. You could pay attention
to the points below to troubleshoot your issue.
1.It is recommended to verify if the configuration of the T-SQL Debugging was done correctly. To verify that, you can follow the steps from the link:
http://msdn.microsoft.com/en-us/library/cc646024(v=sql.100).aspx
2.Verify if the SQL Server Management Studio was started with Administrator permissions (Run as Administrator);
3.Verify if the account used to connect remote to T-SQL Debugger has the right of ‘sysadmin’ on SQL Server Instance and if it is in the Local Administrators Windows Group
4.Verify if the following services are started:
a.TCP/IP NetBIOS Helper;
b.Remote Registry;
c.RPC Service;
5.Verify if DCOM is active on the server and client. To do that please follow the steps described in the link:
http://technet.microsoft.com/en-us/library/cc771387.aspx.
6.If you have intermediary devices between SQL Server and client, it is absolutely necessary to configure on this devices the necessary rules and ports , so the communication between the SQL Server and the client not to be blocked;
7.To verify if you have any issues with the permissions at DCOM level, you can activate the DCOM logging using the following link:
http://support.microsoft.com/kb/892500. To verify if the DCOM works fine you can do the test from the following article
http://support.microsoft.com/kb/259011/en-us.
For more information about the process, please refer to the article:
http://blogs.technet.com/b/beatrice_popa/archive/2012/11/28/quot-unable-to-start-t-sql-debugging-could-not-attach-to-sql-server-process-on-databasename-the-rpc-server-is-unavailable-quot.aspx
Regards,
Michelle Li

How do I connect the debugger for remotely debugging PL/SQL?

Hi everyone,
Remotely debugging PL/SQL from JDeveloper and SQL Developer is something I have tried unsuccessfully to do.
The steps I took were to right-click my connection, select Remote Debug... and specify "4000" for the Port and "n.n.n.n" for the Local address which seems to correctly start the listener. (I used ipconfig to double-check the address.) Then, I run the anonymous block you see below.
begin
dbms_debug_jdwp.connect_tcp( 'n.n.n.n', 4000 );
end;
But, I always get the following error:
Error starting at line 18 in command:
begin
dbms_debug_jdwp.connect_tcp( 'n.n.n.n', 4000 );
end;
Error report:
ORA-30683: failure establishing connection to debugger
ORA-12535: TNS:operation timed out
ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
ORA-06512: at line 2
30683. 00000 - "failure establishing connection to debugger"
*Cause:    An error was indicated when trying to establish a connection
           to a debugger. Usually a TNS error will display along with
           this message to further explain the problem, although this
           TNS error will likely be hidden if you choose to trap the error.
*Action:   Correct the indicated parameter value and try again.
Additionally, my firewall in Windows 7 is disabled, and I work remotely from home via VPN.
The instructions are thatI followed: Sue's Blog... again...: Remote Debugging with SQL Developer.
Any help would be greatly appreciated. Thanks!
James

I found the answer.
Object classes are missing.
The right insert code is down but I have a new question.
-How can I assign Resource acces to user in PL/SQL?
Right insert code:
declare
vn_retval pls_integer;
emp_session dbms_ldap.session;
emp_dn varchar2(256);
emp_array dbms_ldap.mod_array;
emp_vals dbms_ldap.string_collection ;
vv_ldap_host varchar2(256);
vv_ldap_port varchar2(256);
vv_ldap_user varchar2(256);
vv_ldap_passwd varchar2(256);
vv_ldap_base varchar2(256);
begin
vn_retval := -1;
vv_ldap_host := 'XXXXXXX';
vv_ldap_port := '389');
vv_ldap_user := 'LDAP_USER';
vv_ldap_passwd:= 'LDAP_PASSWD';
vv_ldap_base := 'LDAP_BASE';
dbms_ldap.use_exception := true;
-- Initialize ldap library and get session handle.
emp_session := dbms_ldap.init(vv_ldap_host, vv_ldap_port);
-- Bind to the directory
vn_retval := dbms_ldap.simple_bind_s(emp_session, vv_ldap_user, vv_ldap_passwd);
-- Process New Entry in the database
-- Create and setup attribute array for the New entry
emp_array := dbms_ldap.create_mod_array(4);
emp_vals(1) := 'NAME';
dbms_ldap.populate_mod_array(emp_array, dbms_ldap.mod_add, 'cn', emp_vals);
emp_vals(1) := 'NAME';
dbms_ldap.populate_mod_array(emp_array, dbms_ldap.mod_add, 'sn', emp_vals);
emp_vals(1) := 'top';
emp_vals(2) := 'person';
emp_vals(3) := 'organizationalPerson';
emp_vals(4) := 'orcluserv2';
emp_vals(5) := 'orcluser';
emp_vals(6) := 'inetOrgPerson';
dbms_ldap.populate_mod_array(emp_array, dbms_ldap.mod_add, 'objectclass', emp_vals);
emp_vals.delete;
emp_vals(1) := 'NAME' || '1';
dbms_ldap.populate_mod_array(emp_array, dbms_ldap.mod_add, 'userpassword', emp_vals);
-- DN for Entry to be Added under 'ldap_base'
emp_dn := 'cn=' || 'NAME' || ', ' || vv_ldap_base ;
-- Add new Entry to ldap directory
vn_retval := dbms_ldap.add_s(emp_session, emp_dn, emp_array);
-- Free attribute array (emp_array)
dbms_ldap.free_mod_array(emp_array);
-- Unbind from ldap directory
vn_retval := dbms_ldap.unbind_s(emp_session);
end;

Can't get External Application Debugging to work to debug PL/SQL.

I can debug PL/SQL directly. I wish to debug ASP.NET applications using IIS. To debug my application I must attach to aspnet_wp.exe and fire up IE or firefox.. I have tried to set ORA_DEBUG_JDWP just before the call to the PL/SQL SP, but the debugger doesn't stop at the PL/SQL break point--I have set a break point just before the PL/SQL call and then enable 'Start Oracle External Application Debugger" and enter the port number that I set in ORA_DEBUG_JDWP. I believe that ORA_DEBUG_JDWP must be set before an Oracle connection is established. If I do that it interferes with my firefox or IE browser that I need to get to the point of the PL/SQL call--there are many postbacks that are encountered through the course of getting to the point where the PL/SQL call (i.e. logging in, navigating through the menu and then entering values to trigger the call). Has anyone gotten ODT to work in this configured environment? Any suggestions would be appreciated.

Yes, I have gone through the article step by step many times. The crux of my problem I believe is that I am to "3) Add code to your ASP.NET app to set the environment variable at the process level. You need to do this at a point in the code before a connection is opened. In C# this looks something like:
Environment.SetEnvironmentVariable("ORA_DEBUG_JDWP", "host=mymachine;port=8888", EnvironmentVariableTarget.Process);"
I must access the Oracle database for various logon information before I get to the PL/SQL SP that I want to debug. On the first Oracle database access I get the following Oracle error because I have already set the ORA_DEBUG_JDWP variable so any connection to Oracle is trying to access the debugger (That's what I conclude anyway)..
ORA-01031: insufficient privileges\nORA-06512: at \"SYS.DBMS_DEBUG_JDWP\", line 68\nORA-06512: at \"SYS.DBMS_DEBUG_JDWP_CUSTOM\", line 59\nORA-06512: at line 1\n"
Thanks,
Brent
<<Did you have a chance to go through the steps in this article?:
<<http://cshay.blogspot.com/2006/10/debugging-plsql-from-aspnet-and-visual.html
<<Let me know.
<<Christian

Problem in starting SQL*PLUS in oracle database 10g

Hi
Well I am facing one problem while starting SQL*PLUS in oracle database 10g
ERROR - "Procedure entry point longjmp could not be located in dynamic link library orauts.dll"
This has happened when I installed Oracle Database 11g on same machine and when I deinstalled Oracle 11g then SQL*PLUS is started...no error came
Can anybody tell me the reason please...

hi
pls im having the same problem but in my own case i installed oracle apex using 11g.
im env variable is:
C:\Oracle\product\10.1.0\Client_1\bin;C:\Oracle\product\10.1.0\Client_1\jre\1.4.2\bin\client;C:\Oracle\product\10.1.0\Client_1\jre\1.4.2\bin;C:\app\Xty\product\11.2.0\dbhome_1\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;;C:\Program Files\TortoiseSVN\bin;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\
pls which is my apex_home so i can interchange it?
i also have oracle 10g client installed

I cannot debug with SQL server 2008 SSMS asks for Firewall permission?

hi friends,
I run SQL server 2008 R2 developer edition on windows 8 basic edition. SQL server is installed in my local machine. when I tried to debug a sql script it asked the firewall permission as show on image
when googled I found this
Article from MSDN with fix tool but it cannot installed on my Windows 8 OS, is there way to fix it without giving any unauthorized access to my system?
thanks
I use Visual studio 2012 Ultimate and SQL server 2008 developer edition!

Hi,
The hotfix you provide applies for Windows Server 2008.
The windows firewall on this machine is currently blocking remote debugging.
According the message, the following ports need to be enabled for remote debugging. Use the procedure that is described in the section
Configuring a Port in Windows Firewall to enable the following ports through Windows Firewall:
Ports
Protocol
135
TCP
Required
500, 4500
UDP
Required if your domain policy requires network communication to be performed through IPSec.
See the below article for more information:
How to: Enable Transact-SQL Debugging
http://msdn.microsoft.com/en-us/library/vstudio/s0fk6z6e(v=vs.100).aspx
Thanks.
Tracy Cai
TechNet Community Support

Problems with PL/SQL packages

Hello,
I face the following problem with PL/SQL stored procedures. The Oracle
version is 8.0.5 on Windows NT 4. The PL/SQL package has a set of procedures and functions.
The main procedure of the PL/SQL package is triggered from VC++ executable. If for some reason,
an exception is caught in the stored procedure (like no_data_found
exception), then the following problem occurs.
If we try to trigger the stored procedure again through the VC++ executable,
the variables in the stored procedures have the values as in the previous
execution. They are not getting initialised. (The same database connection
is used in VC++ executable).
Currently, only if a new connection to the database is used , the problem is
solved.
Also, change in the input parameters of the procedure is not reflected, once the procedure fails because of any exception. Only the input which was given during the time of execution when the procedure failed,is considered.
What could be the reason for this problem and how can this be corrected?
Please send in your suggestions.
Thanks and Regards,
Ramya Priya
null

Hi Keith,
I am connecting to the database as the package owner..
I have noticed earlier that I have problems when capturing triggers also.. The content of one large trigger contains 36371 characters and when capturing it from DB, the content was truncated to 28020 characters in Designer.
Our ideas with capturing the DB packages/procedures were to use the Designer as version control system.
We wanted to have all objects used in a project in Designer.. entities, tables, triggers, packages, procedures, Forms files, etc. in order to make a configuration for a project release.
Thank you,
Claudia

How to avoid performance problems in PL/SQL?

How to avoid performance problems in PL/SQL?
As per my knowledge, below some points to avoid performance proble in PL/SQL.
Is there other point to avoid performance problems?
1. Use FORALL instead of FOR, and use BULK COLLECT to avoid looping many times.
2. EXECUTE IMMEDIATE is faster than DBMS_SQL
3. Use NOCOPY for OUT and IN OUT if the original value need not be retained. Overhead of keeping a copy of OUT is avoided.

Susil Kumar Nagarajan wrote:
1. Group no of functions or procedures into a PACKAGEPutting related functions and procedures into packages is useful from a code organization standpoint. It has nothing whatsoever to do with performance.
2. Good to use collections in place of cursors that do DML operations on large set of recordsBut using SQL is more efficient than using PL/SQL with bulk collects.
4. Optimize SQL statements if they need to
-> Avoid using IN, NOT IN conditions or those cause full table scans in queriesThat is not true.
-> See to queries they use Indexes properly , sometimes Leading index column is missed out that cause performance overheadAssuming "properly" implies that it is entirely possible that a table scan is more efficient than using an index.
5. use Oracle HINTS if query can't be further tuned and hints can considerably help youHints should be used only as a last resort. It is almost certainly the case that if you can use a hint that forces a particular plan to improve performance that there is some problem in the underlying statistics that should be fixed in order to resolve issues with many queries rather than just the one you're looking at.
Justin

How do debug an application in Shared Memory debug mode using JDev

I don't see the option of using "Shared memory" debug mode in JDev. There is only socket debug option(Attach/Listen) in debugger but no shared memory debug option.
Is it missing or is it hidden somewhere.
Can anyone let me know as all IDEs provide that.

Any updates?

Is there any known problem using Oracle SQL Developer 3.0.04 with Java 1.7?

I'm new to Oracle. I have installed Oracle SQL Developer 3.0.04 and Java 1.7. When I run Oracle SQL Developer, I will get the window Running this product is supported with minimum Java version of 1.6.0_04 and a maximum version less than 1.7. This product will not be supported....
Is there any known problem using Oracle SQL Developer 3.0.04 with Java 1.7?
I have already downloaded Java 1.6 but don't know whether I need to uninstall Java 1.7 first. If don't need to uninstall Java 1.7, how can I set Oracle SQL Developer to run with Java 1.6?
Thanks for any help.
Edited by: 881656 on Aug 25, 2011 11:22 AM

Hi,
One prior post discussing the use of Java 7 is:
SQL Developer 3.0 and Java SE 7?
There is no need to uninstall any Java version (except if you have disk space constraints) and no problem switching between Java versions. This may be controlled in the sqldeveloper.conf file in your ...\sqldeveloper\sqldeveloper\bin directory via the SetJavaHome line. For example:
#SetJavaHome ../../jdk
SetJavaHome C:/Program Files/Java/jdk1.6.0_26
#SetJavaHome C:/Program Files/Java/jdk1.7.0Regards,
Gary Graham
SQL Developer Team

Problems debugging PL/SQL [JDev 9.0.3.1035 Prod]

Similar Messages

Maybe you are looking for