Screen refresh issue with SQL Developer 1.5.5 on Vista 64 bit

I am using the latest version of SQL Developer.
I have screen refresh issues in sql developer. On scrolling up and down the display gets jumbled, some time screen do not display at all. Its making working with SQL Developer very difficult. I don't have such an issue with any of my other editors.
Is this something specific to Vista? Is there any know solution to this issue.
Thanks
Edited by: user5899685 on Sep 1, 2009 11:14 AM

Specific? Not really, but judging from the posts here Vista is more prone. It usually indicates incompatibility between Java and video drivers.
If updating your JDK or video driver doesn't work or isn't an option, just disabling DirectDraw in \sqldeveloper\bin\sqldeveloper.conf usually works too:
AddVMOption -Dsun.java2d.noddraw=trueHope that helps,
K.

Similar Messages

Issue with SQL Developer connect to SQL server

I'm using "SQL Developer 2.1.1.64.45" to work on a migration project which needs to convert a SQL server database to a Oracle 11g database. But I got an issue when I setup the SQL server connection. The SQL Developer let me connect by selecting a SQL server database name (For example: Northwind), but once connected, it always connected to "master" database instead. The "SQL Developer" is running on Windows 7 Professional (x64) platform. My Oracle database is 11g, and SQL server database is SQL 2005. And my SQL server instance name is "SQL2005". Anyone have ever experienced this problem? Thanks in advance.
Edited by: user8276338 on Feb 8, 2011 1:05 PM

Hi Bob,
Thanks for the feedback, lets stick with SQL Developer 3.
Correct me if I'm wrong,
You attempted to migrate from SQL Server to Oracle including target generation and datamove in one go, by filling in each step of the migration wizard to the end.
During the datamove you got
ORA-01000:maximum open cursor exceeded
So it looks like SQL Developer during the migration is not closing cursors fast enough and hits the maximum number of open cursors in your Oracle database.
I think the default max open cursors is 300 in Oracle.
There are a few things we can do here.
You should be able to see the new migration project in your Migration Projects navigator.
By navigating down the project tree to "Converted Database Objects" we can attempt the data move again by right clicking and choosing "Data Move".
But first I would restart SQL Developer so as to free up any lingering open cursors.
That may allow you to complete the data move, as the only cursors being open are being used in the data move and not some cursors which may have been left open from previous steps in the migration.
Now from my perspective I would like to identify where are we leaving open the cursors, so I'm going to setup some testcases my end to see if I can replicate.
From your perspective Id presume you just want to move on with the migration.
So if the above (shutdown and attempt just the data move) doesnt workyou could
A) Increase the MAX OPEN CURSORs on your Oracle databases so it complete the data move
or
B) Use the offline data move technique.
A) Increase MAX OPEN CURSORs
This wiki explains how to do that, looks like 1000 is fairly common, but even a much larger number is not a problem
http://wiki.oracle.com/page/OPEN_CURSORS
ALTER SYSTEM SET OPEN_CURSORS = 10000;
OR
B) Offline Data Move
If you are moving large amounts of data (say > 1GB), then the standard data move (we call it online), which just uses JDBC to SELECT * FROM and INSERT INTO may not cut the mustard.
In this case you can try using our offline technique. SQL Developer will generate a set of scripts for you.
unload_script.bat will use SQL Servers BCP tool to dump out the table data into DAT files.
oracle_ctl.bat will load the data in the DAT files into Oracle.
As we know the names of all the tables, columns ,both SQL Server and Oracle, we can generate fairly good scripts.
The benefit of this technique is large amounts of data can be migrated and you get to use tools designed to dump data and load in data, so you have better error logging and tweaking.
To attempt this in the Migration Wizard , Data Move page, select offline.
If you can describe your database a bit (number of tables, number of procedures, amount of data to migrate) I may be able to define my testcase better so I can replicate the issue.
Thanks
Dermot
SQL Developer Team.

Issue with SQL Developer connecting to databases

Hi all,
I would be really grateful if anyone could advise me on the below issue.
I have 64bit laptop running Windows 7 and I get the following error message when I try to connect via SQL Developer to an external database for work purposes:
Status: Test Failed: C:\app\Terra-PC\product\product\11.2.0\dbhome_1\BIN\ocijdbc.dll: Can't load AMD64-bit .dll on a IA 32 -bit platform.
Thanks for your help.
Luke

Hi,
Actually, I resolved this issue with the help of a colleague. SQL Dev was not able to see my TNSnames file, because the Oracle_Home path was not defined. Something like that, anyway.
Thanks,
Luke

Noticed issues with SQL Developer 3.0

Not sure where to file these found issues (and post them here until someone knows where to...)
- Create TAPI PL/SQL wizard doesn't take into account tablenaming (and columns) which uses all possible 30 characters and therefore generates code that can not be compiled while adding extra characters.
- In the "create index" wizard (right click when in "table" section), it is possible to click and add values which will generated the following (when executed the database will not except the syntax of course)
create index index01 on table01 (column01, column01, column01, column01, column01)

Buntoro wrote:
For creating TAPI, basically, I am not certain what is that actually?
Is it creating PL/SQL (stored proc / function)?
Which part that causes the naming restriction being overruled?
A simple step to reproduce is more than welcome.Can't be reproduced and its that simple that dev. people involved will know what I mean
>
For creating index, I believe that should be marked as a bug. SQL Dev should remove the selected column name to avoid being chosen again.
Thats also a way to solve bugs --- grin --- (snik smiles are not allowed anymore on the OTN forums, beats me why)
For DDL generation script, I believe SQL Dev relies on DBMS_METADATA, therefore this issue implies on your case.
Perhaps you can give any idea to enlighten the developer on how to provide the correct result for XML type.Will report it to the xmldb dev team when beta trails begin, somewhere in the future I guess, for Oracle 12. It has no hurry, there are more XMLDB features not properly supported in the common development Tools (also for all those not Oracle, like toad)
Edited by: Marco Gralike on May 18, 2011 7:04 PM

Issue with SQL Developer 4.1 Early Adopter 2 - start sql-script by "@"

Hi,
today i realized, that starting a sql-script by writing @scriptname.sql in a sql worksheet and press F9 to start the script, does not work anymore.
With EA2 there is always an error message shown like "unkown command" with some strange characters "��" in the script logging window.
The sql-scripts are located in a filesystem folder the os environment variable SQLPATH points to.
In Version 4.0.x this worked perfect! Is this a planned "feature" or just a bug in EA2 fixed in later EA versions?
In addition, when i open such a sqlscript with the file open menu in sqldeveloper the content of the sqlscript is not shown in the script window. There are only some none printable characters "��" displayed in the sqlworksheet, and not the "select ..." a normal texteditor shows.
Thanks in advance
Matthias

Hi,
with encoding set to utf8 it does not work. Don't know why. After setting the encoding to "cp1252" everything works fine again! Thank you very much!
Matthias

Mouse moving issue in sql developer 3.2

Hi,
I'm using sql developer 3.2 in vmware .I'm facing issue when i try to select the package/procedure from left side tree structure with mouse,mouse pointer is moving to some other place.
If i try to click on one object name(procedure/package/function) then mouse pointer is moving to other object name automatically.It is very difficult to work .Can some advice why it is ? And how i can resolve?
And at the same time no issue with sql developer 1.1 .
Environment:
In side vmware
Os:Xp
Sql developer Version 3.2.20.09

Enable security descriptors = Allow virtual applications full write permission to the virtual file system.
Here is how it looks like:
https://twitter.com/packageologist/status/462180503995813888/photo/1

SQL Developer 3.0/3.1 64 Bit Memory Setting

Hi,
To avoid hitting memory setting issues with SQL Dev 3.0/3.1 64 bit clients, you can make the following changes:
1) Close SQL Developer
2) Locate the sqldeveloper.conf file
Found in directory:
C:\<SQLDeveloper32\sqldeveloper\sqldeveloper\bin
3) Change the following line
Before:
AddVMOption -XX:MaxPermSize=128M
After:
AddVMOption -XX:MaxPermSize=256M
4) Launch SQL Developer
A memory issue of this sort will generally result in non-responsive UI behavior.
You can verify that you are hitting this issue by launching the console window version of SQL Developer and checking for memory exceptions.
C:\SQLDeveloper30-64RTMPatch1\sqldeveloper\sqldeveloper\bin\sqldeveloper.exe
A bug has been filed change this setting.
Thanks, Mark

SQL Developer itself will work with a 64-bit JDK. It is possible that the data modeler still requires a 32-bit JDK.
You may get better answers in the dedicated Data Modeller forum.

To display chinese characters with SQL Developer

I have created one table on the Oracle Express Database. In this table ther is one field Nchar tipe.
The NLS_CHARACTERSET of the d.b. is WE8MSWIN1252, the NLS_NCHAR_CHARACTERSET is AL16UTF16.
I have done an insert on the table and in this field i have inserted this word: 了解更多
When i do a select comand with sql developer, on the results i see this only this •••• .
But if i copy this and cut on the Sql Developer editor, i see the corret word.
How could i configurate ?
Regards
Mario

Hi
The following works but there may be better solutions:
http://totierne.blogspot.com/2008/05/issuesquare-boxes-as-text-characters.html
Issue:Square boxes as text characters Solution:Add fonts
Chinese characters in Linux see Debian Chinese How To [1] basically:
1. create a jre/lib/fonts/fallback directory if necessary and
2. copy or link the fonts files into this directory. (On my Linux system: /usr/share/fonts/truetype/arphic/gbsn00lp.ttf )
-Turloch

Jdbc-OCI:112020 Error with SQL Developer 4.0.0.12

Hi,
I receive an error, Incompatible version of libocijdbc[Jdbc:112030, Jdbc-OCI:112020, when attempting to log into an existing connection with SQL Developer 4.0.0.12. I do have the JDK 7u45 for 32 bit Windows 7. I know this was an issue in the past and attempted to look at earlier solutions with no luck. Any idea?

The issue is that if you are using the OCI (thick) JDBC driver the version of the JDBC library (in SQLDeveloper) must match the version in your ORACLE_HOME.
It seems SQLDeveloper 4 ships with 11.2.0.3 version of JDBC and you have 11.2.0.2 client installed.
Possible options:
1 Don't use the OCI driver. You can untick the box in Tools |Preferences|Database |Advanced, but some connection types use it anyway.
2 Upgrade your Oracle client.

Serious UI issues in SQL Developer 4.0 for Mac

I've encountered some serious UI issues in SQL Developer 4.0 for Mac (4.0.0.13) that impact it up to the point where it becomes unusable.
If the database and tables are expanded in the "Connections" view, sometimes a node in the tree seems to become sticky. Whenever you scroll the up or down, it will immediately scroll back to make the old selection visible again. If you want to work with an item that's outside the current view (e.g. to collapse the "Tables" node), you can no longer use it. SQL Developer needs to be restarted.
If the context menu is opened (ctrl click), it appears in the wrong place. It's too far to the right and bottom. If you then move the mouse pointer towards the menu, a rectangle appears and follows the mouse pointer as if you had initiated a drag and drop operation.
If the "Data" tab of a table is selected and if a cell is clicked to edit the cell value, the text cursor is drawn in the wrong position. It can be off by more than one character and it is often drawn in the middle of a character instead of between two characters. It's hardly possible to edit the cell value as you cannot tell for sure where insertions and deletions will happen. You basically need to copy the value into a separate editor, edit it there and copy it back.
The scrolling in the "Data" tab of a table is a pain. For no obvious reason, it first scrolls downwards a few rows and then jumps to the top (at least using a Magic Mouse). If all rows have been loaded, this problem seems to disappear. But generally, the scrolling distance is far too short. With a long finger swipe, one would expect to scroll the contents by several pages. However, it only scrolls about half a page. For shorter swipes, it's similar. It sometimes only scrolls by a few pixels.
Am I the only one to experience these severe problems? Or is the Mac version not as mature as the Windows version yet?

In terms of diagnosis, perhaps not -- probably very time-consuming to debug. I did find some unpublished bugs against dual monitor use ...
Bug 13727841 - FORUM: 64BIT WIN7 SOME DIALOGS SHOW ON DISPLAY 1 WHEN SQLDEV ON DISPLAY 2
Bug 18504928 - NEW CONSTRAINT UI MENU IN TABLE DIALOG AT WRONG LOCATION ON DUAL MONITOR
The first turned out to be an issue in the 64-bit Java AWT libraries, not the 32-bit libraries, and specifically for Windows 7 as opposed to, say XP, but this was all quite a bit in the past and was fixed for 4.0. The second one (on 64-bit Linux), however, just came in yesterday, so you can wait to see if a fix for that also covers your situation or, if you are able, pursue it directly with Oracle Support.

Help for migrating DB2 to Oracle11 g, with Sql Developer

Hello, Good Afternoon,
Today I started a series of exercises to migrate DB2 9 to Oracle 11 g, with SQL Developer in order to evaluate this tool for a project we have in door.
But it is setting a number of issues, because the DB2 tables that we are trying to migrate do not have primary key and load the data sets the error ORA-02270.
It is generating an error when trying to convert the following triggers.
CREATE TRIGGER min_salary NO CASCADE
BEFORE INSERT ON staff REFERENCING NEW AS newstaff
FOR EACH ROW MODE DB2SQL BEGIN ATOMIC
SET newstaff.salary =
CASE
WHEN newstaff.job = 'Mgr' AND newstaff.salary < 17000.00 THEN 17000.00
WHEN newstaff.job = 'Sales' AND newstaff.salary < 14000.00 THEN 14000.00
WHEN newstaff.job = 'Clerk' AND newstaff.salary < 10000.00 THEN 10000.00
ELSE newstaff.salary END;
END
CREATE TRIGGER do_not_del_sales NO CASCADE
BEFORE DELETE ON staff REFERENCING OLD AS oldstaff
FOR EACH ROW MODE DB2SQL
WHEN(oldstaff.job = 'Sales') BEGIN ATOMIC SIGNAL SQLSTATE '75000'
('Sales staff cannot be deleted... see the DO_NOT_DEL_SALES trigger.'); END
SEVERE 197 625 oracle.dbtools.migration.workbench.core.MigrationLogResourceBundle Failed to Convert Trigger MIN_SALARY>: class org.antlr.runtime.NoViableAltException -> null: Line 1 Column 0
SEVERE 196 1328 oracle.dbtools.migration.workbench.core.MigrationLogResourceBundle Failed to Convert Trigger DO_NOT_DEL_SALES>: class org.antlr.runtime.NoViableAltException -> null: Line 1 Column 0
I can do for Work Bench (SQL Developer) not validate that DB2 must carry primary keys?
I can do for Work Bench (SQL Developer), I can turn triggers the 2 above?
Greetings

to follow up the root cause of ORA-02270 it would be good to get the DB2 table definition as the table is defined in the Oracle database.
For the other issue with the trigger, please have a look at:
http://www.oracle.com/technetwork/database/migration/db2-084087.html
=> it lists which objects the migration supports as:
Supported Migration Objects
     Tables
     Views
     Indexes
     Users
     Constraints
=> so no triggers.

View jobs with SQL Developer and export to file with delimiter

Hi,
is there a way to view, create and alter my database jobs with SQL developer?
And is it possible to export tables, views or simple queries to file delimited different from the CSV standard?
Diego.

Hi and Welcome to the Forum!!
To select data from a table or a view you must use the SELECT sql command. Example to get the data from your view you can
select ZMATNUM,ZMATCUR,ZMATATTR from ZMATERIALAs you have said you are using SQL Developer just execute the above query in your sql developer and it will show the data. Right click the grid and export the data to excel file.

Statement terminator problems when exporting data with SQL Developer 3.2

I've ran across what appears to be a bug with SQL Developer 3.2.20.09. If someone can let me know if this is indeed a bug, or just something I need to configure differently, please let me know.
The problem is related to exporting a database as a SQL script, and terminator characters at the end of "create" statements, especially when columns have comments, and problems that occur when using SQLPlus to run the export script to create the tables. With the old SQL Developer 1.5.4, with the "Terminator" and "Pretty Print" options checked, statements like the following are generated:
-- DDL for Type NUM_ARRAY
CREATE OR REPLACE TYPE "NUM_ARRAY"
IS TABLE OF NUMBER(20)
-- DDL for Sequence MYTABLE_SEQ
CREATE SEQUENCE "MYTABLE_SEQ" MINVALUE 1 MAXVALUE 999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ;
-- DDL for Table MYTABLE
CREATE TABLE "MYTABLE"
(     "MYTABLE_ID" NUMBER,
     "COL2" NUMBER,
     "COL3" NUMBER
-- DDL for Table ANOTHERTABLE
CREATE TABLE "ANOTHERTABLE"
(     "ANOTHERTABLE_ID" NUMBER,
     "COL2" VARCHAR2(1024),
     "COL3" VARCHAR2(1024)
COMMENT ON COLUMN "ANOTHERTABLE"."ANOTHERTABLE_ID" IS 'This is a comment.';
When I then run the script using SQLPlus, everything works fine. However, with SQL Developer 3.2.20.09, with the same options enabled, the same statements are generated like this:
-- DDL for Type NUM_ARRAY
CREATE OR REPLACE TYPE "NUM_ARRAY"
IS TABLE OF NUMBER(20)
-- DDL for Sequence MYTABLE_SEQ
CREATE SEQUENCE "MYTABLE_SEQ" MINVALUE 1 MAXVALUE 999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ;
-- DDL for Table MYTABLE
CREATE TABLE "MYTABLE"
(     "MYTABLE_ID" NUMBER,
     "COL2" NUMBER,
     "COL3" NUMBER
-- DDL for Table ANOTHERTABLE
CREATE TABLE "ANOTHERTABLE"
(     "ANOTHERTABLE_ID" NUMBER,
     "COL2" VARCHAR2(1024),
     "COL3" VARCHAR2(1024)
COMMENT ON COLUMN "ANOTHERTABLE"."ANOTHERTABLE_ID" IS 'This is a comment.';
Notice all of the extra slashes in there. If a slash is not used as a statement terminator, SQLPlus treats slashes as a command to repeat the last SQL statement, which causes many errors about tables or sequences already existing. So, I tried removing the "Terminator" flag from the export options. This lead to statements that looked a bit more promising:
-- DDL for Type NUM_ARRAY
CREATE OR REPLACE TYPE "NUM_ARRAY"
IS TABLE OF NUMBER(20)
-- DDL for Sequence MYTABLE_SEQ
CREATE SEQUENCE "MYTABLE_SEQ" MINVALUE 1 MAXVALUE 999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE
-- DDL for Table MYTABLE
CREATE TABLE "MYTABLE"
(     "MYTABLE_ID" NUMBER,
     "COL2" NUMBER,
     "COL3" NUMBER
-- DDL for Table ANOTHERTABLE
CREATE TABLE "ANOTHERTABLE"
(     "ANOTHERTABLE_ID" NUMBER,
     "COL2" VARCHAR2(1024),
     "COL3" VARCHAR2(1024)
COMMENT ON COLUMN "ANOTHERTABLE"."ANOTHERTABLE_ID" IS 'This is a comment.'
The big problem, though, is in the statement for the table with a comment. Notice that there are two statements, but there is not a semicolon after either of them. This unfortunately causes the "COMMENT" statement to be appended to the "CREATE TABLE" statement before being executed, which causes the table to not be created (which causes even more errors later on when the script attempts to populate the table with data).
So, it would appear that this is a bug, but I'm not sure. Is there a way I can configure the export options to make SQL Developer export these statements like it used to in older versions?
Thanks,
-Bill

>
So, it would appear that this is a bug, but I'm not sure.
>
That would be a bug. Thanks for reporting it and providing the detailed example.
>
Is there a way I can configure the export options to make SQL Developer export these statements like it used to in older versions?
>
No.
Leave the thread open. One of the developers for sql developer should be monitoring the forum and can provide more information.

DB2 8.1 to Oracle 11g with SQL Developer 3.0

Hi,
I started migrating my DB2 8.1 to Oracle 11g, with SQL Developer 3.0
Basically, I need to migrate TABLES.
I followed these steps:
1) I created a new Oracle database, tablespaces, users, etc.
2) Then, I created both (DB2 and Oracle) connections into SQL Developer 3.0. All works fine.
3) I start capturing one table with the "Copy to Oracle" feature. Done with no errors.
But when I compare the table structure, I see the following problems in Oracle:
a) All fields are NULLABLE = YES. SQL Developer show this field property correctly in DB2: NULLABLE = NO, but not migrated the same!
SOLUTION: All I want is that SQL Developer simply migrating the same value who I have in the DB2. But how?
b) In DB2 I have one field property called COLUM DEFAULT. In Oracle this property is called DATA_DEFAULT. The SQL Developer show this field property correctly for the DB2 tables (for example: 0.0, ' ', etc), but don't migrated the same value! All fields are configured to DATA_DEFAULT = NULL.
SOLUTION: I think this occurs because NULLABLE is migrated with the value YES. Well, all I need is the same above...
NOTE: I tested the SWISSQL DATA MIGRATION software, and it works fine. All tables, field properties and data are migrated sucessfull. But this program is trial version!
Well, I think all of this are BUGS into SQL Developer.
Please, anyone to help me?
Regards,
Ylram

Welcome to the forum!
>
I just did right click in the procedure body and found [Debug, Compile for Debug, Compile, Run].
>
You listed a bunch of things but you didn't say what steps you actually performed and what the result was.
Did you 'Compile'the procedure? until you compile the procedure you can't debug it.
I just created a new procedure and when I select the body it displays in the 'Code' window on the right. But the 'Debug' icon is not enabled because the procedure was not compiled for debug.
When I compile it for debug the 'Debug' icon is now enabled.

Problems with SQL Developer 2.1

I have upgraded to SQL Developer 2.1 from 1.5.5.
Iam presenting my overall experience with SQL Developer 2.1 compare to 1.5.5 version.
If the session expires, reconnecting is really pain in all SQL Developer versions. It opens a new blank window every time we reconnect, we have to copy all the things into new window every time.
when i tried to execute an insert as select statement it is showing nothing, but it's doing something in the background.
My templates are not working for (ctrl+Shift+T) after i upgraded to 2.1 from 1.5.5.
Things I tried and liked in 2.1 are*
1. 2.1 gives the exact time taken to return the no.of rows (Ex: If it returns first 50 rows, it will display time taken for that particular 50 rows only).
Things I did not like in 2.1*
1. When we try to expand a node, it shows "Loading and folder icon" (I didn't like the folder icon showing up every time)
2. I did not like the new icon for SQL Developer 2.1 itself. (It has become hard to identify the 2.1 on the task bar with this icon)
3. I did not like the close(i.e., x) on the worksheet tab.
4. Look and feel wise 1.5.5 is better than 2.1
Thanks!
RG

Regrettably we can't please all the people all the time.
The little cross was a request specifically from the user community. We had complaints that users inadvertently closed windows and wanted a permanent symbol to show the closing tab. This took much effort and time to finally introduce into the product as it had to be approved through usability teams and introduced into the underlying IDE.
The release notes explain that there is no longer a key sequence for the Code Templates, start typing your code and it should appear in the code insight.
The icon updates on the taskbar was also an update based on user feedback.
While there won't be many changes between the release candidate and production, I do remind you that you are working with beta software and not production software.
Thank you for taking the tiem to post your feedback. I hope you'll find lots to really like in the latest release. Take a look through the 2.1 New Features list.
Sue

Screen refresh issue with SQL Developer 1.5.5 on Vista 64 bit

Similar Messages

Maybe you are looking for