SQL Developer 4.0 EA bugs

One bug and one improvement.
Bug:
Clicking the data tab on tables that include XMLTYPE columns do not display any rows or column headings. You can redproduce with the following script and then click the table in connections or schema view and then click the data tab on version "Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production":
    CREATE TABLE xml_test (
      id NUMBER
    , text VARCHAR2(100)
    , xml_data XMLTYPE
    INSERT INTO xml_test VALUES (1, 'joe', XMLELEMENT("ROOT"));
    INSERT INTO xml_test VALUES (2, 'blogs', XMLELEMENT("ROOT"));
    INSERT INTO xml_test VALUES (3, 'john', XMLELEMENT("ROOT"));
    INSERT INTO xml_test VALUES (4, 'smith', XMLELEMENT("ROOT"));
Improvement:
When opening package spec/body from a file on your local file system detect that both the spec and body are open as files and offer the same arrow controls in the gutter that allow you to jump between a function/procedure in the spec to the same function/procedure in the body and vice versa.

The bug is a known issue and we're working on it, thanks.

Similar Messages

Possible SQL Developer 3.0.04 bug

I'm currently using SQL Developer 3.0.04, using Windows XP, and connecting to an Oracle XE 10g database. I've noticed a strange problem when I export a database and use the default "export all data from all tables" option. Basically, when the rows within each table are exported as "insert" statements, any tables with "DATA" within their name are completely skipped. The statements to create the tables are exported, along with all related constraints, just not the actual table rows.
This is what I did:
1. Created a table named "AAA", with two columns, AAA_ID and AAA_INFO
2. Loaded a few rows into the "AAA" table
3. Performed an export of the database; clicked on Tools->Database Export, chose the database connection, left everything with the default values, checked the "proceed to summary" box, clicked Next, then clicked Finish
4. Checked the export file for insert statements for the "AAA" table; they were present
5. Renamed the table to "AAA_DATA"
6. Performed the export again and checked the export file for insert statements for the "AAA_DATA" table; they were not present
7. Renamed the table to "AAADATAAAA"
8. Performed the export again and checked the export file for insert statements for the "AAADATAAAA" table; they were not present
9. Renamed the table back to "AAA"
10. Performed the export again and checked the export file for insert statements for the "AAA" table; they were present again.
When I go through each of the export screens and manually select all of the database tables within the "Specify Data" section, the rows for the "DATA" tables are correctly exported; the problem only happens when I use the option to go straight to the summary and export everything.
-Bill

Thanks for taking the time to analyze the problem and provide steps to reproduce. I can see how the problem is caused and I have filed a bug for it.

SQL Developer: import from Excel bug

SQL Developer 1.1.2.25 Build MAIN 25.79
This is a test for import from Excel.
Test table:
create table bla
(x number null,
y varchar2(1) null);
Excel data:
x y
1 a
2 b
3
SQL Deveoper generates:
Error at line 3:insert into BLA (X,Y) VALUES(3,'NULL')
IMPORT into table BLAcomplete
Inserted 2rows.
Failed to insert 1rows.
SQL Error:ORA-12899: value too large for column "BCRCEK"."BLA"."Y" (actual: 4, maximum: 1)
I think there is a bug, because there must be generated NULL without apostrophe.
insert into BLA (X,Y) VALUES(3,NULL);

Hi Barry,
   That's[b] GREAT NEWS !!!.
   So, i just update current release 1.1.2.25 to 1.1.2.25.79 ?
Thanks for the great work.
Zack
Oops !!! Am already using 1.1.2.25.79, same as bcrcek above. So need to wait for Patch Release ?
Regards
Zack
Message was edited by:
        Zack.L

SQL Developer 2.1rc1 - some bugs

Hi!
I'd like to report some bugs I've encountered with the RC1 version of Oracle SQL Developer (Version 2.1.0.63 build MAIN-63.41).
- The syntax error highlighting is not very good - I've successfully executed queries almost completely underlined with pink wavy lines
- something strange happens when I hit <Enter> while the cursor is at the end of a row that reads " union all" - a new line does not get inserted, and the cursor disappears. <Backspace> and <Enter> again, and it works ok.
- query execution - the command I entered gets modified, stripped of comments, as far as I can tell, and if I get an error report, the line number reported is off by a couple of lines. I remember this working better in 1.5.

I found a few bugs in the first ten minutes of use:
- The main one was that my backspace key didn't work, no idea why this was as my keyboard is pretty standard?
- The search/highlight window changes size when adding a new highlight, and the close button then disappears until it's re-sized
- Editing xmldata in a window works, if it's not syntax highlighted or able to be pretty printed, but clicking ok does not change the value? Should either work or warn that it doesn't work.
- In the query result window is 'SQL' in blue, not easy to notice that it's a button'y thing to click and see the SQL that was executed. Also, why does the little bubble with the code just float in the middle and not point to anything in particular? Surely it could point to the 'SQL' button or similar?

Sql Developer 1.5.5 bug with large sequence start values.

We have a small table in our sql server 2005 schema (~700) rows. Its primary key is a bigint. We randomly generate ids for this table (don't ask). We have ids for this table which are larger than 2147483647. (java.lang.Integer.MAX_VALUE). I'm using a Windows 10g instance as the repository:
SQL> select * from v$version
2 ;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
Capturing this model works fine.
Converting this model works fine.
When the converted model is "Generated", Sql Developer stops generating the script before the worksheet window is opened with the generated sql. If run from sqldeveloper/bin, this exception is output to the console:
java.lang.Exception: java.util.NoSuchElementException
at oracle.dbtools.migration.workbench.core.ui.AbstractMigrationProgressRunnable.start(AbstractMigrationProgressRunnable.java:141)
at oracle.dbtools.migration.workbench.core.GenerateInitiator.launch(GenerateInitiator.java:42)
at oracle.dbtools.raptor.controls.sqldialog.ObjectActionController.handleEvent(ObjectActionController.java:149)
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:1995)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
at javax.swing.AbstractButton.doClick(AbstractButton.java:357)
at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1225)
at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1266)
at java.awt.Component.processMouseEvent(Component.java:6134)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3265)
at java.awt.Component.processEvent(Component.java:5899)
at java.awt.Container.processEvent(Container.java:2023)
at java.awt.Component.dispatchEventImpl(Component.java:4501)
at java.awt.Container.dispatchEventImpl(Container.java:2081)
at java.awt.Component.dispatchEvent(Component.java:4331)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4301)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3965)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3895)
at java.awt.Container.dispatchEventImpl(Container.java:2067)
at java.awt.Window.dispatchEventImpl(Window.java:2458)
at java.awt.Component.dispatchEvent(Component.java:4331)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Caused by: java.util.NoSuchElementException
at oracle.dbtools.metadata.persistence.PersistableObjectIterator.next(PersistableObjectIterator.java:131)
at oracle.dbtools.migration.generate.GenerateWorker.generateSequences(GenerateWorker.java:862)
at oracle.dbtools.migration.generate.GenerateWorker.generateIndividualSchema(GenerateWorker.java:456)
at oracle.dbtools.migration.generate.GenerateWorker.generateSchema(GenerateWorker.java:365)
at oracle.dbtools.migration.generate.GenerateWorker.runGenerate(GenerateWorker.java:220)
at oracle.dbtools.migration.workbench.core.ui.GenerateRunner.doWork(GenerateRunner.java:71)
at oracle.dbtools.migration.workbench.core.ui.AbstractMigrationProgressRunnable.run(AbstractMigrationProgressRunnable.java:161)
at oracle.dbtools.migration.workbench.core.ui.MigrationProgressBar.run(MigrationProgressBar.java:569)
at java.lang.Thread.run(Thread.java:619)
A problem row can be viewed by issuing this query against the repository:
select * from md_sequences where seq_start > 2147483647;
We have one row returned. The oracle.dbtools.metadata.persistence.MdSequence class uses a java.lang.Integer value to store the start value for the sequence. The value stored in the repository's MD_SEQUENCE table overflows the Integer type.
Updating the SEQ_START column in the MD_SEQUENCE table fixed our problem. (Well, I can now generate the schema. I may have other problems with the sequence being off).
I've written this post to save someone else the day it took me to diagnose this problem with Sql Developer 1.5.5. At the very least Sql Developer should inform the user that it could not generate the script because of the large sequence start value. It basically swallows any error and terminates script generation without any type of feedback.

Update: I was able to recreate the problem!
1. Create a new table (I used TEST).
2. Mark first column af primary key.
3. Save the table.
Notice the name of the primary key index created: (TEST_PK in my case)
4. Edit the table.
5. Under constraints change the name of the primary key constraint.
6. Save the table.
Notice that the index still has its original name.
7. Edit the table.
8. Change something.
9. Attempt to save changes (Fails).
Conclusion:
Either SQL Developer should be aware of indexes with different name than a constraint,
or when SQL Developer changes the name of a constraint with an index, both the constraint and the index should be renamed.

Insufficient privilege when run SQL in PL/SQL Developer

Hi,
My developer had strange behavior when run below SQL from PL/SQL Developer. It will come out with "*Insufficient Privileges*" message.
SELECT Fiscal
FROM pmaps_fiscalweekonly
WHERE intend >= trunc(sysdate)
AND rownum < 5
ORDER BY intend ASC;
Same SQL run without any problem in SQLPLUS and SQL Developer.
But if we use small asc instead capital ASC, it run without problem also in PL/SQL Developer.
SELECT Fiscal
FROM pmaps_fiscalweekonly
WHERE intend >= trunc(sysdate)
AND rownum < 5
ORDER BY intend asc;
Kindly check if someone have any idea.
ZlT

zhilongtan wrote:
But the privilege problem only happened when capital ASC keyword was used in ORDER BY clause. If small asc keyword was used, it run without problem.
It seems to me, it does not relate with privilege or role grant. Please advise. Thanks.
ZlT.I think you should sk this question in a support forum for PL/SQL Developer. The possible bug seems directly connected to this tool. If I remember rightly then this tool is from ALLAutomations. You should ask them. THis forum would be the wrong place to ask.
Edited by: Sven W. on Aug 30, 2010 5:24 PM

How to integrate the Data modeler in Sql developer

Hi
How can we integrate the data modeler into sql developer and use the data modeler?
Thanks

Integrating different oracle products (SQL Developer [Data Modeller], JDeveloper, ...) on platforms like Eclipse, Netbeans, JDeveloper Framework is a really missing feature.
JDeveloper has a good approach for integrated Java and database development, but has not immediate benefits from from other development streams like SQL Developer.
On daily work we must use more than three different tools for most common task
- editing stored functions, procedures and packages with SQL-Developer (code formatter in Jdeveloper produces sometimes UNREADABLE code ( So we are using TOAD instead ). Why can't Jdeveloper use SQL-Developer formatting tools in bug fixed verrions from 1.5.5?
- database modelling with SQL Developer Data Modeler without PLSQL package support ???
- database development with JDeveloper, ADF and offline database model without capabilities for logical databse models
Please put them all together!

Is Sql Developer "sensitive" on objects?

Hi,
in the company I work in I use Pl/Sql Developer for developing in pl-sql (it's the product of Allround Automations http://www.allroundautomations.com/plsqldev.html), bacause we work on Oracle vers. 8.1.7.
Recently I've tried to install on my PC Sql Developer of Oracle vers. 1.1.2 that seems to work well (the higher versions are for Oracle 9 -->)
I've noticed that, rispect to the product I use, in Sql Developer if I write a statement like:
select a.field1, a.field2
from mytable a
where a.
after the a. the tool doesn't present to me the list of mytable's columns and this would be very usefull.
Is it due to the fact that it's not a Sql Developer possibility or I need to do something in preferences or the vers. 1.1.2 doesn't support this function?
Thanks!
Edited by: Mark1970 on 17-feb-2010 5.29

I think it's better to use an official tool for my professional skill, isn't it?Not necessarily. Toad, PLSQL Developer and others are mature tools to work with Oracle DBs while SQL Developer still has many bugs, even in version 2.1, and you need to know what you can do and where not to trust it, e.g. lines missing when exporting large datasets.
Regards
Marcus
P.S.: I have Toad installed on my PC but use SQL Developer almost exclusively. But I'm an early adopter, tested every version and I think I know when not to trust SQL Developer and use other tools instead.

Apex Listener 2.0.1 vs Sql Developer Administration 3.2.20.09 bugs

Apex Listener 2.0.1 / Sql Developer 3.2.20.09 / Apex 4.1.1
1. I'm using basic connection type with service name. Each time I connect to listener administration it is resetted to SID with default name as orcl.
2. Test Settings does not work in case hostname is localhost.
Database Settings apex:Cannot connect to APEX_PUBLIC_USER. Исключение ввода/вывода (input/output exception): The Network Adapter could not establish the connection>
At the same time it's working in defaults.xml:
<entry key="db.hostname">localhost</entry>I'm not sure why. Database and Apex Listener are installed on the same mashine. May be this can help:
<Warning> <Server> <x> <> <DynamicListenThread[Default]> <<WLS Kernel>> <> <> <> <BEA-002611> <Hostname "x", maps to multiple IP addresses: 10.110.x.x, 0:0:0:0:0:0:0:1> 3. I can see "Enable RESTful Services" action in (url http://docs.oracle.com/cd/E35137_01/appdev.32/e35117/intro.htm#autoId110)SQL Developer User's Guide. Still there is no such action in Sql Developer. Thus settings are always uploaded with enabled RESTful Services.
I see error
The pool named: apex_al does not existeach time I connect to Apex Listener Administration in case of RESTful Services is not configured during configuration of apex.war.
I can't find any restrictions for RESTful Services to be configured. So I think this error is unnecessary.
4. From sql developer User's Guide
Connect (context menu only): Connects to the Application Express Listener (see Connecting to Application Express Listener Server).Retrieve Settings, Upload Settings, and Launch URL are enabled when you connect to the Application Express Listener.>
administration settings are retrieved and displayed but still Retrieve Settings, Upload Settings, and Launch URL are disabled in context menu after connection.
I need to perform New Administration action to make them enabled.
Is this expected behavior ?
Is this all bugs or known features ?
Regards,
Igor

DB: V11.2
APEX V 4.2.3.00.08
APEX Listener: V2.0.5.287.04.27
SQLDeveloper: Version 3.2.20.09
OS WIndows 7 64 bit
I am trying to create a connection to a standalone Apex Listener installation via SQL Developer to manage the listener settings. I start a new connection and after entering the UN/PWD of the Listener Administrator I get the following error:
Authentication failed
"CANNOT CONNECT TO CONNECTION.
INVALID RESOURCE OWNER CREDENTIALS"
In the Standalone APEX Listener DOS window I'm getting the following error message:
SEVERE: The pool named: apex_al does not exist
So where do I even start to trouble shoot this???
I add a connection as follows:
Connection Name: Connection
Usename: adminlistener (pwd=adminlistener configured using command :java -jar apex.war user adminlistener "Listener Administrator")
HTTP radio button
Hostname: localhost
Port: 8080
Server Path: /apex
thanks in advance
Paul Platt

Oracle SQL Developer Data Modeler 3.0 Bugs, Resolution and workarounds

The purpose of this thread is to list bugs discovered while using ORACLE SQL Developer Data Modeler 3.0
Mainly with SQL SERVER 2005 and ORACLE 10g models.

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)

PL/SQL Bug in SQL Developer?

SQL Developer v 1.1.1.25 running on Windows XP.
I have a PL/SQL procedure that does not compile with debug in SQL Developer. Compiling it with debug produces the following error:
an Error(1): PLS-00801: internal error [79110].The only way I was able to get the procedure to compile in SQL Developer was to add the 4th line. If I uncomment the 4th line it compiles with debug. Why??
Here is the procedure:
CREATE OR REPLACE
PROCEDURE BOGUS AS
CURSOR c1 IS
SELECT dummy FROM DUAL;
-- x c1%ROWTYPE;
PROCEDURE test ( rec IN OUT c1%ROWTYPE) IS
begin
null;
end;
BEGIN
NULL;
END BOGUS;Message was edited by:
marife
I played around some more with the procedure and discovered the problem. The key is the compiling with debug. I believe that compile with debug cannot build the debug information for a %ROWTYPE as a parameter. But if I define a local variable of that %ROWTYPE, then the compile with debug knows what debug information to track for the %ROWTYPE.
I discovered that in SQL*Plus it compiles, but when you issue the ALTER PROCEDURE bogus COMPILE DEBUG, it does not compile. This is a problem with the debug option for compiling and not a problem with SQL Developer.
Sorry for the posting. Hopefully this information will save other times and fustration.
Mike

Just for anyone else searching on this bug - I get the same error with certain procedures in TOAD when compiling with DEBUG.
Fortunately nobody here has the first clue how to use TOAD debug so it's only ever switched on by accident or after a reinstall (it's the default) - so turning debug off fixes the problem.

Bug in Oracle SQL Developer

I had Oracle SQL Developer 1.5.0.53 and when I did a "Check for Update" it said no updates found, even though SQL Developer 1.5.1 was released on June 9, 2008. So obviously this is a bug you need to fix.
OK - So I downloaded the latest Oracle SQL Developer and installed it and when I opened it up, all my connections were gone!!!
That's another bug you need to fix.

See Does check for updates install 1.5.1 for some suggestions for Check for Update.
For installing 1.5.1 and then losing your connections, did you install in a new directory or over the top of 1.5.0? If yes, then reinstall again into a new directory. If not, did migrate your settings from 1.5.0? Without doing that 1.5.1 won't find your existing connections.
theFurryOne

BUG in Oracle SQL Developer 3.0.04 on the "generating DLL" with comments?

I'm newbie on oracle, but I think that I found out a bug in Oracle SQL Developer version 3.0.04 on the "generating DLL" tool using "comments".
I will describe the steps that I gave:
I created a view, but after I test it I had to change my “where” condition, so I comment the old code and then I wrote the new “where” condition below. After I done that I tried to look at the sql code of my view using “generating DLL” tool, but oracle sql developer only shown me half of the code, a lot of code were missing. Then I began with some test trying to understand what happen and I notice that if I put an invalid sql code in my comment the generating DLL start working with no problems, for example(pseudo-code):
(COMMENT WITH VALID SQL CODE the "Generating SQL" don't work:)
CREATE OR REPLACE VIEW <user>.<view_name> ( <column1>,<column2> )
AS
SELECT column1, column2
FROM table1
INNER JOIN
(SELECT
FROM table2
INNER JOIN .....
INNER JOIN ....
--where time_stamp = (select max(time_stamp) from .....)
WHERE time_stamp >= TRUNC(sysdate)
) t1 ON t1.ID = ....
AND ..... >= TRUNC(sysdate)
ORDER BY ....
Generating DLL returns this(when the error occurs):
CREATE OR REPLACE VIEW <user>.<view_name> ( <column1>,<column2> )
AS
(COMMENT WITH VALID SQL CODE the "Generating SQL" work with no problems:)
CREATE OR REPLACE VIEW <user>.<view_name> ( <column1>,<column2> )
AS
SELECT column1, column2
FROM table1
INNER JOIN
(SELECT
FROM table2
INNER JOIN .....
INNER JOIN ....
--where
WHERE time_stamp >= TRUNC(sysdate)
) t1 ON t1.ID = ....
AND ..... >= TRUNC(sysdate)
ORDER BY ....
I believe that "Generating DLL" tool have some problem with the comments, I also used /*...*/ to comment but the problem is still active.
I notice as well that if I started to add some more comments along the code, the conditions migth change, so I think the problem is related with "comments" code.
Would you mind telling me if this is a real bug or if I'm doing anything wrong.
Thank you in advance,
Rodrigo Campos
Edited by: 894886 on 3/Nov/2011 5:29

Hi Rodrigo,
Thank you for reporting this. The only bug I see currently logged on a comment affecting the generated View DDL involves ending the last line of the definition with a comment, which treats the ending semi-colon (even if on a different line) as part of the comment. That is actually related to a low-priority bug against an Oracle database API.
Unfortunately, your pseudo-code is a bit complex. Trying a few quick, simpler tests against the standard HR schema did not reproduce the issue. I tried INNER JOIN, and nested SELECTs. It would help greatly if you could provide a test case compilable against one of the standard schema, like HR or SCOTT.
Regards,
Gary
SQL Developer Team

Bug report: SQL Developer 3.2.09 Crashes for some Replace Regexp

Hi,
SQL Developer 3.2.09 (tested on Win XP with SQL Developer built-in Java) crashes for some Replace Regexp.
Try the following:
New SQL-sheet
CTRL-R for Replace
Enter "||" (two chars) as search-expression
Enter "" (nothing) as replace-with-expression
Check Regular Expressions Check Box
Hit OK
-->100% CPU usage, no reaction.
Can you confirm the bug?
Edited by: blama on Sep 4, 2012 3:48 PM

I believe the pipe character is a regexp meta character and your regexp probaby matches everything repeatedly. If you want to replace the concatenation operator you don't need a regexp.
Having said that, I am using SQL Developer on Linux with Java 1.6.0_33 and I don't get the hang, just replacing the same thing again and again.
On windows with 1.6.0_24, I do get the hang. It may be a java issue.
Edited by: Jim Smith on Sep 4, 2012 5:39 PM

SQL Developer 3.0 Bug

In ORACLE Developer 3.0.04 is a bug in showing the functions or procedures of a package. When "for update nowait" is included in source code no functions or procedures will be shown.
select vts_server
into v_server
from vt_server
where vts_status = 1
and vts_verfuegbar_knz = 'J'
and vts_server = i.vts_server
for update nowait
When this line will be comment out, the list is already fine.

Known issue. See package body procedures are not displayed (3 posts down from yours.)
Brian Jeffries
SQL Developer Team

SQL Developer 4.0 EA bugs

Similar Messages

Maybe you are looking for