SQL Developer 3.0 Query Builder Issue

When compiling a query within the Query Builder I cannot execute the query - the RUN statement button is disabled. There also appears some "lagging" when building the query.
Is this a bug within the SQL Developer 3.0?
This has the potential to be an excellent tool. I am pleased that this version now gives you function to amend views.
Edited by: user13116583 on Mar 31, 2011 2:48 PM

Hi Marc -
With respect to the "lagging" see Re: 30EA2 - Query Builder locks up when I select the tab. on design trade offs made during the 3.0 early adopter cycle.
The run button should be enabled as soon as you type anything in the Worksheet or drag/drop anything on the Query Builder. Can you give me more detail on what you are doing/seeing?
Brian Jeffries
SQL Developer Team

Similar Messages

SQL Developer 1.1 Query Builder does not display connection tree

I have installed SQL Developer 1.1 on a PC running Windows XP SP2. I am connecting to Oracle 9.2.0.7.0.
After connecting to the database, I right click in the SQL Worksheet and select Query Builder and when the new window is displayed, there are no tables to select from.
What is causing this?

Hi Antony,
Upgrading from SP7 to SP9 fixed a lot of problems for me! It's worth trying.
Problems solved for me:
Page requests take about 2 minutes to display page (now within a few seconds)
KM SQL logging (30-50Mb per minute) problem fixed.
There are some problems upgrading to SP9, but searching this forum will help you in finding some solutions for this
Regards,
Noel

SQL Developer replacement for Query Builder?

Our developers use query builder to quickly develop sql code w/conditions, joins, where clauses, etc. I just installed release 2 of SQL Developer and am trying to figure out if this is a viable replacement for query builder. Is there a graphical "query builder" component as part of SQL Developer?

Barry, I would agree that it should be clean and easy to use. I started using Data Browser 2.0 and migrated to Query Builder 6.0.7.1.0 and while Query Builder is no longer it's own product it's integrated into Reports Developer 10g. The basic layout and operation has been consistent thru the life cycle and I would think you'd keep the "look and feel" consistent with what's currently available. (might simplify integrating it too). My biggest complaint with Query Builder 6.0.7 (se don't use the 10g version) is that it errors when opening a schema with more than 8192 objects. As an E-Business Suite 11.5.10 customer this is an issue for our developers when logging in as the standard APPS user.
So here would be my "wish list"
1. consistent look and feel with "older" versions of Browser/Query Builder
2. removal of 8192 object limitation
3. ability to open older .brw format files
Certainly more improvements would be possible by integrating with SQL Developer and would be welcomed - this wish list is coming from a user who has MANY .brw files in the older 6.0.7 format.

File- Print not working from SQL Developer 1.2.1 Build MAIN-32.13

File->Print not working from SQL Developer 1.2.1 Build MAIN-32.13.
I downloaded sqldeveloper-1.2.1.3213.ZIP and extract to a local directory. From the extracted directory I ran ..\sqldeveloper\sqldeveloper.exe from Windows XP sp2. The program itself seems to run just fine but File-Print doesn't do anything. In Help-About, Java Platform is reported as 1.5.0_06 and Oracle IDE is 1.2.1.3213. I'm not sure where to look for what is causing the problem.
Thanks

I hadn't tried CTRL-P before but I did today. On the first attempt, I saw a small jump in the memory usage for sqldeveloper.exe as reported in Windows Task Manager. Otherwise, there was no change. A second CTRL-P in the same session produced a further bump but subsequent attempts in the same session produced no further change in CPU or Memory Usage.
Using Task Manager to monitor this further, I tried File->Print again and saw that sqldeveloper would periodically climb to 1 or 2 percent CPU and consume a little more memory. After a minute or so, though, all activity stops again.
I do not get a print dialog box from SQLDeveloper using either CTRL-P or File->Print

SQL developer 3.0 - Few Query Builder issues

Hi All,
I have just started using SQL Developer 3.0 so have not fully browsed thru all of the available options in SQL Developer. I have been trying to work on creating and editing sql statements using Worksheet and Query Builder.
I am working on to test this tool so I can give it to the users for them to try and use it - they used to work on the old Query Builder 6.0.7....since it is already de-supported long back to work against 11g database, I am hoping to tell them to use SQL developer 3.0 instead.
Hence, if an user doesn't know how to write a sql statement, he/she would try to do the same using Query Builder.
So, the following questions are more aligned towards a normal user who would try to create a query in the Query Builder window, instead of directly typing a sql statement in the Worksheet window.
1) How to establish/create a relationship between tables after you have dragged down the tables into the Query Builder window? - i tried but couldn't get any options!.
2) Sometimes I see 'Connection closed' error when i try to run a query. How to refresh the connection without opening a new Connection tab?
- I tried this but evertytime it opens up a new connection tab, while the old tab is still present.
3) Columns in the Expression field in Query Builder window can ONLY be displayed in the result set, if the 'output' box on the extreme left of the 2nd section in Query Builder window is checked.
Now when i try to check the output box for an expression (with few aggregate functions), the 'Grouping' check box automatically gets checked, which when run throws an ORA-00934 error: group function is not allowed here...but when I de-select the 'Grouping' check box, the 'output' box also gets un-checked!.
How to solve this out?
Please let me know the resolutions of the above - much appreciated.
With Regards,
Pamir
Edited by: user651047 on 11-Aug-2011 07:53

Hi,
As Raghu noted above, and you also saw in rp0428's following reply,
Re: Problem with displaying sdo_geometry objects
drilling down to the cell edit details is your only recourse for now. Apparently there will be further work done in this area, but it is not clear exactly what or when it will be. For those with access to it, here is a bug reference:
Bug 13680849 - RC1: NOT DISPLAYING THE DATA OF MDSYS.SDO_GEOMETRY
Regards,
Gary

SQL Developer vs TOAD - query performance question

Somebody made me notice same queries are executing slower in SQL Developer than in TOAD. I'm rather curious about this issue, since I understand Java is "slow" but I can't find any other thread about this point. I don't use TOAD, so I can't compare...
Can this be related to the amount of data being returned by the query ? What could be the other reasons of SQL Dev running slower with an identical query ?
Thanks,
Attila

It also occurs to me that TOAD always uses the equivalent of the JDBC "thick" driver. SQL Developer can use either the "thin" driver or the "thick" driver, but connections are usually configured with the "thin" driver, since you need an Oracle client to use the "thick" driver.
The difference is that "thin" drivers are written entirely in Java, but "thick" drivers are written with only a little Java that calls the native executable (hence you need an Oracle client) to do most of the work. Theoretically, a thick driver is faster because the object code doesn't need to be interpreted by the JVM. However, I've heard that the difference in performance is not that large. The only way to know for sure is to configure a connection in SQL Developer to use the thick driver, and see if it is faster (I'd use a stop-watch).
Someone correct me if I'm wrong, but I think that if you use "TNS" as your connection type, SQL Developer will use the thick driver, while the default, "Basic" connection type uses the thin driver. Otherwise, you're going to have to use the "Advanced" connection type and type in the Custom JDBC URL for the thick driver.

SQL Developer 3.3.20 maximized issue

I've been running SQL Developer 3.1.07 on my Linux Mint 13 (Ubuntu 12.04) 64-bit cinnamon desktop for well over a year, and today, I downloaded the 3.2.20 linux rpm, and installed via alien / dpkg.
I migrated my settings, and can connect to any of my databases fine.
However, I'm having problems with the menus when SQL Developer is maximized.
For example,
1. I mouse click on any menu, but the menu does not stay selected (I must hold the mouse button down).
2. When I select a menu entry, another menu is displayed. i.e. click Help, then try to select any item, and the Versioning menu displays.
If I un-maximize SQL Developer, and stretch to 90% of the screen, it works fine. Using the Alt keyboard and up/down arrow works fine.
I updated my Java to 1.6.0_43 and rebooted my PC, but the problem still persists (when maximised).
Anyone have an idea of what might be causing this?

ah,... never mind. Some more Googling and I see there are known issues.
Developer GUI problem on x64 Fedora
Will just have to live with it 90%.
Edited by: stuartu on Apr 11, 2013 9:20 AM

Unit Test in SQL Developer 2.1: Automated Builds

Hi,
I am interested to know if the new Unit Testing framework can be accessed via API so the test execution is initiated from automated build process.
Regards,
Vadim

I am having a problem with the unit testing command line.
I am attempting to run the unit testing using the command line interface.
I can connect to UNIT_TEST_REPOS schema in SQL developer.
I am successfully running units test and suites in SQL developer.
UNIT_TEST_REPOS, RCSV1 and DEVER users are granted on the UT_REPO_USER role and UNIT_TEST_REPOS and DEVER on the UT_REPO_ADMINISTRATOR.
The following commands result in an error box saying "No Repository was found on the selected connection, you need to create a repository." (The HELP button apparently does nothing. The OK button closes the box.)
C:\Program Files\sqldeveloper\sqldeveloper\bin>UtUtil -exp -test -name RCSV1_RCS_SECURITY.GET_LDAP_BASE -repo unit_test_repos -file c:\ut_xml\test.xml
Unable to open repository
C:\Program Files\sqldeveloper\sqldeveloper\bin>UtUtil -run -test -name RCSV1_RCS_SECURITY.GET_LDAP_BASE -repo unit_test_repos -db dever
Unable to open repository
C:\Program Files\sqldeveloper\sqldeveloper\bin>UtUtil -run -test -name RCSV1_RCS_SECURITY.GET_LDAP_BASE -repo dever -db dever
Unable to open repository
I would guess that I am not supplying the correct connection info.
My last comment triggered an idea. It turns out that the connection names required are those connections named in SQL developer. In my case, they are not the same as the schema names. The following command worked as advertised.
C:\Program Files\sqldeveloper\sqldeveloper\bin>UtUtil -run -test -name RCSV1_RCS_SECURITY.GET_LDAP_BASE -repo UNIT_TEST -db DeverLocal
The ANT target is
<target name="UnitTests">
<exec executable="cmd" dir="${sqldev.bin.dir}">
<arg value="/c"/>
<arg value="UtUtil -run -suite -name RCSV1 -repo UNIT_TEST -db DeverLocal"/>
</exec>
</target>
Regards,
Bill

SQL Developer fails to query table

I am trying to use SQL Developer (v3.2.20.09) to query a particular table in an Oracle 10G database using a simple "select * from table" query. When I run the query SQL Developer sits there forever waiting for results but nothing is every returned.
The table is relatively small, just a few thousand rows and just half a dozen columns (mixture of numbers, short text strings and datetimes). I can run other queries on the table in question so I know I have privileges, it's just when run a simple query to return all columns and all rows it fails. I even tried to an export of the table using Tools->Database Export but that too just sat there forever failing to complete.
Any ideas? It seems that there is just something in the table that SQL Developer doesn't like.

I've never used sqlplus before but I just tried it and it runs the same query (select * from [table] where rownum <= 40) without any problems. The strange thing is that once I could see which row was row 40 in sqlplus I queried just that one row in SQL Developer (using the primary key column) and it worked fine.
I did a bit more experimenting and it doesn't look like a problem with that row in particular just with displaying more than a certain number of rows. The first column on the table is called OBJ_ID and is a unique integer which forms the primary key. Row 40 has OBJ_ID = 53. I tried running:
select * from [table] where obj_id between 40 and 53 - no problems
select * from [table] where obj_id between 30 and 53 - no problems
select * from [table] where obj_id between 20 and 53 - no problems
select * from [table] where obj_id between 10 and 53 - failure as above (no errors but SQL Developer never displays the results)

SQL Developer 2.1 version migration issue

Hello Everyone,
Since I was unable to find a similar topic on the forum, I'm posting now the problem I'm facing: I have downloaded release 2.1 for Windows 32 bit (without JDK) and I unzipped it in an empty 'sqldeveloper' folder on a Windows XP machine.
Upon starting it up, there is no migration wizard popping up to allow me to import the existing settings from release 1.2.1 residing in a parallel folder 'sqldeveloper.1.2.1'. If it works, does it import anything more than connections?
I tried to use the tools tab and explore various documentation sources (readme, help, forum, internet search) with no luck so far.
I would guess there is something wrong in my deployment procedure since nobody else has complained of similar issues.
Any hints or suggestions you may want to share would be greatly appreciated.
Thank you,
Dan

The original poster mentioned that he was migrating from 1.2.1, a really old version. That version did/does not store user settings under "Application Data", but in "sqldeveloper/system" in its' own installation directory. Unfortunately, SQL Dev. 2.1 will (apparently) not let you import settings from anything prior to 1.5; at least I was not able to do it when I tried just now (I have all of my previous SQL Developer installations still on my hard drive). It looks to me like what he will have to do is first upgrade from 1.2.1 to 1.5.5 (which will allow him to import his old 1.2.1 settings), and then upgrade from 1.5.5 to 2.1.
Ed. H.

SQL Developer 3.2.09 (Build MAIN-09.23) Disconnected Worksheet bug

If you disconnect from a database, the SQL Worksheet that was using that connection loses its connection as shown in the drop-down at the top-right. (ok)
If you then click on the drop-down to re-connect, you can choose a database and a modal popup appears for you to enter the password - but if you have other connections already open, the focus moves from the password to the OK button and you can't enter the password. Since it's a modal popup, you're now stuck and have to kill SQL Developer (very annoying if you have many sql worksheets open with lots of sql in).
Am I doing something wrong and/or is there a workaround until this is fixed?
Thanks,
Mark

Hi Mark,
Thanks for reporting this. A couple of possibilities for a workaround:
1. Tools | Preferences | Database | Worksheet | Close all worksheets on disconnect.
2. Store/Save your password in the Connection define (may not be desirable for security / may not work anyway)
We see something similar in this situation (switching connections in a worksheet without any disconnects) ...
Change database connection in SQL-Worksheet to a not connected db
where an obvious deadlock occurs. In your case, a full thread dump does not clearly state the deadlock, but there is probably one to be found upon closer examination.
Regards,
Gary
SQL Developer Team

30EA1: 2nd instance of the sql developer delivers no query results

Hi,
the first instance works like expected, the 2nd one doesn't delivers any result in queries and in the Messages i found that Error:
SEVERE 43 0 Error while registering Oracle JDBC Diagnosability MBean.
best regards
Werner

hi,
well - the main reasons have been already discussed; another intresting one
(i don't know if somebody else was already running into it): sometimes i start e.g. a long running pl-sql block in the window
Then i go back to e.g. the code editor to take a look on another part of the code which i want to edit - then the sql developer freezes
(i think because something is executed through the main connection - and unfortunatly the main session is already executing something)
When the pl-sql block is finished i can use the sql developer instance again; but in the meantime i need another instance
in my regular work i use 3-4 instances of the sql developer
(like mentioned above - to prevent myself by modifying the productive db during i am working on the
development one in the same schemas, to work on another topic which a customer asked me without loosing my old work or because a window freezed)
Here an idea (i know - maybe it is dirty) - the sql developer could open always 2 connections - one for the communication of the tool to the database (which can't be used by a window)
and one for the window (sure - i am aware that i can open an unshared connection window, but sometimes i just forget to do that)
Another benefit of that: currently a lot of statements are sent through the connection - if i want to trace something i have to do it in the sqlplus because these statements are messing up my trace
however - i took a look into the new version and i am quite impressed, a lot of new cool features
best regards
Werner

SQL query (pl/sql function body returning query) performance issue

I create my report in building my sql instruction with ( SQL Query pl/sql function body returning sql query );
My report take more than 20 seconds however if i did a cut and paste with the sql code in TOAD the same sql take 1 second.
To try to discover the source of the problem; i take the sql generated by the function and i create another report ( sql query ) this new report take 2 seconds.
My query is very big 25,000 characters with database link.
What is the difference between SQL-quey and sql-query(pl/sql function body returning sql query)
Thanks
Marc

Marc,
Firstly...don't compare the timings from Toad, since often Toad only fetches the first few records for you (i.e. it pages them).
Secondly....the database link could be a factor here, but without seeing your query it's too hard to say.
Can you post the query somewhere (on a webserver say)?

SQL Developer 1.1.0.21: Issues with Data Grid and SQL syntax checking

In this new release of SQL Dev, when I execute a SQL in the SQL Worksheet and click in the Data Grid in the Results tab and try to navigate within a record using arrow keys, the grid cell enters into edit mode by default and so I cannot use the Left or Right arrow keys to navigate the grid. I am forced to use tab key to navigate. This is counter intuitive in my opinion.
Is there any option to change this behavior?
Another issue that I have come across is with SQL syntax checking. In some cases, when I press F9 to execute a SQL, it shows the SQL as executed i.e. shows something like 0.0134 seconds in the toolbar and no results displayed. In reality, the SQL had some syntax error which were NOT reported. This can be frustrating since now I have to fall back to SQL*Plus or TOAD just for syntax check.
I like the fact that SQLDev highlights the current SQL but it would be more useful if it just indicated the first line of the current sql instead of highlighting the whole sql.
Manish

"In this new release of SQL Dev, when I execute a SQL in the SQL Worksheet and click in the Data Grid in the Results tab and try to navigate within a record using arrow keys, the grid cell enters into edit mode by default and so I cannot use the Left or Right arrow keys to navigate the grid. I am forced to use tab key to navigate. This is counter intuitive in my opinion."
In the "Results" tab, Click Ctrl & Tab keys (at the same time) or with mouse click on any cell other than the first column (a sequence or rownum), you will be able to navigate using the arrow keys.
"Another issue that I have come across is with SQL syntax checking. In some cases, when I press F9 to execute a SQL, it shows the SQL as executed i.e. shows something like 0.0134 seconds in the toolbar and no results displayed. In reality, the SQL had some syntax error which were NOT reported. This can be frustrating since now I have to fall back to SQL*Plus or TOAD just for syntax check."
The 0.0134 seconds could be the result of the most recently executed successful statement. Check the Script Output tab for errors. Use F5 (Run Script option) instead of F9.
"I like the fact that SQLDev highlights the current SQL but it would be more useful if it just indicated the first line of the current sql instead of highlighting the whole sql."
On the SQL statement (or code), Right Click -> Format SQL (or press Ctrl & B), proper formatting would help.
I use version 1.0.0.15.57 and seems to be working allright.
- Babu Rangasamy

SQL Developer 3.0.04 - SDO_GEOM Issues

1. Performing a "SELECT *" on an Oracle table with a SDO_GEOMETRY column locks up the tool and I have to use Task Manager to can it.
2. Clicking the Data tab on a table with an SDO_GEOM col either locks up the tool, or it takes forever to return.
3. Performing a "SELECT" of a SDO_GEOM col either locks up the tool or takes forever to return.
None of these issues occur in Toad.
Edited by: JB on Jan 25, 2012 12:41 PM

Hi,
As Raghu noted above, and you also saw in rp0428's following reply,
Re: Problem with displaying sdo_geometry objects
drilling down to the cell edit details is your only recourse for now. Apparently there will be further work done in this area, but it is not clear exactly what or when it will be. For those with access to it, here is a bug reference:
Bug 13680849 - RC1: NOT DISPLAYING THE DATA OF MDSYS.SDO_GEOMETRY
Regards,
Gary

SQL Developer 3.0 Query Builder Issue

Similar Messages

Maybe you are looking for